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] | [Elist Home]


Subject: Re: [ubl-ndrsc] Restrictions of BBIEs


There are a number of questions we need to ask:

- Should the UBL Library restrict the XSD simple types that underlie its 
BBIEs?  I assume the answer is "yes", otherwise we wouldn't have been 
interested in facet data in the spreadsheet.  (Right??)

- How should the UBL Library restrict these XSD datatypes?  Since I 
believe the simple types aren't directly bound to the content of a 
BBIE-related element but rather are applied as simpleContent when an 
element gets bound to a complex type, this gets complicated.  We've been 
assuming you can just bind ElementFoo to some CCTType and be done.  It 
may make more sense to build up the supplementary-component attributes 
into named groups, and reference them each time, along with associating 
the content of the element with the simple type directly.  Then we have 
a choice as to how to do the restriction: named and referenced vs. 
anonymous and in-place.  I suspect that named is better, along the lines 
of our "Garden of Eden" reusability approach so far.

(I'm sorry I don't have time to sketch examples of these possibilities, 
but I bet Gunther could do it easily...)

	Eve

Stuhec, Gunther wrote:
> Hello Mark,
> 
> one example:
> 
> I have BCC named "Article. Identifier". This "Identifier" do not have any restrictions. But sometimes, I will use this "Article. Identifier" for an EAN.UCC-13 with a fixed length of 13 digits. Therefore, it will be an advantage to restrict the length of the derived BIE like:
> 
> EAN-13. Article. Identifier
> 	length= 13
> 
> Kind regards,
> 
> 	Gunther
> 
> 
> -----Original Message-----
> From: CRAWFORD, Mark [mailto:MCRAWFORD@lmi.org]
> Sent: Donnerstag, 31. Oktober 2002 17:10
> To: UBL Design Rules (E-mail)
> Subject: RE: [ubl-ndrsc] Restrictions of BBIEs
> 
> 
> Gunter,
> 
> I am not sure how you would cause a restriction in a BCC.  Please explain.
> 
> Mark
> 
> 
> 
>>-----Original Message-----
>>From: Stuhec, Gunther [mailto:gunther.stuhec@sap.com]
>>Sent: Wednesday, October 30, 2002 4:59 PM
>>To: UBL-NDRSC (E-mail)
>>Subject: [ubl-ndrsc] Restrictions of BBIEs
>>
>>
>>Hello all,
>>
>>a resctriction of BCC is very simple. However, in the case of 
>>BBIEs they may be a requirement to have more than one 
>>restriction. This can be achieved by copying the entire tuple 
>>(complexType/simpleType) into a new one for the relevant 
>>BBIE. However, changes could be made inside of the specific 
>>BCC. This change can't impact the copied BBIE. We need to 
>>resolve this problem. Do have any ideas.
>>
>>Kind regards,
>>
>>	Gunther

-- 
Eve Maler                                        +1 781 442 3190
Sun Microsystems                     NEW!!! cell +1 781 354 9441
Web Technologies and Standards               eve.maler @ sun.com



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


Powered by eList eXpress LLC