RE: How to handle content vs. context markup?
Where does the markup design start? o Existing documents? that is, sprinkling tags through a text o Abstract schema? that is someone sits down and designs a document type without regard to existing texts through some kind of domain analysis process One usually ends up tagging for the effectiveness of the transforms and the granularity of discrete identity. How many kinds of output documents must you handle, are they uptransforms or downtransforms, do you need or can you use the document() function, do they have to be indexed for navigation, how small did the "chunks" get to be (eg, paragraph types vs row/column types)? len -----Original Message----- From: Jens Jakob Andersen, PDI [mailto:jens.jakob.andersen@p...] So what is the experience and best practice of "content vs. context" tagging?
PURCHASE STYLUS STUDIO ONLINE TODAY!
Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!
Download The World's Best XML IDE!
Accelerate XML development with our award-winning XML IDE - Download a free trial today!
Subscribe in XML format