[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [ubl-lcsc] Rule 115 a - d Containership - Joint Discussion for LCSC and NDRSC
Lisa, I will be enroute to Seoul and unavailable. I will review the recommendation and try and submit comments before the meeting. Mark Crawford Research Fellow - LMI XML Lead W3C Advisory Committee, OASIS, RosettaNet Representative Vice Chair - OASIS UBL TC & Chair Naming and Design Rules Subcommittee Chair - UN/CEFACT XML Syntax Working Group Editor - UN/CEFACT Core Components ______ Logistics Management Institute 2000 Corporate Ridge, McLean, VA 22102-7805 (703) 917-7177 Fax (703) 917-7481 Wireless (703) 655-4810 mcrawford@lmi.org http://www.lmi.org "Opportunity is what you make of it" -----Original Message----- From: Lisa-Aeon <lseaburg@aeon-llc.com> To: UBL-NDR <ubl-ndrsc@lists.oasis-open.org>; Ubl-Lcsc <ubl-lcsc@lists.oasis-open.org> Sent: Tue Aug 19 13:02:25 2003 Subject: [ubl-lcsc] Rule 115 a - d Containership - Joint Discussion for LCSC and NDRSC Following discussion on today's LCSC teleconference call I would like to bring the following to your attention. The following containership rules are on HOLD (since the Montreal meeting). LCSC would like to set up a series of joint meetings between LCSC and NDR on Sept 9 and Sept 10. During those meetings, LCSC will present the group with their findings, including a position paper regarding the issue along with examples. There will be time allotted for discussion. Please be available to attend these meetings. Quorum is important (as always) and your opinion needs to be heard while the issue is on the table. Thank you. Lisa FYI - Rules as they stand today: [R 115a] All non-repeatable BIEs that are direct children of the document-levelBIE in the model will be child elements of a generated "Top" element in the schema. The generated "Top" element will be named "[doctype]Top", and its content model will be a sequence. It will reference a generated type named"[doctype]TopType". Both the generated "Top" element and its type will be declared in the same namespace as the document-level element. (Note: This rule implies that all documents will have generated "Top" elements, without exception, regardless of their other 'body' contents, to cover cases where the document will be extended with the Context mechanism, and for general consistency.) [R 115b] All repeatable BIEs in the model will have generated containers. The containers will be named "[name_of_repeatable_element]List". These containers will be required if the cardinality of their contained immediate children requires at least one; if their contained children are optional;the container itself will be optional. At least one of the repeatable children of the List will always be required, but there may be more than one required child if that agrees with the cardinality found in the businessmodel.All "_____List" elements will reference a "_______ListType", which will be declared in the same namespace as the element that represents the repeatable BIE in the business model. The content model of this type will have a single child element, which will have a maximum occurrence that reflects the maximum occurrence in the business model, and a minimum occurrence as described in this rule, above.(NOTE: This rule applies equally to 'list' containers at the document level,and also at lower levels within the document.) [R 115c] The document element in the schema will have a content model that is a sequence of elements, the first of which will be the "Top" element, and the others will be the generated "List" elements, in the order in which their contained, repeatable children appeared in the model. [R 115d] All elements in the generated schema that are direct children of the generated "top" elements in all documents should be gathered together into a common aggregate type, named "TopType", which will be declared in the CommonAggregate Types namespace. This type should be declared abstract, and all document headers should be extensions - even if only trivial extensions to facilitate re-naming - of this abstract type. (Note: This rule allows for polymorphic processing of the set of generic header elements across all document types.) ++++++++++++++++++++++++++++++++++++++++++++++++++++ Lisa Seaburg AEON Consulting Website: http://www.aeon-llc.com Email: lseaburg@aeon-llc.com Alternative Email: xcblgeek@yahoo.com Phone: 662-562-7676 Cellphone: 662-501-7676 "If you obey all the rules, you miss all the fun." -Katharine Hepburn ++++++++++++++++++++++++++++++++++++++++++++++++++++ --- File has not been scanned Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.510 / Virus Database: 307 - Release Date: 8/14/2003
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]