OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

dita message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE: [dita] proposed packaging and doctype shells for DITA 1.2


All of the map doctype shells include the map-group domain, right?

 

Just checking: There are no doctype shells specific to the Machine Industry, Software and Programming, or Classification, Controlled Values, and Taxonomies work or to the extent that there are they are included in the Technical Content collection, right?

 

Just checking: Grouping the doctype shells into three collections (base, tech content, learning and training) doesn’t imply any changes to the organization of the DITA 1.2 specification documents or does it?

 

The current organization of the DITA 1.2 specification documents is:

 

  • DITA 1.2 Specification Overview
  • DITA 1.2 Base Architectural Specification
  • DITA 1.2 Base Language Reference
  • DITA 1.2 Utility Domain Specializations Architecture and Language Reference
  • DITA 1.2 Technical Content Architecture and Language Reference
  • DITA 1.2 Software and Programming Content Architecture and Language Reference
  • DITA 1.2 Learning and Training Content Architecture and Language Reference
  • DITA 1.2 Machine Industry Content Architecture and Language Reference
  • DITA 1.2 Classification, Controlled Values, and Taxonomies Architecture and Language Reference

 


From: Michael Priestley [mailto:mpriestl@ca.ibm.com]
Sent: Friday, August 15, 2008 11:53 AM
To: dita@lists.oasis-open.org
Subject: [dita] proposed packaging and doctype shells for DITA 1.2

 


Assumptions:
- need to keep the legacy shells from 1.1 to avoid breaking existing users
- beyond legacy shells, adding only the bare minimum to exercise each new domain and structural type
- users will go to the web tool for most combinations (such as tech content with learning objectives, or tech content without the sw domain)

Base (2 shells):
        topic and map plus utility domains
Tech content (11 shells):
        topic, concept, task, general task, task with requirements domain, reference, glossary, ditabase (all incorp. hazard, utility, sw, pr, ui domains);
        bookmap, 2 classification maps
Learning and training (7 shells):

        5 l&t topic types, topic with l&t domain, map with l&t domain


Michael Priestley
Lead IBM DITA Architect
mpriestl@ca.ibm.com
http://dita.xml.org/blog/25



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]