 |
 |
 |
Although putting the XML into a text field is still a common
technique. Doc mgt on the cheap.
We use
HTML for templates in Notes fields. It is easy and the user can modify
it
without too much effort or depth.
OTOH,
grandfathering HTML is still haunting us for reasons we all know
about.
Where
markup goes wrong in these situations is that it is all too easy for the user or
an
XML-unaware process to muck it up with the usual results (a
downstream processor halts
and catches fire).
Have
you ever tried to show XML comments in Powerpoint? OpenDoc's
best assault on Office will
be
proper handling and display of XML constructs.
len
From: Anne Thomas Manes
[mailto:atmanes@g...]
Perhaps "storage" is the wrong
word, because it implies persistence to some type of data store, but the basic
concept is valid. Either the XML is persistent or it is transient. If the XML
is persistent, then the application works directly on the XML. If the XML is
transient, then the XML is transformed into some other format (language
objects, relational database, etc.) that the application works with.
|
 | 

|  |
These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.
|  |
| |
 |
 |
 |