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: RE: [codelist-comment] Re: Codelist usability issues - ease and performance design

OK - that is now much clearer - your explanation makes sense - many
thanks for taking the time to review this. 
In conclusion then - I would suggest that you make it very clear that
the purpose is design and that XML artifacts should not be seen as
runtime ready - only design tools - because I suspect many people are
going to think that they should use them "as is" in production
Thanks, DW

 -------- Original Message --------
Subject: [codelist-comment] Re: Codelist usability issues - ease and
performance design
From: "Anthony B. Coates (Miley Watts)" <abcoates@mileywatts.com>
Date: Wed, November 01, 2006 8:50 am
To: "David RR Webber (XML)" <david@drrw.info>, "Comments to OASIS Code
List Representation TC" <codelist-comment@lists.oasis-open.org>
Cc: "Code List Representation TC" <codelist@lists.oasis-open.org>

Dear David,

Thank you for your public comment regarding the OASIS Code List  
Representation TC work:


We discussed it by e-mail and at our last teleconference.  I am replying
on behalf of the TC.

It is always easiest to reply to specific comments about a specific  
version of specification (or draft thereof).  Your comments are more  
general in character.  For the most part, your comments appear to be  
targetted at people who are implementing run-time code list validation  
mechanisms.  Run-time validation mechanisms are outside of the scope of 

the current work of the TC.  The current work is focussed on modelling
encoding code lists for transmission between users and systems.  How  
implementers of run-time validation systems choose to use that code list
information, and represent it for run-time usage, is not in scope.  We  
expect there will be many ways that people will use this information
in repositories and database tables, encoded into XML Schemas and Java  
enumeration classes, etc.).

We discussed your comments about constructing XML documents so that they
are composed of logical parts that can be externally referenced.  We
that these comments apply to XML generally, not to code lists in  
particular.  As such, this TC isn't planning to define a generic
of that sort (nor software to support that mechanism).  We are potential
users of such mechanisms defined elsewhere (including XInclude, for  

Note that we have just published our requirements document for informal 

public review


and that this document references materials that have been contributed
the TC as an input (see



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

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

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