Re: [ubl-lcsc] Code Lists Redux

["G. Ken Holman" <gkholman@CraneSoftwrights.com>]

At 2003-07-21 21:13 +0100, Anthony B. Coates wrote:
>** Reply to message from "G. Ken Holman" <gkholman@CraneSoftwrights.com> on
>Mon, 21 Jul 2003 12:10:53 -0400
> > Are there any thoughts of introducing normative code list XSD files in the
> > LCSC collection of files?
>
>The only thing LCSC could produce is a normative set of out-of-date code 
>lists,
>e.g. the normative LCSC set of last year's currencies.

Well said.

>I just don't see this working.

I can understand ...

>My view is that the only solution is to allow dynamic code lists
>...
>I would expect private companies to provide such lists, possibly for a fee

So, then, would the LCSC publish the UBL code list guidelines for other 
companies and include FPSC expectations in the guidelines?  FPSC would then 
document along the lines of "when using an XSD following the UBL Code List 
Guidelines document, these formatting specifications expect to find ...".

Is that a logical conclusion, then?

Thanks, Tony, for your perspective on this!

............. Ken


--
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