The Adobe XML architecture combines the powerful data and business logic capabilites of XML with rich presentation capabilities of Portable Document Format (PDF). The Adobe XML architecture offers support for arbitrary XML, allowing you to leverage existing and industry-standard schemas. Depending on the process requirements, forms can be deployed as PDF or an XML Data Package (XDP) and processed as XML.
In order to profit--literally--from the new digital markets, publishers must rethink the way they create, manage, publish, and deliver content. They must re-engineer their processes to create more flexibility and guarantee a sustainable and certain future. They must re-imagine a production process that frees their content to be transformed--on-demand--into whatever new formats, devices, and uses consumers require, now and for the future.
Implementing structured authoring with XML allows organizations to create better content. The addition of hierarchy and metadata to content improves reuse and content management. These benefits, however, must be weighed against the time and money required to implement a structured authoring approach. The business case is compelling for larger writing organizations; they will be the first to adopt structured authoring. Over time, improvements in available tools will reduce the cost of implementing structured authoring and make it affordable for smaller organizations.
Compares Gutenberg's invention of the movable type to the creation of XML. But where movable type changed the “economics of a mechanical process,” XML changed the “economics of content authoring, formatting, and customization.”
After spending a week of toil and labor in the Semantic Web mines, I've returned to the surface, to the sweetness and light of the XML developer community. And what do I find but a crisis about the XML part of the technical book publishing industry, as well as a monster thread about character entity names.