Lists Home |
Date Index |
6/11/2002 11:20:55 AM, "Simon St.Laurent" <firstname.lastname@example.org> wrote:
>At 11:06 AM 6/11/2002 -0400, Mike Champion wrote:
>I'm a text-editor kind of guy who writes SAX filters. That solves a lot
So, I take it your approach is to have the application use pattern-matching to
extract the information within an element/attribute value into the form
you wish to process it? For example let the author type the date in any convenient format, then
by default ...I guess you would use regular fragmentations and SAX) to
make it useful by the application???
Hmm, I guess that makes sense a an option; rather than have the GUI
normalize it, or some post-processor normalize it (making it vulnerable
to being broken by somebody "fixing" the XML with Notepad), just
do the "normalization" in the application. I'm personally not crazy about
it (since I tend to use XPath and/or XSLT to locate parts of a document
or a collection of docs to process, and XPath doesnt' know about the private
understanding between author and app writer on what the acceptable formats
for a date might be).
Still, I'm sure we agree on the fundamental point: there is a lot of territory
between helplessly dealing with <date>June 11, 2002</date> as
a string that requires human intervention to process, and drinking the Schema koolaid
in order to automatically bind it to a Date object.