> I've heard of DITA in the past. What I'm not sure to understand is what is > the benefit of supporting DITA. > How do you actually model documents with DITA and suppose you are round > tripping back to DITA from XWiki, what do you actually do with the output > ? You model by creating documents parts as XML files (fragments, concepts in dita world), and you can aggregate them to form a document by creating a dita map file, basically a summary referencing all needed fragments. You generate final document (pdf, rtf, xml, whatever) through a build process (ant or maven) from the sources (xml/ditamap/images/...). Fragments content "looks like" XHTML but with dita specific tags (<fig>, <note> ...). For us it's quite useful as we can easily define parts that are reused among documents (terminology, contacts ...) without heavy copy/paste, and integrate the documentation in overall build process. It's a bit like a maven site, but greatly more sophisticated and adapted to projects technical documents output.
Our use-case for integrating XWiki in the loop is because the people targeted by these documents have no easy possibility to : - view final documents "online" - add their own comments to documents before they are delivered (in an easier way than bug tracking on documents ...) Publication to XWiki would solve this issue... Reverting back modifications from XWiki to DITA format would add more collaboration by letting "end users" propose modifications even if they don't know much about dita. Well I realize it's a bit out-of-scope of this thread, because dita is not what we could call "popular". But if I investigate more on this subject I'll open a new thread (if you're interested of course). -- View this message in context: http://xwiki.475771.n2.nabble.com/Extending-XWiki-collaboration-toolset-tp6900649p6907687.html Sent from the XWiki- Users mailing list archive at Nabble.com. _______________________________________________ users mailing list users@xwiki.org http://lists.xwiki.org/mailman/listinfo/users
