W3C home > Mailing lists > Public > public-html@w3.org > July 2007

Re: 3.12.8 dfn automatic cross-referencing

From: Thomas Broyer <t.broyer@gmail.com>
Date: Tue, 31 Jul 2007 16:49:00 +0200
Message-ID: <a9699fd20707310749x2ba02ce3u6f98dc5abbaa3172@mail.gmail.com>
To: public-html@w3.org

2007/7/31, Ben Boyle:
>
> SUGGESTION 1:
> a. for any abbr (maybe other prose elements), if it is contained
> within a dfn ancestor than that dfn comprises the definition
> b. for any abbr (etc.) not contained within a dfn, find a matching
> element (same tagName, same textContent) that is contained within a
> dfn ancestor - let that be the definition.
> (n.b. a @title attribute would take precedence over these steps).
>
> This is fairly similar to the existing algorithm and will work with
> the example. It is not the same though (the current algorithm would
> find a matching dfn element without a nested abbr element).
>
> -------------------------
>
> SUGGESTION 2:
> Another option I'd support (which has been proposed before) would be
> using an idref relationship.
>
> <p>The <dfn id="GDO">Garage Door Opener (<abbr>GDO</abbr>)</dfn>
> is a device that allows off-world teams to open the iris.</p>
> <!-- ... later in the document: -->
> <p>Teal'c activated his <abbr idref="GDO">GDO</abbr>
> and so Hammond ordered the iris to be opened.</p>
>
> I've used @idref as an abstract name to illustrate the concept. I
> would not mind @for if that isn't too much overloading.

SUGGESTION 3:
Attach two "defining terms" to <dfn> instead of one.
I already proposed it in [1] but it was in case the <dfn> had a single
child being an <abbr> with a title attribute. The use case is almost
the same though: being able to refer to a <dfn>/<abbr> without
repeating the title attribute each and every time.

[1] http://www.w3.org/mid/a9699fd20707200102o79b96221nc054f92be2beecb2@mail.gmail.com

-- 
Thomas Broyer
Received on Tuesday, 31 July 2007 14:49:21 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:38:47 UTC