Hello everyone:
I gone through the Listening Session notes and have found the following rough ideas/proposals for things that might go into DITA 2.0:
- Scott Hudson (Jeppesen): The apiname element in DITA is overloaded.
- Colin Ferguson (VCE): It would be great if there was some way separating the structured (hierarchical) and semantic content; many people (read: SMEs) don’t care about the order in which they write things, but they understand the idea of semantically-describing
content. Believes that adoption would be better served by making the two more distinct, and that structure could be looser.
- Colin Ferguson (VCE): would like to see a meta-task type standard; process that includes tasks within a larger procedure; something that could construct “super tasks” and would like to see more control over that;
- Zoe Lawson (IBM): Would like to see JSON output, likes the “guided tour” inline help; swagger is all JSON based; if there was a way to get that “it would be crazy useful”.
- Jacqueline Lehr (Schneider-Electric): round-trip DITA-Confluence-wiki support
- Dynamic maps with if/then rule that could poll the user/product and deliver different, customized content based on results
I don't think all of these things are necessarily DITA 2.0 (or even DITA standard) related, but I think it worthwhile to discuss these ideas at a future meeting.
Cheers!
-
Keith Schengili-Roberts
Market Researcher and DITA Evangelist
IXIASOFT
825 Querbes, Suite 200, Montréal, Québec, Canada, H2V 3X1
|