As part of the "which XML" decision making, you no longer have to think about what you want to do with your content in the future. Right now if you are not wanting your content ready for absolutely anything and everything you shouldn't be thinking XML. Ready for everything means at least all of the following:
- Web
- Mobile delivery
- Packaged solutions such as SCORM, and DVD Delivery
- E-books - any format
- Remixable/reusable Content Objects
- Multi-dimension interstellar holograms
All of these usage scenarios (with the possible exception of Item 7) must be instantly doable and cost predictable. Unfortunately XML has become an metaphor for - you are going to pay through the nose now and into the future!
An "XML first" strategy using TEI, DocBook or some ground-breaking XML Schema is going to cost you disproportionately. It will be under constant maintenance and will be a budget hole. One of the reasons I am writing this post is because once more we are converting a library of customized DocBook files to reprint PDF and ebook formats. It irritates me to convert novels and trade-books from DocBook to XHTML (even though there may be a bit of revenue in it), especially when the XML content interpretation is nearly always some customized nonsense, especially with Front Matter and metadata (that's another story), and always needs quality review.
These specialist XML Schemas are just not required for any content. It is a continuing theme on this blog (and will continue to be so), XHTML and CSS do it all. If your consultant is saying anything else, tell him to buy me a drink and I will explain the simple facts.
More than anything XML for valuable content needs to be simple, ubiquitous, extensible, customizable - malleable to achieve the future strategies. The legacy XML Schemas are exactly the opposite, specific, rigid, locked and expensive to change.
Use XHTML, and if done well it will all cost less than any other schema, and you really will be ready for the future.
Comments