dita — archive

[Robert Anderson]

Hi everybody, There is still no response to this one, so my plan for tomorrow's meeting is to keep to the original proposal. The specification should describe default behaviors for references from one map to another map, but allow that specializations may define alternate behaviors as appropriate. Compliant DITA processors should be expected to follow any alternate behaviors for OASIS approved elements, because those behaviors must be described as part of the specification. However, there is no mechanism for processors to automatically determine the non-default behaviors for other specializations. I would be happy to have a way to define non-default behaviors for map references. However, I am not sure how to come up with one that is simple enough to use, so it is not a part of this proposal. Thanks, Robert D Anderson IBM Authoring Tools Development Chief Architect, DITA Open Toolkit (507) 253-8787, T/L 553-8787 (Good Monday & Thursday) Robert D Anderson/Rochester/IBM@IBMUS wrote on 09/05/2007 04:28:03 PM: > In an attempt to draw out more responses on this one ... > > The issue under discussion is how to define differences in behaviors. To > make it easier, I will give a specific example. > > We have a chapter element defined in bookmap. When this points to a map, it > casts the referenced material in the role of a chapter, or a sequence of > chapters if there are multiple top-level elements. Attributes and metadata > will cascade to the referenced 'chapters'. > > Within IBM we have another specialization,