Updating the cardinalities for the next review

["G. Ken Holman" <gkholman@CraneSoftwrights.com>]

It turns out that no decision was made regarding the cardinality 
problems that were reported earlier.

Below I have a more refined list based on important observations made 
by Tim (thanks!).

I've made the assumption that every element with one of the following 
property term nouns is a prose BBIE ... can anyone think of any others?

   Comments       Conditions  Description   Information  Instructions
   Justification  Note        Purpose       Reason       Remarks
   Requirements   Resolution  Restrictions  Situation    Risk
   Terms

The first list is where I intend to change "0..1" and "1" to, 
respectively, "0..n" and "1..n".  I think that change is easy and 
important to accommodate languages.

The second list are candidates to change "0..n" and "1..n" to, 
respectively, "0..1" and "1".  But I'm not convinced I can simply 
change them without violating the semantics of the construct.  So I'm 
leaving them untouched unless someone tells me which ones can change.

Would all members involved in model design please review the second 
list and tell me if any of them should be limited to one in their 
maximum count?

Thank you for your help with this.

. . . . . . . . . Ken


*..1 Cardinalities found on prose text BBIEs: 36 (13 old; 23 new)

"Allowance Charge. Allowance Charge_ Reason. Text" (old): 0..1
"Certificate. Remarks. Text" (new): 0..1
"Consignment. Carrier Service_ Instructions. Text" (new): 0..1
"Consignment. Customs Clearance Service_ Instructions. Text" (new): 0..1
"Consignment. Forwarder Service_ Instructions. Text" (new): 0..1
"Consignment. Handling_ Instructions. Text" (new): 0..1
"Consignment. Information. Text" (new): 0..1
"Consignment. Special Service_ Instructions. Text" (new): 0..1
"Consumption Average. Description. Text" (new): 0..1
"Consumption Correction. Description. Text" (new): 0..1
"Consumption Point. Description. Text" (new): 0..1
"Despatch Line. Backorder_ Reason. Text" (old): 0..1
"Despatch Line. Outstanding_ Reason. Text" (old): 0..1
"Exception Notification Line. Description. Text" (new): 0..1
"Forecast Revision Line. Description. Text" (new): 0..1
"Fulfilment Cancellation. Cancellation_ Note. Text" (new): 1
"Item Management Profile. Replenishment Owner Description. Text" (new): 0..1
"Location. Conditions. Text" (old): 0..1
"On Account Payment. Note. Text" (new): 0..1
"Order Cancellation. Cancellation_ Note. Text" (old): 1
"Order Response Simple. Rejection_ Note. Text" (old): 0..1
"Packing List. Description. Text" (old): 0..1
"Party Tax Scheme. Exemption_ Reason. Text" (old): 0..1
"Receipt Line. Reject_ Reason. Text" (old): 0..1
"Retail Event. Description. Text" (new): 0..1
"Shipment Stage. Demurrage_ Instructions. Text" (new): 0..1
"Shipment Stage. Instructions. Text" (new): 0..1
"Shipment. Handling_ Instructions. Text" (old): 0..1
"Tax Category. Tax Exemption Reason. Text" (old): 0..1
"Telecommunications Supply Line. Description. Text" (new): 0..1
"Transport Equipment. Description. Text" (new): 0..1
"Transport Equipment. Information. Text" (old): 0..1
"Transport Equipment. Special_ Transport Requirements. Text" (new): 0..1
"Transport Execution Plan Request. Document Status Reason 
Description. Text" (new): 0..1
"Transport Execution Plan. Document Status Reason Description. Text" 
(new): 0..1
"Transport Handling Unit. Handling_ Instructions. Text" (old): 0..1


*..n Cardinalities found on new non-prose text BBIEs: 39 (28 new)

"Awarding Criterion. Calculation Expression. Text" (new): 0..n
"Awarding Criterion. Minimum Improvement Bid. Text" (new): 0..n
"Awarding Criterion. Weight. Text" (new): 0..n
"Clause. Content. Text" (new): 0..n
"Contract Award Notice. Regulatory Domain. Text" (new): 0..n
"Contract Notice. Regulatory Domain. Text" (new): 0..n
"Contracting Party. Activity Type. Text" (new): 0..n
"Contracting Party. Contracting Party Type. Text" (new): 0..n
"Evaluation Criterion. Expression. Text" (new): 0..n
"Evidence. Candidate_ Statement. Text" (new): 0..n
"External Reference. Hash Algorithm Method. Text" (new): 0..n
"Framework Agreement. Frequency. Text" (new): 0..n
"Item Property. List Value. Text" (new): 0..n
"Item Property. Value Qualifier. Text" (new): 0..n
"Meter Property. Value Qualifier. Text" (new): 0..n
"Meter Property. Value. Text" (new): 0..n
"Party Legal Entity. Company Legal Form. Text" (new): 0..n
"Requested Tender Total. Monetary Scope. Text" (new): 0..n
"Service Provider Party. Service Type. Text" (new): 0..n
"Tender Line. Orderable_ Unit. Text" (new): 0..n
"Tender Receipt. Contract Name. Text" (new): 0..n
"Tender. Contract Name. Text" (new): 0..n
"Tenderer Qualification Request. Company Legal Form. Text" (new): 0..n
"Tenderer Qualification Response. Contract Name. Text" (new): 0..n
"Tendering Terms. Funding_ Program. Text" (new): 0..n
"Tendering Terms. Penalty Clauses. Text" (new): 0..n
"Utility Item. Subscriber Type. Text" (new): 0..n
"Work Phase Reference. Work Phase. Text" (new): 0..n

--
Contact us for world-wide XML consulting and instructor-led training
Free 5-hour lecture: http://www.CraneSoftwrights.com/links/udemy.htm
Crane Softwrights Ltd.            http://www.CraneSoftwrights.com/o/
G. Ken Holman                   mailto:gkholman@CraneSoftwrights.com
Google+ profile: https://plus.google.com/116832879756988317389/about
Legal business disclaimers:    http://www.CraneSoftwrights.com/legal