ubl — archive

[Jon Bosak]

Western hemisphere participants: Note that this meeting takes place Monday evening in your time zones. AGENDA FOR PACIFIC UBL TC MEETING 00:30 - 02:30 UTC TUESDAY 16 SEPTEMBER 2008 http://www.timeanddate.com/worldclock/fixedtime.html?month=9&day=16&year=2008&hour=0&min=30&sec=0 STANDING CON CALL NUMBER Skype: +9900827043982678 US/Canada toll-free: 1-888-350-0075 International: 201-793-9022 Conference Room Number: 3982678 then # (this applies only if dialing in) MINUTES OF THE UBL TC MEETING IN MONTRÉAL Pending. STANDING ITEMS Additions to the calendar: http://ubl.xml.org/events Liaison reports Subcommittee report: PSC Subcommittee report: TSC Review of Atlantic call minutes INTERNATIONAL DATA DICTIONARY Status, etc. UBL WORK SCHEDULE ACTION (1/8): JB to revise the work schedule spreadsheet. Pending finalization of the BII schedule this month. CUSTOMIZATION GUIDELINES Status, etc. UBL 2.1 ISSUES LIST ACTION (12/18): TM to populate the new issues list with all currently known UBL 2.1 issues. Pending. NAMING AND DESIGN RULES There are several questions that need to be answered before we can complete this editing cycle. 1. Regarding this leftover issue from NDR 2.0: http://lists.oasis-open.org/archives/ubl/200803/msg00001.html - Do these code list metadata items belong in Section 6 on code lists (as Ken has suggested) or among the instance constraints in section 8? - Are these new NDR rules? If so, I will need to assign either CDLx or INDx identifiers, depending on the answer to the first question. 2. Regarding this tracking item (minutes of Pacific call 1 July 2008): / ============================================================= | Regarding NDR and order of BBIEs in advance of ASBIEs: this | is not a rule, just a pattern. | | TM: This is a modeling policy established in order to | maintain a logical sequence as items are added in subsequent | revisions (so that we are not simply adding everything new | at the end). The schema should express the logical sequence | of the model. | | AGREED to add an editorial note to this effect in the NDR | document. \ ============================================================= I'm not clear on why exactly we need to say this and where it would go. The relevant section in the NDR draft is 3.1, Overall Schema Structure, and the only rule is, [GXS1]Except in the case of extension, where the "UBL Extensions" element is used, UBL schemas SHOULD conform to the following physical layout as applicable: It's in the figure that follows that the order of ABIEs and BBIEs is given. Seems to me that the "SHOULD" in the rule covers what we want to say here; is there something I'm missing? 3. Questions about several examples (text of each is given at the end of this agenda). Example 1 - Wouldn't it make more sense if addresstype came first, then address, then partytype? - Are addresstype and partytype actually children of party? - Where is the end tag for the party element? [Answer from BH: I think you are correct because the NDR says that components should be an alphabetical order - not 100% sure though.] Example 2 - Is