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: Re: [codelist] Fwd: ICG report from Rome

In my post below I was thinking of external referencing mechanisms 
... such as a CVA file pointing to a code list member of a code list set.

Note that with some kind of internal self-referencing mechanism, a 
user could possibly package a collection of genericode files that 
point to each other to describe a multi-dimensional taxonomy.  Each 
branch would be a genericode code list and then one or even multiple 
links from each row could branch out to other genericode code lists.

For example, a program's user interface menu subsystem could be 
described by a set of genericode files with only one branch per row, 
where the linking is to other genericode files in the code list set.

Or something along those lines.  There would need to be some concept 
of a "start here" in the collection (or something simple as a 
convention of using the first of the set).

Something to think about.

. . . . . . . Ken

At 2009-05-21 17:07 -0400, I wrote:
>At 2009-05-13 19:15 +0100, Anthony B. Coates (DES) wrote:
>>the genericode 2.0
>>proposal that I recently sent to the CLRTC list included the changes that
>>they need to support this.  So, if everyone is happy with what I sent, I
>>now have to get cracking with updating the specification document to
>What are your plans for specifying the URL in <LocationUri> for a 
>code list published as a member of a code list set?
>Consider the situation if UN/CEFACT chooses to publish their suite 
>of code lists as a single genericode 2.0 file, with all of their 
>code lists in the one file.
>Somewhere in the middle of this file is the currency code list, and 
>in the <Identification> element for that code list is a 
><LocationUri> element pointing to where this code list is found.
>Given that there is not a unique id= or xml:id= attribute for each 
>code list in the set, and given that the short name for code lists 
>is not constrained to be unique for each list in the set, it seems 
>there is no convention available for use after a "#" after the 
>URL.  What value should be used for the <LocationUri> element?
>. . . . . . . . . . . . Ken

Upcoming: hands-on code list, UBL, XSLT, XQuery and XSL-FO classes
in Copenhagen Denmark and Washington DC USA, October/November 2009
Interested in other classes?  http://www.CraneSoftwrights.com/o/i/
Crane Softwrights Ltd.          http://www.CraneSoftwrights.com/o/
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
Male Cancer Awareness Nov'07  http://www.CraneSoftwrights.com/o/bc
Legal business disclaimers:  http://www.CraneSoftwrights.com/legal

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