[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [dita] Need Clarification on Implications of Different List Markup Patterns
Hi Erik,
Yes, this is an interesting way to provide further restrictions on a “loose” content model without the need to make it a specialized semantic type – which does fit the kind of situations I’m thinking of.
What I am also suggesting, however, is that the base DITA topic and core specializations be explicitly made looser, with a specialization or constraint mechanism then used to specify recommended best practice usage.
For example, the base DITA topic could be changed to allow nested sections, which would make it much more extensible. But for technical writing the committee could also specify constraints that do NOT allow nested sections as a recommended best practice. Today, these recommended best practices are built right into the base topic model.
Thanks much, Eric
Eric Severson From: Erik Hennum
[mailto:ehennum@us.ibm.com]
Hi, Eric: http://www.oasis-open.org/apps/org/workgroup/dita/download.php/25090/IssueConstraints12008.html
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]