W3C home > Mailing lists > Public > w3c-sgml-wg@w3.org > May 1997

RE: Link-2: Pseudo-elements

From: James K. Tauber <jtauber@jtauber.com>
Date: Tue, 20 May 1997 08:40:02 +0800
Message-ID: <01BC64FB.3C31D940@cyg145.dialup.uwa.edu.au>
To: "'Steven J. DeRose'" <sjd@eps.inso.com>, "'Tim Bray'" <tbray@textuality.com>, "w3c-sgml-wg@w3.org" <w3c-sgml-wg@w3.org>

> > I'd be be happy to see CHILD(N) refer to the Nth "proper" element. It is
> > intuitive enough and psuedo-element linking can always be achieved as a type
> > of sub-element linking instead.
> I presume you mean, element as opposed to subelement.

Yep, sorry. The confusion is magnified by the fact 'sub-element' seems to be used in this thread to mean part of an element's content (ie possibly character data).

> But still, how do we refer to content that isn't a whole subelement? That's
> a major subtraction of functionality.

Yes, I agree. But it is separate from the question of what CHILD(N) means. I'd like to see CHILD(N) mean the Nth child *element* and, in addition, would like some means of addressing character data.

For example, it makes it impossible for external links to refer to anything
that the original author didn't tag: like, pointing to a word or phrase and
describing it as a typo, an allusion, a desired link origin, a noun, or
whatever. Bad thing to leave out of a language, IMHO.

That was the very point I made in response to Tim's Link-6 post.

James K. Tauber / jtauber@jtauber.com
Perth, Western Australia
Received on Monday, 19 May 1997 20:52:23 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:25:26 UTC