[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [ubl-fpsc] FPSC responsibilities regarding code lists
Ken / All Hi I don't know much about it (which might force me to keep things simple which might be good) but in producing sample instances, I would like to merely use the UNECE guidelines at: http://www.unece.org/etrades/unedocs/codelistintegration.htm (I really love their site with its webservices and all) We need to prove that things can be kept fairly simple. Maybe I'll have changed my tune by the time I've tried adding codelists to the instances. Should codelist data appear in the forms? I would have thought a simple drop down box in an input form is the best way to demo a codelist but we aren't at the stage of input forms yet. As far as a display form is concerned, I don't see that codelists make any difference, except that we might want to display both the code and the codelist scheme name in some way. I would think that a typical sample implementation would be limited to the use of just one scheme (same as used on UN eDocs site) so the codelist scheme name might be just displayed as explanatory text on the form beside the code. All the best Steve >>> "G. Ken Holman" <gkholman@CraneSoftwrights.com> 07/08/03 01:45 AM >>> Hello all, This is input into our discussion Thursday regarding code lists ... we have to try and think up what it means to say regarding a code list "how it looks and works", and what readers of our formatting specifications need to know about code lists. If someone thinks they have a good handle on what we could say, could they step forward and volunteer to write a position paper from FPSC for us all to review? I'm not sure what more we could say than "the schema defines an enumeraton that is available to be used when presenting information that include coded values". This discussion would be separate from stylesheets, as a stylesheet fragment that "implemented" code lists would be created out of what we say in FPSC regarding code lists. Please speak up if you can think of anything! Thanks ................... Ken At 2003-07-07 15:49 -0500, Lisa-Aeon wrote: >From: "G. Ken Holman" <gkholman@CraneSoftwrights.com> > > At 2003-07-03 09:11 -0500, you wrote: > > >With all of the schema that is > > >coming out right now it would be great to somehow include this...... > > > > Sure ... I can transform the schema into lookup tables for use by the > > stylesheets. Were you thinking of anything more extensive than that? >... > >LISA: I am not sure what I am looking for, mostly a way to tie this into >the 0p80 schema as part of a sample, for people to see how it looks and >works. Should be something simple. -- Upcoming hands-on courses: in-house corporate training available; North America public: XSL-FO Aug 4,2003; XSLT/XPath Aug 12, 2003 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 You may leave a Technical Committee at any time by visiting http://www.oasis-open.org/apps/org/workgroup/ubl-fpsc/members/leave_workgroup.php
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]