Erratum identified: Business Document Envelope v1.1 Committee Specification 01

["G. Ken Holman" <gkholman@CraneSoftwrights.com>]

Fellow BDXR TC members,

This post is for the record that an erratum has been identified 
(thanks, Kenneth!) in BDE v1.1 CS01 in the documentation for the 
payload information:

 http://docs.oasis-open.org/bdxr/bdx-bde/v1.1/cs01/bdx-bde-v1.1-cs01.html#S-BASIC-PAYLOAD-INFORMATION

The second information item incorrectly documented as DocumentTypeID 
is, in fact, correctly DocumentTypeCode in the model and in the schema:

<xsd:element ref="cbc:DocumentTypeCode" minOccurs="0" maxOccurs="1">
  <xsd:annotation>
     <xsd:documentation>
        <ccts:Component>
           <ccts:ComponentType>BBIE</ccts:ComponentType>
           <ccts:DictionaryEntryName>Payload. Document Type Code. 
Code</ccts:DictionaryEntryName>
           <ccts:Definition>This element identifies the type of the 
payload instance in the envelope.</ccts:Definition>
           <ccts:Cardinality>0..1</ccts:Cardinality>
           <ccts:ObjectClass>Payload</ccts:ObjectClass>
           <ccts:PropertyTerm>Document Type Code</ccts:PropertyTerm>
           <ccts:RepresentationTerm>Code</ccts:RepresentationTerm>
           <ccts:DataType>Code. Type</ccts:DataType>
        </ccts:Component>
     </xsd:documentation>
  </xsd:annotation>
</xsd:element>

The OASIS process only describes approving errata for OASIS 
Standards, not for Committee Specifications:

  https://www.oasis-open.org/policies-guidelines/tc-process#errata

... and so I propose we wait to make the edit until we decide how we 
are to proceed with the Committee Specification in light of the 
collaborative work with SBDH.

. . . . . . Ken

--
Contact info, blog, articles, etc. http://www.CraneSoftwrights.com/o/ |
Check our site for free XML, XSLT, XSL-FO and UBL developer resources |
Streaming hands-on XSLT/XPath 2 training class @ US$45 (5 hours free) |