[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: [ubl-ndrsc] Code list rules document
Here's my feedback: 1. 117-124 first and second-order code lists are introduced. The section goes on to give some detail about first-order code lists and their architecture -- but nothing further is said about second-order ones. Was this on purpose or just an oversight? 2. It's good that we've got an early section (3.2) specifying the correspondence between our representation and ebXML's. The table in section 3.2 is extremely valuable. Small point -- that table should have a caption (with number) for reference. 3. It's really good that you're using the ISO 3166-1 code list for illustration. Makes the work so much more defensible than it would otherwise be (if we chose to use a hypothetical). Question: does it actually work? i.e. did you actually test the proposal with the UNECE schema and the "template" and create instance documents to see if valid documents are validated and invalid ones are flagged as such? (I ask, since the illustration starting on line 210 has shorthands for readability). Reason I asked is 'cause I tried it for a few minutes the other day and ran into some validation problems with the UNECE schema. 4. line 314. It's good that you expunged all the uses of global elements from the architecture, yet let the audience know that they could define their own global elements all they want. 5. In section 4 "Rationale" each contender is evaluated against the requirements listed in section 4.1. For each contender in section 4.2 there is a section entitled "Derivation Opportunities" (these are in sections 4.2.*.3). Why is not "derivation opportunities" one of the "requirements" listed in section 4.1, scored in sections 4.2.*.4, and contributing to the total scores given in section 4.3? -----Original Message----- From: Eve Maler - Sun Microsystems [mailto:Eve.Maler@sun.com] Sent: Sunday, August 25, 2002 4:13 PM To: ubl-ndrsc@lists.oasis-open.org; ubl-comment@lists.oasis-open.org Subject: [ubl-ndrsc] Code list rules document I have managed to finish a real draft of the code list rules document. This document extracts and expands on the code list rules that were in the most recent public snapshot of the NDR document (draft 12). While there are a few outstanding issues, I think it's largely usable in its current state. I hope you all will give this a careful review, try it out, and send your comments in. In my current technical circumstances I'm unable to attach files to email messages -- perhaps a blessing! I have FTP'd the relevant files to both the NDR archive and the "current" directory (Mavis, could you please update the NDR portal?): http://www.oasis-open.org/committees/ubl/ndrsc/archive/wd-ublndrsc-codelist- 01.doc http://www.oasis-open.org/committees/ubl/ndrsc/archive/wd-ublndrsc-codelist- 01.pdf http://www.oasis-open.org/committees/ubl/ndrsc/archive/CodeListModuleTemplat e.xsd Thanks, Eve Eve Maler +1 781 442 3190 Sun Microsystems cell +1 781 883 5917 XML Web Services / Industry Initiatives eve.maler @ sun.com ---------------------------------------------------------------- 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