[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: [ubl-ndrsc] Restrictions of BBIEs
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 > > ---------------------------------------------------------------- > To subscribe or unsubscribe from this elist use the subscription > manager: <http://lists.oasis-open.org/ob/adm.pl> > ---------------------------------------------------------------- To subscribe or unsubscribe from this elist use the subscription manager: <http://lists.oasis-open.org/ob/adm.pl>
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC