1.2 Errata: Missing discussion of domain constraint module location

[Eliot Kimber <ekimber@rsicms.com>]

If you have a domain constraint module, it must necessarily declare a
constraint-specific domain integration entity. This is discussed in the
topic "Requirements for domain constraint modules".

For this entity to have any effect the domain module must be included in the
shell DTD *before* the domains integration parameter entity declarations.

However, the discussion in the topic "DTD document-type shell: Coding
requirements" only provides for including the constraint modules after the
domain integration parameter entities.

We need to make one or the other of these corrects:

Option 1: Allow constraint modules to have a separate constraint entity
declaration (.ent) file that is included before the domain integration
entities. This would be consistent with the pattern for domains.

Option 2: Allow constraint .mod files to be included *before* the domain
integration entities. This would make the domain integration parameter
entities available.

For myself, I think Option 1 is the better option even though it requires
changes to more places in the spec, because it maintains the .ent/.mod
pattern used for structural and domain modules.

Cheers,

E.

-- 
Eliot Kimber
Senior Solutions Architect, RSI Content Solutions
"Bringing Strategy, Content, and Technology Together"
Main: 512.554.9368
www.rsicms.com
www.rsuitecms.com
Book: DITA For Practitioners, from XML Press,
http://xmlpress.net/publications/dita/practitioners-1/