OASIS Code List Representation TC

I have been in discussion with the ICG group of UN/CEFACT, which is  
responsible for publishing CEFACT's code lists.  They would like to use  
genericode, but they have a requirement to be able to publish all of their  
code lists within a single XML document, so they can give their users a  
single file that avoids some of the version management issues that come  
with multiple files.  They still plan to make the individual code lists  
available in individual genericode files, but they want this option to  
have all in one file.

Personally, I think this is a reasonable request, and I would like to  
suggest doing it, perhaps as part of a small version 1.1 updated to CS  
1.0.  It involves adding the ability to embed a code list or column set  
document within a code list set document, and updating the specification  
to discuss the implications of doing that.

Please feel free to post your thoughts about this to the list (or to the  
comments list if you are not a member of the OASIS CLRTC).  Thanks,

Cheers, Tony.
-- 
Anthony B. Coates
Associate Director
Document Engineering Services (Limited)
UK: +44 (20) 8816 7700, US: +1 (239) 344 7700
Mobile/Cell: +44 (79) 0543 9026
Skype: abcoates
anthony.coates@documentengineeringservices.com
http://www.documentengineeringservices.com/

Strangely, I wanted to do this just a couple of days ago. Although I found a way around it, I would support the change. It seems to have some benefits with no downside.

Regards

Paul

> 

                                                

					
                                                    

        
                                                
				
                                                

                                                    
                                                        
                                                        Original Message
                                                
                                                Original Message-----
> From: Anthony B. Coates (Document Engineering Services)
> [mailto:anthony.coates@documentengineeringservices.com]
> Sent: 03 April 2008 00:36
> To: Code List Representation TC
> Subject: [codelist] Genericode 1.1? - a request from CEFACT for embedded
> code lists in code list set documents
> 
> 
> I have been in discussion with the ICG group of UN/CEFACT, which is  
> responsible for publishing CEFACT's code lists.  They would like to use  
> genericode, but they have a requirement to be able to publish all 
> of their  
> code lists within a single XML document, so they can give their users a  
> single file that avoids some of the version management issues that come  
> with multiple files.  They still plan to make the individual code lists  
> available in individual genericode files, but they want this option to  
> have all in one file.
> 
> Personally, I think this is a reasonable request, and I would like to  
> suggest doing it, perhaps as part of a small version 1.1 updated to CS  
> 1.0.  It involves adding the ability to embed a code list or column set  
> document within a code list set document, and updating the specification  
> to discuss the implications of doing that.
> 
> Please feel free to post your thoughts about this to the list (or to the  
> comments list if you are not a member of the OASIS CLRTC).  Thanks,
> 
> Cheers, Tony.
> -- 
> Anthony B. Coates
> Associate Director
> Document Engineering Services (Limited)
> UK: +44 (20) 8816 7700, US: +1 (239) 344 7700
> Mobile/Cell: +44 (79) 0543 9026
> Skype: abcoates
> anthony.coates@documentengineeringservices.com
> http://www.documentengineeringservices.com/
> 
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  You may a link to this group and all your 
> TCs in OASIS
> at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php 
> 

I have no problems, Tony, with this and I am encouraged that such a 
change appears to be attractive to many parties.

Can you please propose a 1.1 document and associated schema?

Given that this does not make instances of genericode 1.0 
non-conformant with the 1.1 schema, I suggest we keep the namespace 
URI string the same (as we are doing in UBL with UBL 2.x 
versions).  Does anyone feel that we need to change the namespace URI 
string?  Recall the versioning policy in the namespace document itself:

   http://docs.oasis-open.org/codelist/ns/genericode/1.0/

. . . . . . . . . . Ken

At 2008-04-03 00:35 +0100, Anthony B. Coates (Document Engineering 
Services) wrote:
>I have been in discussion with the ICG group of UN/CEFACT, which is
>responsible for publishing CEFACT's code lists.  They would like to use
>genericode, but they have a requirement to be able to publish all of their
>code lists within a single XML document, so they can give their users a
>single file that avoids some of the version management issues that come
>with multiple files.  They still plan to make the individual code lists
>available in individual genericode files, but they want this option to
>have all in one file.
>
>Personally, I think this is a reasonable request, and I would like to
>suggest doing it, perhaps as part of a small version 1.1 updated to CS
>1.0.  It involves adding the ability to embed a code list or column set
>document within a code list set document, and updating the specification
>to discuss the implications of doing that.
>
>Please feel free to post your thoughts about this to the list (or to the
>comments list if you are not a member of the OASIS CLRTC).  Thanks,


--
Upcoming:  UBL Apr.22,24; genericode code lists Apr.23; Rome,Italy
World-wide corporate, govt. & user group XML, XSL and UBL training
RSS feeds:     publicly-available developer resources and training
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)
Male Cancer Awareness Nov'07  http://www.CraneSoftwrights.com/o/bc
Legal business disclaimers:  http://www.CraneSoftwrights.com/legal

