I think that this description and the following example are
not quite in synch. It’s unclear to me that the text and example actually
match.
Within
the constraint module there must be a declaration for
a general text entity named "tagname-constraints",
where tagname is the name of the element type to which the constraints apply.
The replacement text for the entity must be
of the form "(tagname qualifierTagname-c)", where tagname is
the name of the element type to which the constraints apply, qualifier is
as for the module filename (e.g., "strict"), and Tagname is
the element type name with an initial capital (e.g. "Topic"). The
literal "-c" indicates that the name is the name of a constraints
domain. There must also be a declaration of the %tagname.content
parameter entity that defines the constrained content model.
For example:
<!ENTITY %
basicHighlight-c-ph "b | i">
<!ENTITY
basicHighlight-c-att "(topic hi-d basicHighlight-c)">
In
this example, the set of highlight domain elements has been reduced to just
<b> and <i>.
The description seems to be a reuse of the explanation for
structural constraint modules and doesn’t quite fit what the example
shows.
Thanks.
Julio
J. Vazquez
Sr.
Information Architect
919-354-1123
Follow
me on Twitter @juliov27612
http://www.sdicorp.com/Solutions/Corporations.aspx
Author
of Practical DITA
