Additional updates:

CCT Schema Module - Unique ID in Annotation.  ATG2 agreed that there were no official UN/CEFACT identifiers for CCT components but since Unique ID is required according to the NDR, some value needed to be supplied.  The Unique IDs in the ATG2 schema modules represent a temporary identifier that will be updated once the official UN/CEFACT identifiers are available.

Attributes (using LCC convention) beginning with an acronym.  ATG2 has added a new rule that requires all characters of an acronym to be lower case if they appear at the beginning of an attribute.  For example, UOM Code will become uomCode instead of uOMCode.

CCT Schema Module - Missing Supplementary Components.  Code. Type was missing listVersionIdentifier and Identifier. Type was missing schemeVersionIdentifier.

At this point, there are very few open issues between OAGi and ATG2 on the CCT schema modules (additional issues do exist for other parts of the NDR).

One of the key remaining issues centers around the implementation of Code. Type and Identifier. Type in the UDT module.  In selecting which supplementary components are used for these UDTs, ATG2 has assumed that everyone will use imported Code Lists and Identifier Lists.  Furthermore, there is also an assumption that users will apply the same naming and namespace name rules for these external schema modules.  If these assumptions are correct, supplementary components such as listAgencyIdentifier, listAgencyName, and listName are not necessary because the information is embedded in either the module name or the namespace name.

This approach is problematic for both OAGi and (I believe) ATG2.  For example, if I look at the TBG17 Address ACC, there are BCCs for Address. Format. Code, Address. Postcode. Code, and Address. Type. Code.  I would not expect any of these BCCs would have an external Code List module, but since they are based on the UDT Code. Type, there is no way to define supplemental information such as listAgencyName or listAgencyIdentifier.

Another open issue is the ATG2 implementation of Binary Object and the setting of mimeCode to "required".  In general, I agree that mimeCode will be present most of the time, but I cannot guarantee that it will be available in every instance of an OAGIS message.  This seems to be a little too restrictive for a generic CCTS implementation.

All of the other issues were relatively minor, consisting of things such as the consolidation of certain rules and clarification of several rules.

Garret Minakawa wrote:

Today's ATG2 working group session closed approximately 70 of the ~250 comments submitted by OAGi.

I don't have the exact ATG2 wording but here's a summary of the decisions.

CCT Schema Module - xsd:token vs. xsd:normalizedString.  This issue has been going back and forth between UBL and OAGi for months.  OAGi has always expressed a preference of going with xsd:token while UBL has used xsd:normalizedString.  The current ATG2 NDR uses xsd:token but that decision was changed today.  Now, every occurrence of content or supplementary component with a representation term of Code or Identifier will be expressed as xsd:normalizedString within the CCT Schema modules.  This should not be a major issue for OAGi since we've always been somewhat ambivalent about the issue.

CCT Schema Module - xsd:string for Text components.  The ATG2 decision was to use xsd:string for all content or supplementary components with a representation term of Text.  This may seem a bit obvious but the current OAGIS (and ATG2) CCT Schema Module uses xsd:token for supplementary components like formatText, fileName, listAgencyName, and a few others.  This decision seems perfectly reasonable and should not present any problems for OAGi.

CCT Schema Module - Truncation Rule for Supplementary Components.  Naming conventions for supplementary components has also been an issue that has gone back an forth multiple times.  One of the key issues revolved around the fully qualified Dictionary Entry Name for the supplementary component and whether this Dictionary Entry Name should be the xsd attribute name.  ATG2 has now decided that if the Object Class Term of the supplementary component contains the same term as the CCT it is qualifying, the name of the CCT should be truncated from the supplementary component name.

For example, Amount. Type contains a supplementary component with the Dictionary Entry Name of Amount. Currency, Identifier.  Since the Object Class Term of the supplementary components is the same as the CCT, it is truncated, resulting in a supplementary component name of "currencyIdentifier" or "currencyId".  The supplementary component Code List. Agency, Identifier will be truncated to "listAgencyIdentifier" or "listAgencyId".

In addition, an exception is made for the Identifier. Type CCT.  In the case of Identifier. Type, if the Object Class Term of the supplementary component contains the term "Identification" (not "Identifier"), that term is truncated from the supplementary component name.  This is so supplementary components such as Identification Scheme. Version. Identifier can be truncated to "schemeVersionIdentifier" or "schemeVersionId".

Naming Rule - Truncate "Text".  This rule applies to all schema components, not just CCTs or supplementary components.  Essentially, the rule states if the representation term of a schema component is "Text", the term "Text" will be truncated from the schema component name.

Using the supplementary component Amount. Format. Text as an example, if we apply the truncation rule for supplementary components, we would end up with a supplementary component name of "formatText".  Now, if we also apply the "Text" truncation rule, the supplementary component name becomes "format".

The bottom line is that all of these changes should be good news for OAGi.  We will need to make some changes to our current OAGIS 9.0 CCT Schema Modules, but many of the changes (such as the supplementary component truncation rules) will actually bring us back to our original version of these schema modules (before UBL harmonization).

Furthermore, these changes will now bring ATG2, UBL, and OAGIS into virtually 100% alignment for the CCT Schema Module definitions.

If there are any comments or concerns about these changes, please post them to the member list.

Thanks,

garret