RE: [ubl-ndrsc] Proposed Modification to [ELN4] - ASBIE Naming

[Grimley Michael J NPRI <GrimleyMJ@Npt.NUWC.Navy.Mil>]

> shouldn't
> <xsd:element name="InvoiceLegalTotal" type="cat:LegalTotal"/>
> be
>
> <xsd:element name="InvoiceLegalTotal" type="cat:LegalTotalType"/>

Yep, my bad.

> The type of an ASBIE is always the type of 
> the ABIE being associated with.

I agree; aside from my typo, that's what I indicated.

> the point i was trying to make in my earlier email was that 
> InvoiceLegalTotal is a legitimate re-use of the LegalTotal (in a 
> specific context).

I understand the point of your last email; unfortunately, we currently have a rule that states that a global element must be declared for all ASBIEs. The purpose of the modification to the naming rule is simply to prevent name collisions with the globally declared ABIE that corresponds to the ASBIE's type.



-----Original Message-----
From: Tim McGrath [mailto:tmcgrath@portcomm.com.au]
Sent: Wednesday, 21 January 2004 20 54
To: Grimley Michael J NPRI
Cc: UBL-NDRSC (E-mail)
Subject: Re: [ubl-ndrsc] Proposed Modification to [ELN4] - ASBIE Naming


the point i was trying to make in my earlier email was that 
InvoiceLegalTotal is a legitimate re-use of the LegalTotal (in a 
specific context).  we will never want to reuse InvoiceLegalTotal in any 
other place because it describes a unique association.  The qualifiers 
should not be part the type.  The type of an ASBIE is always the type of 
the ABIE being associated with.
this rule reads like a reverse engineering of the schemas rather than a 
logical interpretation of the principles behind it.

PS

shouldn't
<xsd:element name="InvoiceLegalTotal" type="cat:LegalTotal"/>
be

<xsd:element name="InvoiceLegalTotal" type="cat:LegalTotalType"/>


Grimley Michael J NPRI wrote:

>[ELN4] A UBL global element name based on an ccts:ASBIE MUST be the
>ccts:ASBIE dictionary entry name property term and qualifiers; and the
>object class term and qualifiers of its associated ccts:ABIE. All
>ccts:DictionaryEntryName separators MUST be removed.
>
><New>If the omission of the ccts:ASBIE dictionary entry name object class
>term results in a name collision then the ccts:ASBIE dictionary entry
>name object class term MUST be added to the beginning of the element name.</New>
>
>Redundant words in the ccts:ASBIE property term or qualifiers and the
>associated ccts:ABIE object class term or qualifiers MUST be dropped <New>unless
>the result produces a name collision</New>.
>
>
>
>EXAMPLES:
>====================================
>With object class:
>
><xsd:element ref="InvoiceLegalTotal">
>  <xsd:annotation>
>    <xsd:documentation>
>      <ccts:Component>
>        <ccts:CategoryCode>ASBIE</ccts:CategoryCode>
>        <ccts:DictionaryEntryName>Invoice. Legal Total</ccts:DictionaryEntryName>
>        <ccts:Definition>Associates the invoice with a set of totals...</ccts:Definition>
>        <ccts:ObjectClass>Invoice</ccts:ObjectClass>
>        <ccts:PropertyTerm>LegalTotal</ccts:PropertyTerm>
>        <ccts:RepresentationTerm>LegalTotal</ccts:RepresentationTerm>
>        <ccts:DataType>LegalTotal.Type</ccts:DataType>
>        <ccts:AssociatedObjectClass>LegalTotal</ccts:AssociatedObjectClass>
>      </ccts:Component>
>    </xsd:documentation>
>  </xsd:annotation>
></xsd:element>
>
>Because there is already a Global Element named 'LegalTotal' in the Reusable schema, and we add no additional qualifiers, we will have a name collision if we don't include the Object Class. Therefore, ASBIE Global Element Name becomes 'InvoiceLegalTotal'. (Yes, Gunther, this is a direct result of our Global Element decision.):
>
><xsd:element name="InvoiceLegalTotal" type="cat:LegalTotal"/>
>
>====================================
>Without object class:
>
><xsd:element ref="AdditionalDocumentReference" minOccurs="0" maxOccurs="unbounded">
>  <xsd:annotation>
>    <xsd:documentation>
>      <ccts:Component>
>        <ccts:CategoryCode>ASBIE</ccts:CategoryCode>
>        <ccts:DictionaryEntryName>Invoice. Additional_  Document Reference. Document Reference</ccts:DictionaryEntryName>
>        <ccts:Definition>Provides other means of identifying an Invoice </ccts:Definition>
>        <ccts:ObjectClass>Invoice</ccts:ObjectClass>
>        <ccts:QualifierPropertyTerm>Additional</ccts:QualifierPropertyTerm>
>        <ccts:PropertyTerm>DocumentReference</ccts:PropertyTerm>
>        <ccts:RepresentationTerm>DocumentReference</ccts:RepresentationTerm>
>        <ccts:DataType>DocumentReference.Type</ccts:DataType>
>        <ccts:AssociatedObjectClass>DocumentReference</ccts:AssociatedObjectClass>
>      </ccts:Component>
>    </xsd:documentation>
>  </xsd:annotation>
></xsd:element>
>
>Because we have the qualifier 'Additional', we have no need to include the Object Class in order to prevent name collision with global 'DocumentReference' in Reusable:
>
><xsd:element name="AdditionalDocumentReference" type="cat:DocumentReferenceType"/>
>
>
>
>
>
>
>
>
>
>To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/ubl-ndrsc/members/leave_workgroup.php.
>
>  
>

-- 
regards
tim mcgrath
phone: +618 93352228  
postal: po box 1289   fremantle    western australia 6160