Re: [ubl-dev] problem cardinality

[elisa blasi <elisablasi@gmail.com>]

Hi Ken,
thanks for the reply even if not everything is clear to me.
First what do you mean with the statement '... that "choice" constructs would not be used when expressing the spreadsheets as schema constraints', to which spreadsheet are you referring to?

I understand the UBL schemas have to support 
all general cases and that it's up to the interacting partners to define
 constraints and rules. In my question I was simply highlighting that, 
even if reasonable that the 2 indicated elements have a cardinality 0-1,
 at the least of them has to be present otherwise, to my understanding, 
the UBL document would have no recipient. Did I correctly understand?
TIA, cheers
   Elisa

2010/11/3 G. Ken Holman <gkholman@cranesoftwrights.com>

In the original design of the UBL Naming and Design Rules, it was decided that "choice" constructs would not be used when expressing the spreadsheets as schema constraints.

Thus, where two trading partners agree that in their situation the two items are mutually exclusive, they impose business rules on top of the schema rules that check that one of the two are specified and not both and not neither.

The UBL structures convey the content of the document from point A to point B, but for absolute generality for all communities adopting UBL, the standardized structures themselves are rather loose.  The community makes, or two trading partners make, it their own by layering on top their business requirements.

I hope this helps.

. . . . . . . . . . . Ken

p.s. interestingly, this NDR issue (among others) is under review in today's committee teleconference

At 2010-11-03 13:00 +0100, elisa blasi wrote:

Hi all,
I don't understand the cardinality of CarrierParty and FreightForwarderParty in the ForwardingInstructions document, that is 0...1.
 0..1 cardinality means that CarrierParty and FreightForwarderParty are optional fields. But CarrierParty and FreightForwarderParty are the receivers of ForwardingInstr. and I think that at least one of the two fields must be specified..
The only solution is to think that CarrierParty may be absent in the document when there is FreightForwarderParty : in this sense the cardinality of CarrierParty can be 0...1 ,and viceversa FreightForwarderParty may be absent in the document when there is CarrierParty ..but at least one of the two fields must be specified..
What is the meaning of this cardinality? Can you help me ??
Regards, elisa

--
Contact us for world-wide XML consulting & instructor-led training
Crane Softwrights Ltd.          http://www.CraneSoftwrights.com/u/
G. Ken Holman                 mailto:gkholman@CraneSoftwrights.com
Legal business disclaimers:  http://www.CraneSoftwrights.com/legal


---------------------------------------------------------------------
To unsubscribe, e-mail: ubl-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: ubl-dev-help@lists.oasis-open.org