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


Help: OASIS Mailing Lists Help | MarkMail Help

codelist-comment message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: The basic structure of the lists

  As a person who would need to convert the lists to be used by other
applications, I have some concerns over the structure of the lists in
terms of the XML.

  In order to get values from any list the xpath required would need to
be complex in terms of looking for an appropriate attribute that given
that name of the value and then fetching the value from a related

  This gives you a flexible structure for defining data but it does not
allow schemas to provide validation of content or for applications to
easily pickout the required data.

  I would have prefered the use of something like 


  Rather than

  <Value type="numericode">1</Value>  (yes I know this is not an exact
example from the document)

  The later form would not be able to be validated by a schema and
therefore it would be possible to have the word numericode spelt
incorrectly and the list would be broken.  There are tools which can
help in this kind of thing (CAM, Schematron) but it would be better to
have a structure that made the best use of native XML rather than this
current open schema approach.

  One was round the need to allow flexibility of the names for value
types would be to have a schema structure that others could use to
define elements that could become legitimate children of the value or
row structures. 

Martin Roberts

-----Original Message-----
From: Anthony B. Coates (Miley Watts) [mailto:abcoates@mileywatts.com] 
Sent: 18 May 2007 11:12
To: Comments to OASIS Code List Representation TC
Subject: [codelist-comment] Committee draft of genericode 1.0 does not
support xml:base

The committee draft of genericode 1.0 does not support xml:base.  It
should be modified to do so.  The difficulty is that genericode
documents potentially contain two kinds of URLs:

1. those used as URIs to identify code lists, etc.; 2. those used as
suggested locations for retrieving other documents.

The appropriate bases for these two groups may sometimes be the same,
but certainly won't always be the same.  As such, a choice needs to be
made about which group to which to apply xml:base.  It is recommended
that the second group of URLs, location URLs, are the ones to which
xml:base applies.  Additionally, the spec should be tightened to say
that canonical URIs (for identifying code lists and their versions,
etc.) must be absolute URIs and not relative URIs.

Cheers, Tony.
Anthony B. Coates
Senior Partner
Miley Watts LLP
Experts In Data
+44 (79) 0543 9026
Data standards participant: genericode, ISO 20022 (ISO 15022 XML),

To unsubscribe, e-mail:
For additional commands, e-mail:

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]