Lists Home |
Date Index |
- From: Chris Maden <email@example.com>
- To: firstname.lastname@example.org
- Date: Fri, 6 Aug 1999 12:02:44 -0400 (EDT)
> Thanks for your response. Just to steer this discussion (if
> there is one) in the right direction, I am not interested in
> debating all the element considerations to make (we've discussed ad
> nauseam things like zip code vs. postal code, should it consider
> international, what if the USPS standard changes, shouldn't it be
> alphanumeric instead of numeric since we're not calculating on it,
> etc.). What I'm really trying to find out is if XML might enable us
> to totally avoid doing this work at all, and isn't the idea of
> "federating" XML tags unnecessary?
Ah. No, XML does not relieve you of analyzing your data. You may be
able to benefit from an analysis that someone else has done by
borrowing their "zipcode" element type and some sample code for
handling it, but really you're going to need to do the same analysis
and develop a full or partial document type for your data.
XML gives you the power to describe your own data; it doesn't help you
to describe it more than you understand it, though.
<!NOTATION SGML.Geek PUBLIC "-//Anonymous//NOTATION SGML Geek//EN">
<!ENTITY crism PUBLIC "-//O'Reilly//NONSGML Christopher R. Maden//EN"
<USMAIL>90 Sherman Street, Cambridge, MA 02140 USA" NDATA SGML.Geek>
xml-dev: A list for W3C XML Developers. To post, mailto:email@example.com
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:firstname.lastname@example.org the following message;
To subscribe to the digests, mailto:email@example.com the following message;
List coordinator, Henry Rzepa (mailto:firstname.lastname@example.org)