[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [dita] DITA 1.2 specification documents
Hi Jeff et al, This list looks great – just remember that you’ll
either need to produce a single document called “DITA 1.2” that
will then contain the requisite front matter and listing of each of the
separate components (think intro section to a multi-volume set); or each of
these will become a separately-balloted stand-alone specification/standard. Obviously you can combine *some* of the pieces
into the main DITA 1.2 document and leave others to stand alone as appropriate
as well. I know I’ve brought it up before, but I just don’t
want to see the process delayed once you’re ready to go to public review J All the best, Mary From: Ogden, Jeff
[mailto:jogden@ptc.com] Here is the list of
planned DITA 1.2 specification documents as of the last time we talked about
this. a) DITA 1.2 Base
Architectural Specification (introduction, topic, map, and metadata markup,
processing including delayed resolution, specialization including constraints). b) DITA 1.2 Base
Language Reference (map, topic, metadata including delayed resolution, map
group domain). c) DITA 1.2 Utility
Domain Specializations Architecture and Language Reference (utilities,
highlighting, and hazard statement domains). d) DITA 1.2 xNAL Domain
Specializations Architecture and Language Reference. e) DITA 1.2 Technical
Content Architecture and Language Reference (concept, task, reference,
glossary). f) DITA 1.2 Software,
Programming, and User Interface Domains Specializations Architecture and
Language Reference. g) DITA 1.2 Book
Architecture and Language Reference (bookmap). h) DITA 1.2 Learning and
Training Content Architecture and Language Reference. i) DITA 1.2 Machine
Industry Architecture and Language Reference. j) DITA 1.2 Semantic
Linking, Controlled Values, and Taxonomies Architecture and Language Reference. k) DITA 1.2
Processing Guidelines and Examples (non-normative). Item
(e) might or might not be renamed. Item
(f) might or might not have some doctype shells added. I
would still like to create item (k), but suspect that we should drop it from
the DITA 1.2 work and do it later as a “best practice” or similar
document that is non-normative and outside of the DITA 1.2 Specification. Given
recent discussions it is possible that we may want to combine some of these
items, but exactly how isn’t clear to me at this point. -Jeff |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]