Lists Home |
Date Index |
- From: firstname.lastname@example.org
- To: email@example.com
- Date: Wed, 13 Oct 1999 09:59:08 -0700
I'm trying to understand XML. Stop laughing.
The single question is, of course, "what do I need to do in my
applications?" My apps being the type that create documents (productivity).
I have found a glut of information about what XML is and isn't, but somehow
I'm still unable to see how it makes sense in such applications. What I
1) I can offload some code. Pre-fab parsers/validators, XLink and XPointer
solve some problems that I have already solved. If I switch to XML I don't
have to maintain some code that enables this magic. Less code is better, but
in reality it's a pretty small amount of code that doesn't take much effort
2) Although XML is not a solution to interoperability problems, solutions
will probably evolve in terms of XML. It might make sense to use an XML
format to be prepared for future developments. Gambling.
I have more questions than information at the moment. Is that the general
case out there? Where does it make sense to start integrating XML? As a
document storage format? For object exchanges (interchange formats)?
Just thought I'd ask, :)
xml-dev: A list for W3C XML Developers. To post, mailto:firstname.lastname@example.org
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To unsubscribe, mailto:email@example.com the following message;
To subscribe to the digests, mailto:firstname.lastname@example.org the following message;
List coordinator, Henry Rzepa (mailto:email@example.com)