W3C home > Mailing lists > Public > www-html@w3.org > July 2003

Re: WD-xhtml2-20030506: <qst>ions and <ans>wers

From: Daniel Brockman <daniel@brockman.nu>
Date: Sat, 26 Jul 2003 03:06:58 +0200
Message-ID: <001c01c35312$367eeb30$64b670d5@wigwam>
To: <www-html@w3.org>

Hi all,

I don't think the <qa> element is a bad idea per se, but I'm wondering if a
more generic associative/grouping element would be more useful. Essentially
it would be like a definition list, only it associates flow content with
flow content, instead of inline content with flow content. I'm thinking you
could use it for all sorts of things besides the question/answer list;
however, I can't immediately see many such potential usage cases. Where do
we have relations between flow? How about annotated text?

One issue, of course, is what the implied semantics of such an element
should be. Would it be commutative, or would the items in it have different
roles like in definition lists? That is, should the first item be the
"header" and the rest the "content," or should they be of equal
"importance"? Sorry about the lack of propery terminilogy here.

I haven't given this much consideration; it was just something that occured
to me as I read the discussion about <qa> and I thought you people might
want to investigate it further. One thing I do know is that I do not want
any element whose semantics are not clearly and thorougly defined, so keep
this out of there unless you can think of clear uses for it. (Obviously, I
don't need to tell you guys; I'm just covering my own back.)

Anyway, thank you for your time.


Regards,

Daniel Brockman
daniel@brockman.nu
Received on Friday, 25 July 2003 21:09:16 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 March 2012 18:15:56 GMT