RE: [dita] Groups - Issue 34: Constraints - restriction withoutspecialization (was replacement domains) (Issue34.html) uploaded

Hi, JoAnn:

Yes, that's one important use -- simplifying content models.  The Use Cases section has a few other important uses.

The proposal would declare and manage these restrictions within the DITA architecture so you can get consistency across your topic types and even agree with partners on a set of common restrictions.

One beneficial side effect would be in simplifying the type hierarchy because you would specialize only for semantic reasons and not because you want to simplify the content model.

The limitation is that we can't provide any special magic to propagate restrictions (any more than we can define specializations by delta).  To restrict the content model for an element, you would have to redefine the entire content model for the element.  If the system recognizes that you've done so for a purpose, however, it can validate that you've done so consistently and check whether other content conforms to your restrictions.

Thanks,

Erik Hennum



"JoAnn Hackos" <>

"JoAnn Hackos" <> 

10/17/2005 12:32 PM

To

Erik Hennum/Oakland/IBM@IBMUS, <>

cc

Subject

RE: [dita] Groups - Issue 34: Constraints - restriction without specialization (was   replacement domains) (Issue34.html) uploaded

Erik et al.

One of the most common use cases we encounter is to reduce the elements

allowed at various points in the DTD. Do I understand correctly that

this proposal would provide us with a mechanism essentially to "hide"

certain elements that we don't want authors to use without creating a

specialization?

JoAnn 

-----Original Message-----

From:  [mailto:] 

Sent: Monday, October 17, 2005 11:07 AM

To: 

Subject: [dita] Groups - Issue 34: Constraints - restriction without

specialization (was replacement domains) (Issue34.html) uploaded

This revision adds links to some sample posts indicating the need that

motivated this proposal.

 -- Erik Hennum

The document revision named Issue 34: Constraints - restriction without

specialization (was replacement domains) (Issue34.html) has been

submitted

by Erik Hennum to the OASIS Darwin Information Typing Architecture

(DITA)

TC document repository.  This document is revision #1 of Issue34.html.

Document Description:

This proposal provides an architectural mechanism for restricting the

content models and attribute lists of existing elements.

View Document Details:

http://www.oasis-open.org/apps/org/workgroup/dita/document.php?document_

id=14936

Download Document:  

http://www.oasis-open.org/apps/org/workgroup/dita/download.php/14936/Iss

ue34.html

Revision:

This document is revision #1 of Issue34.html.  The document details page

referenced above will show the complete revision history.

PLEASE NOTE:  If the above links do not work for you, your email

application

may be breaking the link into two pieces.  You may be able to copy and

paste

the entire link address into the address field of your web browser.

-OASIS Open Administration