[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: Getiing Ready!
Folks, I
have just completed an initial read of the entire 3.0 CIQ Specification Document.
I have tremendous respect for what they have done. A great spec!!!! CIQ
provides common ground for addressing, naming, and relating names and addresses
to parties, yet is flexible enough not to compromise specific system
requirements. Its code lists for attributes (e.g., “city” as a
name attribute for<municipality> or “last name” as a value
for <NameElement> allows these values to be renamed as necessary. The
elements themselves are fixed. This is very interesting to me. Flexible
structure is not an oxymoron. It lives in CIQ. Quite
frankly, we may also want to review using the GeoRSS element in CIQ Address in
place location in all of our specs. It is fairly simple, relatively clear,
and is GML compatible. It might be better than our “wheel reinvention.” Finally,
I now even have a reason to consider using both elements and attributes in a
spec. As I read CIQ, all elements are MUST understands for all CIQ
compliant systems. Attributes are MAY understand and might be SHOULD
understand. But CIQ compliant systems are not expected to use, or even
understand all attributes and their possible values. Some might not
understand any of them. Think of attributes in CIQ as pre-defined
<parameter> tags, as parameter is defined in CAP, that are applied to the
element in question rather than the entire message. That
said, I (actually the CIQ spec) have a few questions on our CIQ adoption. The
following quoted material below is from the CIQ spec. Adopting CIQ correctly
means answering the questions represented by the bullets below. Have we done
so? If so, have we documented it? Documenting our answers to these
questions would go along way toward removing the ambiguity that exists between
our very nice examples that use CIQ and our relative lack of explanation of
where the CIQ portions of those examples come from. “Following
are the features of CIQ specifications that assist in customisation of the
specifications to meet specific application or data exchange requirements, and
the details of customisation SHOULD be documented and agreed (if involving more
than one party in data exchange) at application/system design time to enable
automating interoperability of information/data represented using CIQ
specifications at application/system run time: ·
List of all elements of CIQ XML
Schemas that SHOULD be used in the exchange. This includes details of which elements
are mandatory and which elements are OPTIONAL ·
List of all attributes of CIQ XML
Schemas that SHOULD be used in the exchange. This includes details of which
attributes are mandatory and which attributes are OPTIONAL ·
The approach that will be used for
Code Lists (Option 1 or Option 2) ·
The code list values that SHOULD
be used for each CIQ code lists. This includes updating the default XML Schemas
for code lists (Option 1) with the values to be used and updating the default
genericode based code lists (Option 2) with the values to be used. These code
list files SHOULD then be implemented by all applications/systems involved in
data exchange. If genericode based code list approach (Option 2) is used, then
the XSLTs for value validation SHOULD be generated and implemented by all
applications/systems involved in data exchange. ·
Whether xLink or Key Reference SHOULD
be used to reference party, name or address, and the details ·
Whether XML schema SHOULD be
extended by using new attributes from a non-target namespace
and if so, details of the additional attributes ·
Whether business rules SHOULD be
defined to constrain the CIQ XML schemas and if so, details of the business
rules that SHOULD be implemented consistently by all applications/systems
involved in data exchange.” Now --- Did I stir up a hornet’s
nest?? Respectfully, From: Rex Brooks
[mailto:rexb@starbourne.com] Thanks Will do. Cheers, Rex At 9:50 AM -0500 12/29/07, Gary Ham wrote:
Rex Brooks |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]