Hello UBL TC,
I promised you a 2.1 PRD1 release candidate today, and here it is:
http://www.oasis-open.org/committees/download.php/39273/UBL-2.1-PRD1-20100909.zip
I'd like to consider this a sanity check, but a possible schema
issue has turned up.
Naming and Design Rules ELD12, ELD13, and ELD14 (see page 122 of
UBL-2.1.pdf) read as follows:
ELD12
The UBL Extensions element MUST be declared as the first
child of the document element with xsd:minOccurs="0".
ELD13
The UBLProfileID element MUST be declared immediately
following the UBL Extensions element with xsd:minOccurs="0".
ELD14
The UBLSubsetID element MUST be declared immediately
following the UBLProfileID element with xsd:minOccurs="0".
VER15 is relevant, too:
VER15
Every UBL document schema MUST declare an optional element
named UBLVersionID immediately following the optional UBL
Extensions element.
Ken Holman has pointed out that Naming and Design Rule ELD14
should refer to CustomizationID, not UBLSubsetID. But it looks
like there's another problem here as well. ELD13 says that
UBLExtensions must be immediately followed by UBLProfileID, but
VER15 says that UBLExtensions (ignore the extra space for now, we
can fix that) must be immediately followed by UBLVersionID.
Here's a fragment of the declarations from an xsdrt file chosen at
random (DespatchAdvice, as it happens):