Sure.
Not sure where it should go. In
the <fn> description or in the @id description or both.
My own view is that systems that
put an id on every element are evil and should be discouraged, but that isn’t
an appropriate comment for the DITA spec. :-).
-Jeff
From: Bruce Nevin
(bnevin) [mailto:]
Sent: Thursday, October 29, 2009 9:59 AM
To: Ogden, Jeff;
Subject: RE: [dita] Presence of @id affects processing?
For tools that ID everything, one could in every instance
use <xref type="fn"> in combination with <fn
id="foo">. Advice to that effect might be appropriate?
From: Ogden, Jeff [mailto:]
Sent: Thursday, October 29, 2009 6:49 AM
To:
Subject: RE: [dita] Presence of @id affects processing?
Comments below.
-Jeff
> -----Original Message-----
> From:
[mailto:]
> Sent: Wednesday, October 28, 2009 6:27 PM
> To:
> Subject: [dita] Presence of @id affects processing?
>
> The 1.1 lang spec for <fn/> says that the
presence of the ID attribute
> on <fn/> affects how the footnote is rendered.
Is that true?
[JeffO:] Yes, it’s
true. In retrospect this might not be the best design, but we are stuck
with it now.
> If so, I think we need to mention it in the ID
attribute section of the
> archspec. I'm imagining a tool vendor providing an
option to
> "automatically generate IDs", not knowing
that the presence of the ID
> attribute has processing implications.
>
> Are there other elements for which the presence of
@id has any effect,
> whatsoever?
[JeffO:] Not that I am
aware of, but it is hard to be absolutely certain without rereading the entire
spec. with this in mind.
>
>
> source: http://docs.oasis-
> open.org/dita/v1.1/CD01/langspec/langref/fn.html
>
>
> -seth
