[
Lists Home |
Date Index |
Thread Index
]
Paul,
Regarding your original question of:
<Question>
I don't know of any attempts to standardise
such a format. Is there any activity in this direction? If
not, I shall try to start one through the OASIS e-Government
TC.
</Question>
You may want to become familiar with the work that the OASIS UBL TC has
done in this area (I was a TC member until a recent employment switch).
Specifically, the following:
(1) Eve Maler's position paper on representing codelists:
http://www.oasis-open.org/committees/ubl/ndrsc/pos/p-maler-codelists-09.pdf
(2) Codelist module schema template:
http://www.oasis-open.org/committees/ubl/ndrsc/current/CodeListModuleTemplate.xsd
Kind Regards,
Joe Chiusano
Booz | Allen | Hamilton
"Keith W. Boone" wrote:
>
> Another issue is that [some] coding systems change over time, so you would
> want to be able to record the time span for which a code is valid.
>
> Keith
>
> -----Original Message-----
> From: Michael Kay [mailto:michael.h.kay@ntlworld.com]
> Sent: Friday, November 22, 2002 4:48 AM
> To: 'Paul Spencer'; xml-dev@lists.xml.org
> Subject: RE: [xml-dev] Representing Code Lists
>
> Neither of these formats extends easily to allow multiple values for a
> given code, e.g. a short form and a long form, or an English form and a
> Welsh form (to be UK-parochial for once!). Nor do they allow multiple
> codes for the same value, e.g. two-letter and three-letter country
> codes: though you could decide that those should be in separate tables.
>
> Michael Kay
>
> > -----Original Message-----
> > From: Paul Spencer [mailto:ps@boynings.co.uk]
> > Sent: 21 November 2002 21:45
> > To: xml-dev@lists.xml.org
> > Subject: [xml-dev] Representing Code Lists
> >
> >
> > In government work, it is frequently necessary to use
> > standard codes. When displaying a document using such codes,
> > it would be useful to have a standard format for representing
> > any such list. For example:
> >
> > <?xml version="1.0" encoding="UTF-8"?>
> > <ISO5218-1977 xmlns="http://example.com/namespace";>
> > <Value Code="1">male</Value>
> > <Value Code="2">female</Value>
> > <Value Code="9">not specified</Value>
> > </ISO5218-1977>
> >
> > or perhaps:
> >
> > <?xml version="1.0" encoding="UTF-8"?>
> > <List Codelist="ISO5218-1977" xmlns="http://example.com/namespace";>
> > <Value Code="1">male</Value>
> > <Value Code="2">female</Value>
> > <Value Code="9">not specified</Value>
> > </List>
> >
> > I see such lists being made publicly available (subject to
> > any IPR issues). I don't know of any attempts to standardise
> > such a format. Is there any activity in this direction? If
> > not, I shall try to start one through the OASIS e-Government
> > TC. In which case, which format is preferred? Or another one?
> >
> > Regards
> >
> > Paul Spencer
> >
> > -----------------------------------------------------------------
> > The xml-dev list is sponsored by XML.org
> > <http://www.xml.org>, an initiative of OASIS
> <http://www.oasis-open.org>
>
> The list archives are at http://lists.xml.org/archives/xml-dev/
>
> To subscribe or unsubscribe from this list use the subscription
> manager: <http://lists.xml.org/ob/adm.pl>
>
> -----------------------------------------------------------------
> The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
> initiative of OASIS <http://www.oasis-open.org>
>
> The list archives are at http://lists.xml.org/archives/xml-dev/
>
> To subscribe or unsubscribe from this list use the subscription
> manager: <http://lists.xml.org/ob/adm.pl>
>
> -----------------------------------------------------------------
> The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
> initiative of OASIS <http://www.oasis-open.org>
>
> The list archives are at http://lists.xml.org/archives/xml-dev/
>
> To subscribe or unsubscribe from this list use the subscription
> manager: <http://lists.xml.org/ob/adm.pl>
begin:vcard
n:Chiusano;Joseph
tel;work:(703) 902-6923
x-mozilla-html:FALSE
url:www.bah.com
org:Booz | Allen | Hamilton Inc.;IT Digital Strategies Team
adr:;;8283 Greensboro Drive;McLean;VA;22012;
version:2.1
email;internet:chiusano_joseph@bah.com
title:Senior Consultant
fn:Joseph M. Chiusano
end:vcard
|