On Fri, 04 Apr 2008 10:51:09 +0100, G. Ken Holman  

Apologies that I've been so slow moving on this.  I mentioned previous  
that UN/CEFACT ICG had request some additions to the genericode Schema.   
In particular, in the 1.0 Schema, a code list set can contain

  * code lists
  * references to code lists
  * references to other code lists sets

UN/CEFACT ICG would like us to add

  * code list sets (not just references)

To be complete, I think we could also add

  * column sets (external definitions of columns and keys)
  * references to column sets

I have a prototype Schema that supports this, and am working on a set of  
examples to demonstrate the different ways code list sets can be  
constructed.  While doing that, I have found a bug in the genericode 1.0  
Schema.

In the 1.0 Schema, a code list reference contains

  * a mandatory canonical URI
  * an optional canonical version URI
  * any number of location URIs

A code list set reference contains exactly the same.

However, a column set reference contains

  * a mandatory canonical version URI
  * any number of location URIs

This is an oversight on my part.  When I made an update to the content  
model for references, I apparently fixed only the code lists and code list  
sets, not the column sets.

I think we should fix this, but that would make the next release of  
genericode backwards incompatible.  It would be a 2.0 release instead of a  
1.1 release.  I suspect it would only be "technically" backwards  
incompatible, because I have no evidence that anyone is using column set  
references at present (but I would certainly like to hear from anyone who  
is).  The purpose of this e-mail is to let you all know about this issue,  
and to get your feedback about fixing it in the next release of genericode.

Thanks very much in advance,

Cheers, Tony.

On Sat, 05 Apr 2008 11:58:38 +0100, Anthony B. Coates (Document  
Engineering Services) 

I can't add a lot to this. I am not using column set references, and I don't know of anyone who is. My preference would be to go for the correction before they are being used unless anyone else is known to be using them.

Paul



                                                

					
                                                    

        
                                                
				
                                                

                                                    
                                                        
                                                        Original Message
                                                
                                                Original Message-----
From: Anthony B. Coates (DES) [mailto:anthony.coates@documentengineeringservices.com] 
Sent: 14 April 2009 00:47
To: Code List Representation TC
Subject: Re: [codelist] Genericode 1.1? - a request from CEFACT for embedded code lists in code list set documents

Apologies that I've been so slow moving on this.  I mentioned previous  
that UN/CEFACT ICG had request some additions to the genericode Schema.   
In particular, in the 1.0 Schema, a code list set can contain

  * code lists
  * references to code lists
  * references to other code lists sets

UN/CEFACT ICG would like us to add

  * code list sets (not just references)

To be complete, I think we could also add

  * column sets (external definitions of columns and keys)
  * references to column sets

I have a prototype Schema that supports this, and am working on a set of  
examples to demonstrate the different ways code list sets can be  
constructed.  While doing that, I have found a bug in the genericode 1.0  
Schema.

In the 1.0 Schema, a code list reference contains

  * a mandatory canonical URI
  * an optional canonical version URI
  * any number of location URIs

A code list set reference contains exactly the same.

However, a column set reference contains

  * a mandatory canonical version URI
  * any number of location URIs

This is an oversight on my part.  When I made an update to the content  
model for references, I apparently fixed only the code lists and code list  
sets, not the column sets.

I think we should fix this, but that would make the next release of  
genericode backwards incompatible.  It would be a 2.0 release instead of a  
1.1 release.  I suspect it would only be "technically" backwards  
incompatible, because I have no evidence that anyone is using column set  
references at present (but I would certainly like to hear from anyone who  
is).  The purpose of this e-mail is to let you all know about this issue,  
and to get your feedback about fixing it in the next release of genericode.

Thanks very much in advance,

Cheers, Tony.

On Sat, 05 Apr 2008 11:58:38 +0100, Anthony B. Coates (Document  
Engineering Services) 

We are using genericode in the electronic court filing specification, but I'm pretty sure we are not using column set references.

Jim



                                                

					
                                                    

        
                                                
				
                                                

                                                    
                                                        
                                                        Original Message
                                                
                                                Original Message-----
From: Paul Spencer [mailto:paul.spencer@boynings.co.uk] 
Sent: Tuesday, April 14, 2009 1:52 AM
To: 'Anthony B. Coates (DES)'; 'Code List Representation TC'
Subject: RE: [codelist] Genericode 1.1? - a request from CEFACT for embedded code lists in code list set documents

I can't add a lot to this. I am not using column set references, and I don't know of anyone who is. My preference would be to go for the correction before they are being used unless anyone else is known to be using them.

Paul


Original Message-----
From: Anthony B. Coates (DES) [mailto:anthony.coates@documentengineeringservices.com] 
Sent: 14 April 2009 00:47
To: Code List Representation TC
Subject: Re: [codelist] Genericode 1.1? - a request from CEFACT for embedded code lists in code list set documents

