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

Re: conflation of issues or convergence of interests?

From: Ben Boyle <benjamins.boyle@gmail.com>
Date: Sun, 29 Jul 2007 11:26:39 +1000
Message-ID: <5f37426b0707281826l11a18511p6bf2cdbfd5e87d18@mail.gmail.com>
To: "Sander Tekelenburg" <st@isoc.nl>
Cc: public-html@w3.org

> Agreed. HTML5 offers a great improvement in defining the relation between
> complimentary content. But I don't see how any of these features allow
> authors to definite of the relationships between equivalents.

You're right. I was talking about associating the surrounding
contextual information, not equivalents.

There are three things I want to be able to do:

1. identify the related (and exclude non related) information
surrounding embedded media. I believe this can be accomplished using
the section elements, as noted in my previous post.

2. provide alternative information when the media is not rendered. I
prefer the fallback model available with object/video/audio for this
(I believe it provides the best flexibility to authors).

3. provide equivalent information in the same page and explicitly
identify this relationship. For example, if I authored a page with an
embedded video, I might also include a transcript using <dialog> with
narration set against screenshots of key visuals. I want the
transcript to be shown to everyone, regardless of whether the video is
supported. If the video and transcript sit side by side, then I don't
know of a way to mark that relationship as "equivalent". I'm not sure
I need to though, I would probably be happy to either:
(a) group them all together with a section and trust that they are
"related" and let the headings and order of information (I would not
put the video first) provides enough information to the user
(b) replace the first key visual with <video> which has an <img> fallback.

I've now practically talked myself out of needing a way to capture
"equivalence" in my markup. But this is a very specific use case. I'd
love to hear of some better scenarios, let's talk about content that
demonstrates these problems and see what we can do with HTML5 and if
we really need additional markup to capture relationships.

We might also get some tutorials out of it!

cheers
Ben
Received on Sunday, 29 July 2007 01:26:58 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:16:02 GMT