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

 


Help: OASIS Mailing Lists Help | MarkMail Help

ubl-ndrsc message

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


Subject: RE: [ubl-ndrsc] FW: More ASBIE Confusion (in UBL)


Greetings,
 
After looking at some of the other schemas, it seems that the only time a global element isn't declared for the ASBIE is when its name would be the same as the global element declared for the ABIE in the Reusable schema.
 
Mike Grimley
 
-----Original Message-----
From: Grimley Michael J NPRI [mailto:GrimleyMJ@Npt.NUWC.Navy.Mil]
Sent: Tuesday, January 13, 2004 1:56 PM
To: CRAWFORD, Mark; Lisa Seaburg (E-mail)
Cc: Sue Probert (E-mail); MJG At Work (E-mail)
Subject: More ASBIE Confusion (in UBL)

Greetings,
 
First the problem, then a question about the solution...
 
While reviewing the UBL Invoice schema, I came upon the following element declaration within the sequence defining InvoiceType:

  <xsd:element ref="cat:InvoiceLine" maxOccurs="unbounded">
    <xsd:annotation>
      <xsd:documentation>
        <ccts:Component>
          <ccts:CategoryCode>ASBIE</ccts:CategoryCode>
          <ccts:DictionaryEntryName>Invoice. Invoice Line</ccts:DictionaryEntryName>
          <ccts:Definition>An invoice has one or more invoice lines</ccts:Definition>
          <ccts:ObjectClass>Invoice</ccts:ObjectClass>
          <ccts:PropertyTerm>InvoiceLine</ccts:PropertyTerm>
          <ccts:RepresentationTerm>InvoiceLine</ccts:RepresentationTerm>
          <ccts:DataType>InvoiceLine.Type</ccts:DataType>
          <ccts:AssociatedObjectClass>InvoiceLine</ccts:AssociatedObjectClass>
        </ccts:Component>
      </xsd:documentation>
    </xsd:annotation>
  </xsd:element>

Although the documentation indicates that this is an ASBIE, it references the InvoiceLine global element in the reusable schema (ref="cat:InvoiceLine"), which is an ABIE:
   
    ** Global Element declaration in Reusable (cat:) **

  <xsd:element name="InvoiceLine" type="InvoiceLineType"/>
  <xsd:complexType name="InvoiceLineType">
    <xsd:annotation>
      <xsd:documentation>
        <ccts:Component>
          <ccts:CategoryCode>ABIE</ccts:CategoryCode>
          <ccts:DictionaryEntryName>Invoice Line . Details</ccts:DictionaryEntryName>
          <ccts:Definition>Information directly relating to a line item of a transaction. It identifies the item but only includes details about the item that are pertinent  to one occurrence on a line item, e.g. quantity etc.</ccts:Definition>
          <ccts:ObjectClass>InvoiceLine</ccts:ObjectClass>
          <ccts:RepresentationTerm>Details</ccts:RepresentationTerm>
        </ccts:Component>
      </xsd:documentation>
    </xsd:annotation>

There is no global element declaration for the ASBIE. (Same problem with most of the 'ASBIE' declarations.) Aren't we essentially containing an ABIE within another ABIE. If not, what would be the difference?

Now, to take the next step, if we were to declare a global element of type "InvoiceLineType" for the ASBIE (as indicated in the NDR), what would we name it? The first step would lead us to "InvoiceInvoiceLine", then we would remove the duplicate 'Invoice' (as per the NDR) which would leave us with a global "InvoiceLine" element. However, we already have a global "InvoiceLine" element in the Reusable schema/namespace. Do we create another one for the Invoice namespace?

??
MikeG



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