1.2-targetted comments from architectural spec review

Comments from:
JO: Jeff OGden
YE: Yas Ettessam
SD: Stan Doherty
EK: Eliot Kimber
MP: Michael Priestley

New proposals:
YE        guidelines
for public IDs
MP        allow
draft-comment in more places, eg directly in body (otherwise need to add
empty para to add a comment after a table)
JO        consider
making xml:lang a required attribute on the root topic and map elements

Covered by existing proposals:
JO        namespaces
discussion (covered in 12030)
JO        explicit
element for content title in topicref, move navtitle to element also (covered
in 12017, which is inaccurately labelled as a conref proposal in the table)

General spec comments (should not require
a proposal):
SD        add
diagrams to terminology section showing rel between types/terms
SD        DITA
module descriptions: add table showing use by doctype with one col/doctype?
JO        add
examples and example output for each infotype
JO        in
linking topic, add complete list of (default) relationships (make linking
a processing topic)
JO         add
"aggregating" processing topic
JO        document
behavior of mismatch between topicref assertions and target's reality (eg
format, scope, type...)
JO        reorganize
metadata discussions to provide single organized section on metadata
MP        review
translatable-content dispositions in translation properties tables - many
seem overly conservative
JO        add
exampes for structural vs. domain specialization
EK         search
for "file", reword as document

Michael Priestley

IBM DITA Architect and Classification Schema PDT Lead



http://dita.xml.org/blog/25