OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   Re: [xml-dev] Representing Code Lists

[ Lists Home | Date Index | Thread Index ]

Hi Paul,

The OASIS ebXML Registry specification describes a more general taxonomy 
representation model where a  ClassificationScheme can be used to 
represent a Code List and ClassificationNodes may be used to define a 
flat or hierarchical structure within a ClassificationScheme to 
represent the values in that code list.

The registry performs validation of proper usage of code list values in 
other documents. The code values may be used to classify or categorize  
arbitrary content (e.g. an OAG BOD, an XML Schema etc.) . Such 
classification information may then be used to discover the classified 
content using ad hoc queries in XML as well as SQL query syntax.

The OASIS ebXML Registry specification V2.1 is an approved OASIS 
standard and may be found at:


An royalty free implementation of ebXML Registry V2.1 may be found at:


Work is underway on V3 of the ebXML Registry specifications which 
defines several important features:

-Automatic content validation and cataloging

-Cooperating registry federations

-RESTful interface

The open source implementation provides many of the V3 features already.


Paul Spencer wrote:

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


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS