• From: "Stephen T. Mohr" <smohr@v...>
• To: <xml-dev@X...>
• Date: Fri, 5 May 2000 10:53:42 -0400

I think you're confusing the role of the XML processor and the application
built on top of it.  You've typed the element as "number" but included
string information.  This relies on an implicit mapping to a string, which
is properly the role of the application.

If you are restricted to schemas, you have to look at the requirements.  If
the problem is one of extension, e.g., tomrrow I add 6 => XYZ, then type the
element as an enumeration and bypass the numeric encoding.  If the problem
is one of changing the mapping, e.g., tomorrow 5 stops mapping to COM and
maps to XYZ, schemas won't help you.  Look at changing the authoring app or
the consuming app or both with a data driven mapping -- possibly XML.


***************************************************************************
This is xml-dev, the mailing list for XML developers.
To unsubscribe, mailto:majordomo@x...&BODY=unsubscribe%20xml-dev
List archives are available at http://xml.org/archives/xml-dev/
***************************************************************************

• Follow-Ups:
  • Re: alternate enums in XML Schema
    • From: Rick JELLIFFE <ricko@g...>

• References:
  • alternate enums in XML Schema
    • From: Craig.Curtin@u...

• Prev by Date: alternate enums in XML Schema
• Next by Date: RE: alternate enums in XML Schema
• Previous by thread: alternate enums in XML Schema
• Next by thread: Re: alternate enums in XML Schema
• Index(es):
  • Date
  • Thread