XML.orgXML.org
FOCUS AREAS |XML-DEV |XML.org DAILY NEWSLINK |REGISTRY |RESOURCES |ABOUT
OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
Re: [xml-dev] Replace short codes when converting legacy to XML?

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:costello@mitre.org>costello@mitre.org> 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:xml-dev-unsubscribe@lists.xml.org>xml-dev-unsubscribe@lists.xml.org
subscribe: <mailto:xml-dev-subscribe@lists.xml.org>xml-dev-subscribe@lists.xml.org
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 |



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


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 1993-2007 XML.org. This site is hosted by OASIS