xml-dev - RE: Re: alternate enums in XML Schema

[Craig.Curtin@ubsw.com]

my concern is of extentions. our underlying XML element is
getting stored in the database as a "number". but the number (6)
also has an human readable alias ("XYZ").  

i wanted the schema to contain both types of information for 
display (string) as well as storage (number). i also want to
constrain the data to an enumeration set (ie. today 1-5 are
valid, next week its 1-8, ...)

i'm a newbie to XML, so i am easily confused... ;-)

thanks for the reply

-----Original Message-----
From: smohr 
Sent: Friday, May 05, 2000 9:54 AM
To: xml-dev
Cc: smohr
Subject: Re: alternate enums in XML Schema


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@xml.org&BODY=unsubscribe%20xml-dev
List archives are available at http://xml.org/archives/xml-dev/
************************************************************************
***


This message contains confidential information and is intended only 
for the individual named.  If you are not the named addressee you 
should not disseminate, distribute or copy this e-mail.  Please 
notify the sender immediately by e-mail if you have received this 
e-mail by mistake and delete this e-mail from your system.

E-mail transmission cannot be guaranteed to be secure or error-free 
as information could be intercepted, corrupted, lost, destroyed, 
arrive late or incomplete, or contain viruses.  The sender therefore 
does not accept liability for any errors or omissions in the contents 
of this message which arise as a result of e-mail transmission.  If 
verification is required please request a hard-copy version.  This 
message is provided for informational purposes and should not be 
construed as a solicitation or offer to buy or sell any securities or 
related financial instruments.


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