Discussion based on the UBL briefing paper issued by Tim McGrath
raising a number of issues with the UBL and OAG use of CCT schema
modules.
Issue1: Formal Attribute naming of
SC
Group agreed that attributes should reflect the formal dictionary
entry name of the supplementary component as specified in CCTS. Although not specifically called out in CCTS, in
fact supplementary components follow the pattern of tripartate
naming.
Issue2: xsd:token vs
xsd:normalizedString
xsd:token is more restrictive than xsd:normalizedString in that it
does not allow leading and trailing spaces or two or more spaces in sequence.
Internally in the UN/EDIFACT database code values are stored with leading
spaces, although the spaces are not part of the code value itself.
The only justifiable reason for using xsd:normalizedString
identified was to provide for human readability. This approach is however
considered dangerous as it introduces the possibility of errors in a B2B
environment.
Group agreed to use xsd:token for codes and
identifiers.
Following the reasoning above also the SC Language. Local.
Identifier should use xsd:token.
Issue3: Supplementary component
Format
The CCT schema module will include an attribute for each of the
SC, including format. However in the UDT schema module the format attribute will
not be declared where an appropriate xsd:built-in data type can be used.
Issue4: Restrictions on Binary Object for Picture, Sound and
Video
The CCT schema module will include an attribute for each of the SC
for both primary and secondary representation terms. The UDT schema module will
only declare those SCs that are appropriate.
UDT:BinaryObject will declare an attribute for each
SC
UDT:Graphic, UDT:Picture, UDT:Sound and UDT:Video will be declare
as independent complex types containing only the required SCs as
attributes.
Issue5: Patterns for Indicator data
type
The CCT schema module will include an attribute for each of the
SC, including format.
The UDT schema module will declare the indicator as
xsd:base=boolean with pattern true and false.
CEFACT intends to finalise their
CCT and UDT schema modules within the next two weeks following the
above.
