W3C home > Mailing lists > Public > www-html@w3.org > May 2005

Re: About XHTML 2.0

From: Orion Adrian <orion.adrian@gmail.com>
Date: Mon, 23 May 2005 13:04:22 -0400
Message-ID: <abd6c80105052310041c63b764@mail.gmail.com>
To: www-html@w3.org

And I agree with most of what you have said, however I do not like
maxims as they feel like religion to me and two, my point made accross
this list several times is that one does not need to address the two
objects separated. If you do, then you have to use something like
<group> and not <separator />. But I'd like to know why you need to
address the peices.

I'm coming here from the literary world where the separation is not
used to create document structure, but used much like an elipsis or
other literatary tool.

Orion Adrian

On 5/23/05, Sebastian Redl <sebastian.redl@getdesigned.at> wrote:
> Mark Birbeck wrote:
> >Mikko,
> >
> >I don't understand why this is getting so complicated. There are plenty of
> >use-cases for something that comes between two items (a separator) in a
> >*semantic* way. That's not presentational, and the two objects being
> >separated are not something that might need a name. It's like a 'pause' when
> >you are reading.
> >
> >
> The two objects separated are, as you say, separate objects. Yet you
> insist on putting them into the same container, without individual
> containers.
> I think a good maxim would be, "Every object gets its own container." If
> no available container tag fits the requirements, then perhaps we should
> add another container element. But not put an empty element in-between.
> There's plenty of use cases for <separator>, you say. Well, there are
> several use cases for <br>, but it still can be completely replaced by
> the <l> tag. Which I, personally, much prefer, because I like to keep my
> documents generic, and that means making every structural element
> (including explicitely separated lines) directly addressable as the
> content of a single tag.
> Objects separated by <br> or <sep> are not addressable. They are
> reflected only by a text node (a rather unstable object that, for
> example, cannot have an ID) in the infoset and the DOM, and it's not
> possible to select them using CSS. That alone makes these tags inferior
> to container tags.
> Sebastian Redl
Received on Monday, 23 May 2005 17:04:28 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:06:10 UTC