Hi Folks,
I am creating an XML Schema for air refueling routes. The XML format will replace a legacy format.
You are suggesting other humans change their terms instead of using acronyms but I notice you haven't called this an Extensible Markup Language Schema. Would more people understand the term if you did?
David
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/
Or unsubscribe: xml-dev-unsubscribe@lists.xml.org
subscribe: xml-dev-subscribe@lists.xml.org
List archive: http://lists.xml.org/archives/xml-dev/
List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
