OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

dita message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE: [dita] conref and attribute overrides discussion



The wording in the 1.1 spec for "Content inclusion (conref)" 
includes the following about merging attributes:

-------

The resolved element's attribute specifications can be drawn from 
both source and target elements in the following priority:

   1. All attributes as specified on the source element except 
      for attributes which specify the value "-dita-use-conref-target"
   2. All attributes as specified on the target element except:
         1. The id attribute
         2. Any attribute also specified on the source element such
            that its specified value (on the source element) is not
            "-dita-use-conref-target"
   3. The xml:lang attribute has special treatment as described in
      The xml:lang attribute.

. . .

If the target element has a conref attribute specified, the above 
rules should be applied recursively with the resolved element from 
one source/target combination becoming one of the two elements 
participating in the next source/target combination....

-------

This seems to imply that the resolved element would have the conref 
attribute as specified on the source element.
 
Is this what we want?
 
It seems that the conref resolution process should "use up" the 
conref attribute which should therefore not remain in the resolved 
document.  There may be a risk that the conref will be seen and 
processed again under some circumstances.

Should we amend our wording to indicate that the resolved element's
attribute specifications should not include any conref attribute
specification?
 
paul


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]