[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [ubl-lcsc] UBL Schema 1.0-alpha draft-1 20030918 (With Draft CodeList Schemas)
Lisa This is because we should have the in-use (default) codelist schemas named *Use* and the imports named the same. Once Chee-Kai fixes this (and we fix a couple of model things like GUID) it'll all work a lot better. Steve >>> "Lisa-Aeon" <email@example.com> 19/09/03 16:05:52 >>> I have been going through the last draft, I have a few issues. Maybe its my use of the tools, but I keep getting multiple "Can not open file" messages and its mostly the codelist files. Is there a quick way to fix that? Also, our document structure is still so dang flat - open a document and get a thousand elements in your face. None of what NDR was trying to say about containers sunk in I guess. I am just listing my objection to a very ugly document design here. Lisa ----- Original Message ----- From: "G. Ken Holman" <gkholman@CraneSoftwrights.com> To: "UBL LCSC" <firstname.lastname@example.org> Sent: Friday, September 19, 2003 8:04 AM Subject: Re: [ubl-lcsc] UBL Schema 1.0-alpha draft-1 20030918 (With Draft CodeList Schemas) > This is looking good, Chee-Kai! But I do see some issues to be addressed. > > At 2003-09-19 11:16 +0800, Chin Chee-Kai wrote: > >Here's an implementation of UBL Schema 1.0-alpha draft-1 20030918, > >with codelist schemas, placebos and stocks, included. > > (1) I don't see any "Standard" definitions. One thing that has been > overlooked in this implementation of the design is that the design > distinguishes all code lists as *either* standard or placebo, and the > in-use schema is the one of these that is defined for the code list. > > The stock definitions only apply for those code lists with placebo definitions. > > When looking at the complete selection of code lists you will not see > either a placebo definition or stock definition for those that have a > standard definition. > > For example, I note from your catalogue XML that "chn" is > standard. Therefore, in the list of XSD files I would see "chn-Use-" and > "chn-Standard-" but not any others for "chn" ... and I suspect the > "chn-Stock-" that I do see you have created is the correct content for the > "chn-Standard-" file. > > (2) In your catalogue XML I note that "acc" has a stock > definition. Therefore, I would expect to see "acc-Use-" and "acc-Placebo-" > (both of those being the same content) and then an additional "acc-Stock-" > definition with the stock values. I *do* already see the Placebo and Stock > definitions, so all that is missing is the "-Use-". > > All of the XSD schemaLocation= attributes pointing to code lists in the > import statements of Reusable should be using the "-Use-" filename. > > (3) In your catalogue XML I note that "cnt" has an external > definition. Therefore I would expect to see "cnt-Use-" and "cnt-Placebo-" > (both of those being the same content), and (eventually, I realize you may > not have done externals yet) the "cnt-Stock-" synthesized from the XSLT > stylesheet using "cnt-Placebo-" as the main source and > "http://www.unece.org/etrades/unedocs/repository/codelists/xml/CountryCode.x sd" > as the input of enumerations (which would be somewhere in the spreadsheet > and your catalogue XML. > > >Couple of notes (please refer to the XML CodeListCatalogue): > > > >- Stock codelist schemas are generated whenever there are > > values in "Actual Values" field. > > True, but also Stock code list definitions are also generated whenever > there is an external definition. > > >Internationlisation of > > externally defined codelists are still in stage of discussion. > > So they (and what these happen to be) are yet to be defined > > and included. > > Ahhhhh ... thank you ... that addresses a couple of my points above. > > >- I've inserted <ccts:Instance> info into Placebo and Stock codelists > > as per other Reusable and Document schemas, in anticipation that > > they might be useful (since the prefix information is associated > > with codelists anyway). But let me know if they're not really > > useful and I could remove them in draft-2. > > > >- Private adjunct schema isn't included. > > Nor would they ever be by us ... private-use files will all be generated by > implementers and end-users. > > Thanks, Chee-Kai, I hope these comments help. > > ......................... Ken > > -- > Next public US delivery: 3-day XSLT/2-day XSL-FO 2003-10-13 > Next public European delivery: 3-day XSLT/2-day XSL-FO 2003-11-?? > Instructor-led on-site corporate, government & user group training > for XSLT and XSL-FO world-wide: please contact us for the details > > G. Ken Holman mailto:gkholman@CraneSoftwrights.com > Crane Softwrights Ltd. http://www.CraneSoftwrights.com/o/ > Box 266, Kars, Ontario CANADA K0A-2E0 +1(613)489-0999 (F:-0995) > ISBN 0-13-065196-6 Definitive XSLT and XPath > ISBN 0-13-140374-5 Definitive XSL-FO > ISBN 1-894049-08-X Practical Transformation Using XSLT and XPath > ISBN 1-894049-11-X Practical Formatting Using XSL-FO > Member of the XML Guild of Practitioners: http://XMLGuild.info > Male Breast Cancer Awareness http://www.CraneSoftwrights.com/o/bc > > > To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/ubl-lcsc/members/leave_workgroup.php. > --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.515 / Virus Database: 313 - Release Date: 9/1/2003 To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/ubl-lcsc/members/leave_workgroup.php.