Quote:
|
Originally Posted by Clive Long 1. If your organisation uses XML what is its primary application?
1.1 Data transfer between devices?
1.2 Content "distribution" for rendering on different devices / browsers?
1.3 Other? (please specify) |
We use it all over the shop. My primary use of it is focused around XML document processing through XSLT (including rendering in XHTML + XForms). Communication through SOAP. A little bit of some of the many XML standards out there. For example using XInclude for document inclusion processing. I use Apache Cocoon as a pipeline framework. Don't really send alternative rendering for multiple targets but I'm keeping it in mind while developing the system.
Oh and Schema. OK basically I'm an XML nut.
Quote:
|
Originally Posted by Clive Long 2. How does your organisation "hold" its XML
2.1 In "flat files"?
2.2 In some standard database e.g. Oracle?
2.3 Other? (please specify) |
It is interesting to not see "as XML" (or would you deem that flat files) as an option. Anyway for the XForms data we get back from the client we then persist in a SQL database and when data is fetched back the row(s) are converted back into XML based on the Schema.
Quote:
|
Originally Posted by Clive Long 3. What benefits have accrued from using XML? |
It's really easy to take an XML document and make another one out of it using XSLT (which is, as it happens, an XML document). I like that; a lot. For example I can provide the news as an Atom feed and then feed that into the body of a HTML file.
If you have a Schema you can easily get real time validation on files and such so some of the tools are really good to work with.
Quote:
|
Originally Posted by Clive Long 4. What problems are experienced using XML? |
Sometimes trying to debug some of the processing (when things go wrong) can be a pain. Umm the SQL tools I have for mapping I haven't been that impressed with but they are improving. It can be a bit verbose but I don't see that as a big deal.