Tool for conducting DITA 1.3 spec reviews

I didn't find any mention of conref restrictions between general task and constrained task.
http://docs.oasis-open.org/dita/v1.2/os/spec/archSpec/module-compatibility.html#module-compatibility Doesn't mention constraints at all.
Should be updated to include mention of constraints, as well as intended behavior of loose validation by default, with processor option to turn on strict validation.
http://docs.oasis-open.org/dita/v1.2/os/spec/archSpec/conref.html#conref Does mention constraints, but in language that is inherited from DITA 1.1, so in fact it's not referring to constraints in the DITA 1.2 sense but using the word in a generic fashion.
Needs to be updated to reflect DITA 1.2 meaning of constraint, intended processing behavior, and link to specific topic on constraints and conref/generalization.
http://docs.oasis-open.org/dita/v1.2/os/spec/archSpec/recognizedconstraintmechanisms.html#recognizedconstraintmechanisms http://docs.oasis-open.org/dita/v1.2/os/spec/archSpec/vocabularymodules.html#vocabularymodules http://docs.oasis-open.org/dita/v1.2/os/spec/langref/data.html#data Mentions constraints but uses word in the generic sense.
Need new wording to avoid confusion.
http://docs.oasis-open.org/dita/v1.2/os/spec/archSpec/domainsatt.html#domainsatt Mixes "document constraint mechanism" (meaning schema or DTD) and "constraint module" language (meaning DITA 1.2 constraints), potentially causing confusion.
http://docs.oasis-open.org/dita/v1.2/os/spec/archSpec/generalize.html#generalize Uses "topic nesting constraint" along with DITA 1.2 constraint language, potentially causing confusion.
Mixes use of the word constraint in a generic sense with specific sense, potentially causing confusion.
http://docs.oasis-open.org/dita/v1.2/os/spec/conformance.html#ThisIsARevisionOfTheDraftDITA1.2Co-034C9AC3 http://docs.oasis-open.org/dita/v1.2/os/spec/archSpec/createConstraintsDomainSpec.html#createConstraintsDomainSpec http://docs.oasis-open.org/dita/v1.2/os/spec/archSpec/constraintsGeneralize.html#constraintsGeneralize Says that constraints MAY be checked for validity during conref.
Should be updated to explicitly set default as loose validation, with processor option to turn on strict, and make it clear that the rest of the topic only applies if strict validation is turned on.
Michael Priestley, Senior Technical Staff Member (STSM)

Total Information Experience (TIE)

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