This Wiki page is designed to collect comments on the second review of the DITA 1.2 specification, 21 September - 3 October 2009. This review is being conducted by members of the OASIS DITA Technical Committee.

Previous | Next | Home page for the second review

Important: Reviewers, be sure to preface comments with your name and the date, for example, [Eberlein, 18 September 2009]

[WEK, 10 Dec 2009] All comments addressed.

Concrete ("shell") document types

[gerjosep, 18 Oct 2009] Please see my comments to these sections on the previous Wiki page!

[WEK, 7 Dec 2009] Done.

Modularization and integration of design

DTD doctype shell coding requirements

[s.park 7 oct]: The 1.1 topic types DTDs do not have/integrate ENT files. Is this coding requirement new to 1.2? Would it be helpful to explain what new functionality drives this requirement?

[WEK, 7 Dec 2009] This is a side effect of the structural/domain module unification, because now structural modules must also declare a domains attribute configuration entity. As a rule we are not highlighting 1.2-provided features where they are defined.

Shall we explicitly state that the domain entity declaration must have a public or unambiguous system identifier?

[WEK, 7 Dec 2009] There is a general statement elsewhere that modules that are intended for use outside a very controlled environment should have associated public identifiers.

Thanks for showing an example use of URN as public ID!

[WEK, 7 Dec 2009] Thanks for noticing.

In domain declaration redefinition example, there was a missing training semicolon. Was: &newAtt-d-att Changed source to: &newAtt-d-att;

[WEK, 7 Dec 2009] Thanks.

XSD doctype shell coding requirements

ConcreteDocumentTypes (last edited 2009-12-10 20:19:01 by ekimber)