The point of XML is that it's a data format that you can process. But the
specific STRUCTURE of the XML for a given use is not preordained. It's up to
your team to work out the best XML structure to use. XML includes tooling that
you can use to transform XML from one structure to another, and
What does this doc look like to end users? Is that going to change, or
will it stay the same and the developers just want you to reduce the
amount of work they have to do?
Is their ideal that they could just plug what you give them into their project?
Are we talking about a web application here?
Hey, Cuc:
For some unknown reason, I can't reply to the forum, so I'm replying to you
directly.
If you're not familiar with XML, I recommend this book:
https://www.amazon.com/XML-Bible-Elliotte-Rusty-Harold/dp/0764549863/ref=sr_1_1?s=books=UTF8=1528931328=1-1=xml+1.1+bible
It's a lot to read,
Hi C2...
If your model is very simple, you could create your own, but then you'd
have to develop and maintain your structure application and publishing
workflow (not for the faint-hearted). If you use DITA or Lightweight
DITA, you get the structure applications for free as well as publishing
Hello Frame Users.
Our software team has said they are going to switch their input from plainly
formatted HTML to XML. I'm hoping to get some advice on what should be required
from them. I am only familiar with unstructured Frame and so far we have
manually processed the entire content dump
