• Draft_1.2_TOC

http://docs.oasis-open.org/dita/v1.1/CS01/archspec/archspec.html

***review whole spec with should/may etc terminology in mind

***core spec vs specializations: if a tool supports core only, is it 1.2 compliant? should we expect tools to support eg both semiconductor and machine industry specializations at the same time? or should they have packages that support specific subsets of specializations, even though they're all part of 1.2?

Architectural spec

1.0 About the DITA 1.1 Specification

***Add explanation of new factoring of spec based on specializations - link to all

2.0 An introduction to DITA

• 2.1 Definitions and background concepts
  • 2.1.1 Basic concepts
  • 2.1.2 Terminology
  2.2 Naming conventions and file extensions
• 2.3 DTD organization
• 2.4 XML Schema organization

3.0 DITA markup

• 3.1 DITA topics
  • 3.1.1 What are topics?
  • 3.1.2 Why topics?

  • 3.1.3 Information typing ***make more generic

  • 3.1.4 Transitional text

  • 3.1.5 Generic topics *** mention topic specializations and domains without actually listing

    • 3.1.5.1 Topic structure ***section containment [12021]

    • 3.1.5.2 Topic content
    • 3.1.5.3 Topic modules
  3.2 DITA maps

  • 3.2.1 What are maps? ***mention map specializations and domains without actually listing

  • 3.2.2 Why DITA maps?
  • 3.2.3 Common DITA map attributes and metadata
  • 3.2.4 DITA map structure
  • 3.2.5 DITA map modules

  • 3.2.6 Inheritance of attributes and metadata in maps ***crisp up terminology - cascade?

    • 3.3.3 Topic properties in topics and maps ***moved from metadata section

    • 3.3.3.1 Metadata inheritance between maps and topics

• 3.3 Metadata elements and common attributes ***mention metadata domain specializations without actually listing

  • 3.3.1 Common metadata elements
    • 3.3.1.1 Publication metadata elements
    • 3.3.1.2 Management metadata elements
    • 3.3.1.3 Metadata qualification elements

    3.3.2 Common attributes ***additions for indirect referencing? [12007]

    • 3.3.2.1 Identifier and content referencing attributes 3.3.2.2 Metadata attributes
    • 3.3.2.3 Miscellaneous Attributes
    • 3.3.2.4 Architectural attributes

4.0 DITA processing ***clarify required behaviors vs default behaviors; maybe call this "behaviors", create separate processing spec that includes definition of precedence, etc.?

• 4.1 IDs and references ***major addition for keyref/indirect referencing [12007]

• 4.2 Navigation behaviors ***split out into linking, TOC, indexing additions for indirect referencing [12007] ***link to 12031 docs for taxonomies

• 4.3 Content inclusion (conref) ***additions for indirect referencing [12007]

• * ***additions for range referencing, preserve without resolving, push over pull [12013,12014,1205]

• 4.4 Conditional processing (profiling) ***link to 12031 docs for controlled values

• 4.5 Chunking
• 4.6 Translation
  • 4.6.1 The xml:lang attribute
  • 4.6.2 The dir attribute

  • XXX move to an appendix? contains specializations, but needs to: 4.6.3 All elements with translation properties

• *** Printing?

• *** Collation? per 12035 - differentiate from indexing - wording: could/should use when creating a collation process?

5.0 DITA specialization ***consider making task-oriented rather than content v design v processing? eg create a specialization, add processing support, generalize... need to provide examples as well; maybe provide common pitfalls/mistakes?

• ***Specialization and custom document types?

  • Intro - define terms, overall process etc. ***relaxed constraints on topic/domain cross-referencing [12010]

  • Creating a custom document type

  • Creating a structural specialization ***relaxed constraints on topic/domain cross-referencing [12010]

    • From a topic type

    • From a map type

  • Creating a domain specialization ***relaxed constraints on topic/domain cross-referencing [12010]

    • From a topic type

    • From a map type

    • From common metadata

    • Creating a simple domain specialization

    • Creating an attribute domain specialization

  • Creating a constraints domain specialization [12008]

  • Specializing foreign or unknown content

  • Generalization

  • Limits of specialization and common pitfalls

Other specification documents, with some impact notes:

• Base language specification (topics, maps, metadata)
• Processing specification (including order of operations where needed)
• Core utilities specializations (utilities, mapgroup, highlighting, xNal)
• Technical content specializations (concept, general task, task, reference, glossary)
• Book publishing specialization (bookmap)
• Software specializations (software domain, programming domain, UI domain)
• Semantic linking, controlled values, taxonomies specializations
• Machine industries specializations
• Learning and training specializations
• Context-sensitive help specializations