Apologies that I've been so slow moving on this.  I mentioned previous  
that UN/CEFACT ICG had request some additions to the genericode Schema.   
In particular, in the 1.0 Schema, a code list set can contain

  * code lists
  * references to code lists
  * references to other code lists sets

UN/CEFACT ICG would like us to add

  * code list sets (not just references)

To be complete, I think we could also add

  * column sets (external definitions of columns and keys)
  * references to column sets

I have a prototype Schema that supports this, and am working on a set of  
examples to demonstrate the different ways code list sets can be  
constructed.  While doing that, I have found a bug in the genericode 1.0  
Schema.

In the 1.0 Schema, a code list reference contains

  * a mandatory canonical URI
  * an optional canonical version URI
  * any number of location URIs

A code list set reference contains exactly the same.

However, a column set reference contains

  * a mandatory canonical version URI
  * any number of location URIs

This is an oversight on my part.  When I made an update to the content  
model for references, I apparently fixed only the code lists and code list  
sets, not the column sets.

I think we should fix this, but that would make the next release of  
genericode backwards incompatible.  It would be a 2.0 release instead of a  
1.1 release.  I suspect it would only be "technically" backwards  
incompatible, because I have no evidence that anyone is using column set  
references at present (but I would certainly like to hear from anyone who  
is).  The purpose of this e-mail is to let you all know about this issue,  
and to get your feedback about fixing it in the next release of genericode.

Thanks very much in advance,

Cheers, Tony.

On Sat, 05 Apr 2008 11:58:38 +0100, Anthony B. Coates (Document  
Engineering Services) 

At 2009-04-13 21:47 +0100, Anthony B. Coates (DES) wrote:
>Apologies that I've been so slow moving on this.  I mentioned previous
>that UN/CEFACT ICG had request some additions to the genericode Schema.
>In particular, in the 1.0 Schema, a code list set can contain
>
>  * code lists
>  * references to code lists
>  * references to other code lists sets
>
>UN/CEFACT ICG would like us to add
>
>  * code list sets (not just references)
>
>To be complete, I think we could also add
>
>  * column sets (external definitions of columns and keys)
>  * references to column sets
>
>I have a prototype Schema that supports this, and am working on a set of
>examples to demonstrate the different ways code list sets can be
>constructed.  While doing that, I have found a bug in the genericode 1.0
>Schema.

We are allowed to issue errata.

>In the 1.0 Schema, a code list reference contains
>
>  * a mandatory canonical URI
>  * an optional canonical version URI
>  * any number of location URIs
>
>A code list set reference contains exactly the same.
>
>However, a column set reference contains
>
>  * a mandatory canonical version URI
>  * any number of location URIs
>
>This is an oversight on my part.  When I made an update to the content
>model for references, I apparently fixed only the code lists and code list
>sets, not the column sets.
>
>I think we should fix this, but that would make the next release of
>genericode backwards incompatible.  It would be a 2.0 release instead of a
>1.1 release.  I suspect it would only be "technically" backwards
>incompatible, because I have no evidence that anyone is using column set
>references at present

Then we should be safe issuing a 1.0 erratum that fixes the inconsistency.

Then adding the new code sets and column sets would be a version 1.1.

>(but I would certainly like to hear from anyone who
>is).  The purpose of this e-mail is to let you all know about this issue,
>and to get your feedback about fixing it in the next release of genericode.

I'll check with Mary.

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

--
XSLT/XQuery/XSL-FO hands-on training - Los Angeles, USA 2009-06-08
Training tools: Comprehensive interactive XSLT/XPath 1.0/2.0 video
Video lesson:    http://www.youtube.com/watch?v=PrNjJCh7Ppg&fmt=18
Video overview:  http://www.youtube.com/watch?v=VTiodiij6gE&fmt=18
G. Ken Holman                 mailto:gkholman@CraneSoftwrights.com
Crane Softwrights Ltd.          http://www.CraneSoftwrights.com/o/
Male Cancer Awareness Nov'07  http://www.CraneSoftwrights.com/o/bc
Legal business disclaimers:  http://www.CraneSoftwrights.com/legal

At 2009-04-13 21:47 +0100, Anthony B. Coates (DES) wrote:
>This is an oversight on my part.  When I made an update to the content
>model for references, I apparently fixed only the code lists and code list
>sets, not the column sets.
>
>I think we should fix this, but that would make the next release of
>genericode backwards incompatible.  It would be a 2.0 release instead of a
>1.1 release.  I suspect it would only be "technically" backwards
>incompatible, because I have no evidence that anyone is using column set
>references at present (but I would certainly like to hear from anyone who
>is).  The purpose of this e-mail is to let you all know about this issue,
>and to get your feedback about fixing it in the next release of genericode.

I have confirmation from OASIS that we are obliged to treat the 
backwards-incompatible change as substantive, thus mandating a 2.0 
release that would contain the fix and other features.

. . . . . .  Ken

>Cc: Robin Cover