Re: Replace short codes when converting legacy to XML?

"G. Ken Holman" <[email protected]>
Newsgroups gmane.text.xml.devel
Message-ID <[email protected]>
Thank you, Stephen!

Roger, this specification is in the process of being updated, with 
zero changes to the genericode schema itself:

   https://github.com/oasis-tcs/codelist-genericode/releases/tag/csd05wd01-20220202-2113z

Managing a code list through this specification will give you 
opportunities for multi-lingual documentation and other value-level 
metadata in addition to list-level metadata.

. . . . . Ken

At 2022-03-14 13:33 +0000, Stephen D Green wrote:
>Genericode
><http://docs.oasis-open.org/codelist/cs-genericode-1.0/doc/oasis-code-list-representation-genericode.html>http://docs.oasis-open.org/codelist/cs-genericode-1.0/doc/oasis-code-list-representation-genericode.html
>
>Why reinvent the wheel?
>
>
>On Mon, 14 Mar 2022 at 12:03, Roger L Costello 
><<mailto:[email protected]>[email protected]> wrote:
>Hi Folks,
>
>I am creating an XML Schema for air refueling routes. The XML format 
>will replace a legacy format.
>
>Each point on an air refueling route is identified: is the point an 
>entry point (enter the air refueling route), an exit point (exit the 
>air refueling route), and so forth.
>
>For generations air navigators have used the code ET for EnTry point 
>and the code EX for EXit point. I think the codes were made short 
>due to limited computer memory on the airplanes.
>
>I figure it's time for the air navigators to change and use 
>human-friendly terms. So, instead of creating my XML Schema using legacy codes:
>
><xs:enumeration value="ET"/>
><xs:enumeration value="EX"/>
>
>I plan to create an XML Schema that uses human-friendly terms:
>
><xs:enumeration value="entry point"/>
><xs:enumeration value="exit point"/>
>
>Is it a good idea to replace the codes with human-friendly terms? 
>Or, should my XML Schema continue using the codes?
>
>Once I've completed my XML Schema I will show it to the air 
>navigators to get their approval (or disapproval).
>
>/Roger
>
>
>
>_______________________________________________________________________
>
>XML-DEV is a publicly archived, unmoderated list hosted by OASIS
>to support XML implementation and development. To minimize
>spam in the archives, you must subscribe before posting.
>
>[Un]Subscribe/change address: 
><http://www.oasis-open.org/mlmanage/>http://www.oasis-open.org/mlmanage/
>Or unsubscribe: 
><mailto:[email protected]>[email protected]
>subscribe: 
><mailto:[email protected]>[email protected]
>List archive: 
><http://lists.xml.org/archives/xml-dev/>http://lists.xml.org/archives/xml-dev/
>List Guidelines: 
><http://www.oasis-open.org/maillists/guidelines.php>http://www.oasis-open.org/maillists/guidelines.php
>
>--
>----
>Stephen D Green


--
Contact info, blog, articles, etc. http://www.CraneSoftwrights.com/x/ |
Check our site for free XML, XSLT, XSL-FO and UBL developer resources |
Streaming hands-on XSLT/XPath 2 training class @US$125 (5 hours free) |
Essays (UBL, XML, etc.) http://www.linkedin.com/today/author/gkholman |


_______________________________________________________________________

XML-DEV is a publicly archived, unmoderated list hosted by OASIS
to support XML implementation and development. To minimize
spam in the archives, you must subscribe before posting.

[Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
Or unsubscribe: [email protected]
subscribe: [email protected]
List archive: http://lists.xml.org/archives/xml-dev/
List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.