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] FW: comments on draft DITA 1.1 Arch Spec.


 

> -----Original Message-----
> From: Grosso, Paul [mailto:pgrosso@ptc.com] 
> Sent: Tuesday, 2006 October 03 10:00
> To: dita@lists.oasis-open.org
> Subject: [dita] FW: comments on draft DITA 1.1 Arch Spec.
> 
> Attached as PDF is an annotated copy of the architectural spec.

Michael et al.,

One comment I wanted to highlight for a timely answer
is where, in the description of the conref attribute,
the latest spec now says:

 When the referencing and targetting [sic] elements
 have attributes, the resolved element should have
 both sets of attributes. When the attributes conflict
 (for example, both referencing and target elements
 have an id attribute), the referencing element's
 attributes take precedence.

The spec didn't used to say this, and in the past,
our assumption was that the referencing tag (and 
all its attributes) were used for the resolved
element's start tag, and the target element's contents 
(but not its start tag attributes) were used for the 
contents of the resolved element.

It may be that the older spec was ambiguous enough
to allow both interpretations [in which case, it's
a good thing we're adding this clarification now
in response to earlier reviews], but I did want to
ensure that the latest wording is really what we all
want it to say.  It is going to require changes in
implementations, at least for us, so I wanted to get
a definitive answer soon.

paul


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