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] Schema Review: ASBIE Element Creation Rule


Michael wrote:
> We have a rule that states:
>         [ELN3]A UBL global element based on an ccts:ASBIE MUST be
>         declared and bound to the xsd:complexType of its associated
>         ccts:ABIE.
> I believe that what was expected was something like this:
>         <xsd:element name="ReceiptDocumentReference" 
> type="cat:DocumentReferenceType"/>        
Exactly what we intended by the rule - there would be a separate element declaration for every ASBIE.

> However, in those cases where direct reuse of the global 
> element (ABIE), declared in the Reusable schema, makes sense, 
> we find something like this:
>         <xsd:element ref="cat:LegalTotal"/>
>                    instead of
>         <xsd:element name="InvoiceLegalTotal" 
> type="cat:LegalTotalType"/>
> Obviously, a global element *is* being declared and it *is* 
> bound to type 'cat:LegalTotalType', albeit indirectly through 
> the reference to the element 'cat:LegalTotal'.
> I agree with Tim, that this is an appropriate reuse of the 
> reusable 'cat:LegalTotal' element. If no one expresses any 
> differing opinions, we (QA) will accept it as conformant to our NDR.

Isn't this reuse confusing?  Yes you can do it this way, but it becomes ambiguous as to what is being used - an ABIE or an ASBIE.


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