The sharing of xml content, I'm talking about implies having the
stylesheets to render it in a useful form. With specialization in
DITA, the idea is that every computer could be installed with the
default stylesheets that could give you a rough draft output of the
xml document that you received from someone else - as long as they
used DITA..
I don't see that as a very strong business case for most companies...
I'd speculate that the technology could evolve where the stylesheet
could be embedded within the xml to render it seamlessly when
necessary instead..
Regards.
--
Rajal
On May 10, 2008, at 12:05 AM, Dave Pawson wrote:
Rajal Shah wrote:
The one business need that DITA is trying to solve with
specialization - based on all my discussions with the DITA experts
- is that it allows you to share/distribute your xml content files
without having to distribute the stylesheets.
Docbook does that already? Why can't I share a chapter/section/sectN?
I've not heard a use case for 'specialization' yet on this thread
(Other than 'they do it' it must be good).
The Xinclude overhead is likely a low use case soluable by
more processing power when needed. Or use entities.
regards
--
Dave Pawson
XSLT XSL-FO FAQ.
http://www.dpawson.co.uk
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
