OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

ubl message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Element Documentation - NDR Question


It was a good meeting in Manhattan last week.  Mark Crawford did
a really good job overviewing CCTS 3.0.

I provided some comments on the NDR to Mike last week.  I started looking
closer at the UBL 2.0 schemas.  I found something that I found confusing.
Element declarations (ABIE and BBIE) do not have any documentation nodes
for them when they are defined.

A referred element does have a definition.  For example:

<xsd:element name="DocumentResponse" type="DocumentResponseType"/>

    <xsd:element ref="cac:DocumentResponse" minOccurs="1"
maxOccurs="unbounded">
        <xsd:annotation>
          <xsd:documentation>
            <ccts:Component>
              <ccts:ComponentType>ASBIE</ccts:ComponentType>
              <ccts:DictionaryEntryName>Application Response. Document
Response</ccts:DictionaryEntryName>
              <ccts:Definition>A response to one or more
documents.</ccts:Definition>
              <ccts:Cardinality>1..n</ccts:Cardinality>
              <ccts:ObjectClass>Application Response</ccts:ObjectClass>
              <ccts:PropertyTerm>Document Response</ccts:PropertyTerm>
              <ccts:AssociatedObjectClass>Document
Response</ccts:AssociatedObjectClass>
            </ccts:Component>
          </xsd:documentation>
        </xsd:annotation>
      </xsd:element>

From a management of business objects and reusability I would prefer the
documentation (or at least the definition) to be available when the
element is defined.  I don't want to have to go look at where it is
being used in order to understand the meaining of the element.


Betty





[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]