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


Help: OASIS Mailing Lists Help | MarkMail Help

codelist message

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

Subject: FW: [codelist] Code List TC URIs/URLs; was: Dissenting argument on namespace URI

In this approach, should we not keep all previously approved versions in the “approved” area?  If so, does this suggest the need to incorporate the version number into the file name or a subfolder name?


-----Original Message-----
From: Anthony B. Coates (Miley Watts) [mailto:abcoates@mileywatts.com]
Sent: Monday, April 23, 2007 5:27 AM
To: Code List Representation TC
Subject: Re: [codelist] Code List TC URIs/URLs; was: Dissenting argument on namespace URI


OK, I've been thinking some more about document URLs for different 

versions of our documents.


In the new OASIS template, there are 4 sets of document URLs.  I'm putting 

in some suggestions, which I'll explain afterwards:



Specification URIs:


This Version:





Previous Version:

Not applicable


Latest Version:





Latest Approved Version:

Not applicable.



The "This Version" URLs are as we have agreed, although I've added the 

specific documents this time.  I'm presuming we won't list "Previous 

Version" in this case, since there are no previous committe drafts, etc.


For "Latest Version", I'm suggesting that we use a




area to provide canonical references to latest versions of documents 

(committee drafts, committee standards, and/or OASIS standards).  For 







Similarly, I'm going to suggest (although not shown in this case) that we 

use a




area to provide canonical references to the latest committee standard or 

OASIS standard versions of documents.  For example:






However, if we were to go with this plan, then I think it would be more 

consistent to change our committe draft 1.0 URLs to






which differs from UBL usage, but would make things like URL re-writing of 

canonical URIs more straightforwards.


Does that sound plausible?  This is just a suggestion, alternate proposals 

are very welcome.


Cheers, Tony.


On Tue, 17 Apr 2007 21:00:23 +0100, Anthony B. Coates (Miley Watts) 

<abcoates@mileywatts.com> wrote:


> Thanks Ken, that's good.  However, how should we provided URLs for 

> "latest" and "latest accepted" versions?  Thanks,

> Cheers, Tony.

> On Tue, 17 Apr 2007 19:07:47 +0100, G. Ken Holman 

> <gkholman@CraneSoftwrights.com> wrote:

>> Thanks for bringing these questions to the fore, Tony ... it has made 

>> me realize that we have some decisions to make before finishing up the 

>> documentation.


>> At 2007-04-17 17:50 +0100, Anthony B. Coates (Miley Watts) wrote:

>>> On Tue, 17 Apr 2007 03:52:49 +0100, Robin Cover <robin@oasis-open.org>

>>> wrote:


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

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

>>>> http://docs.oasis-open.org/codelist/schemas/genericode/1.0/ Schemas


>>> I realise now (as I'm looking at the latest OASIS document templates) 

>>> that

>>> we also need a URL location for the spec itself (and perhaps the

>>> requirements doc too).  I would like to suggest that the specification

>>> should have a URL of the form


>>> http://docs.oasis-open.org/codelist/documentation/genericode/1.0/oasis-code-list-representation-genericode-1.0.*


>> Again from my UBL experience led by Jon, I think it is very helpful in 

>> UBL that all of the files associated with a deliverable are found in 

>> subdirectories of a single subdirectory for that deliverable:


>>    http://docs.oasis-open.org/ubl/cs-UBL-2.0/

>>    http://docs.oasis-open.org/ubl/os-UBL-2.0/


>> So in our case the directory structures would be:


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

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

>>    http://docs.oasis-open.org/codelist/cd-genericode-1.0/       Draft

>>    http://docs.oasis-open.org/codelist/cd-genericode-1.0/xsd/

>>    http://docs.oasis-open.org/codelist/cd-genericode-1.0/doc/

>>    http://docs.oasis-open.org/codelist/cs-genericode-1.0/       Spec

>>    http://docs.oasis-open.org/codelist/cs-genericode-1.0/xsd/

>>    http://docs.oasis-open.org/codelist/cs-genericode-1.0/doc/

>>    http://docs.oasis-open.org/codelist/os-genericode-1.0/       Standard

>>    http://docs.oasis-open.org/codelist/os-genericode-1.0/xsd/

>>    http://docs.oasis-open.org/codelist/os-genericode-1.0/doc/


>> We could include in the genericode doc subdirectory (and call out from 

>> an informative annex in the document) the code list examples you cite 

>> in your text available in the doc/ directory as standalone files (such 

>> that readers don't need to cut and paste to get real copies of the 

>> examples you have).


>> This turns the directory structure inside out from what we discussed 

>> before today's teleconference:  using the release as a base and having 

>> an expected set of subdirectories (thus keeping voting packages easily 

>> together in a ZIP distribution).


>>> where the extension could be "odt" or "pdf" (and I could do "doc" if

>>> required as well).


>> Right ... there is no use of index.html ... that way looking at the 

>> base directory you will see the individual ODT and PDF (and HTML?) 

>> renderings of the specification.


>> . . . . . . . . . . Ken



>> --

>> 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 Aug'05  http://www.CraneSoftwrights.com/o/bc

>> Legal business disclaimers:  http://www.CraneSoftwrights.com/legal






Anthony B. Coates

Senior Partner

Miley Watts LLP

Experts In Data

+44 (79) 0543 9026

Data standards participant: genericode, ISO 20022 (ISO 15022 XML), 



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