W3C home > Mailing lists > Public > www-tag@w3.org > September 2002

RE: two failings of XLink

From: Didier PH Martin <martind@netfolder.com>
Date: Fri, 27 Sep 2002 17:03:22 -0400
To: "'Ann Navarro'" <ann@webgeek.com>, "'Tim Bray'" <tbray@textuality.com>, <www-tag@w3.org>
Message-ID: <000901c26669$51193180$c801a8c0@didierhome>

Hi Ann,

Ann said:
The HTML WG can't simplify our needs based on whether something like 
'longdesc' is or isn't typically used. It is a constraint placed on us
by 
the WAI folks, which means it's a constraint placed on our acceptance of

linking solutions.

Didier replies:
Pardon my ignorance but in which ways the WAI folks impose to the HTML
WG to specify the <img> element (as a use case) as Tim mentioned using
an Xlink extended link. What are these constraints?

Ann said:
You don't want HLink? Fix XLink, we'll be happy to use it if we can meet

all OUR requirements when doing so, since we can't ignore or drop them
at 
will.

Didier replies:
Does fixing xlink mean that there are no way to redesign some XHTML
elements? In which ways the ones you already redesigned satisfy the WAI
criteria? Just curious to know the internal intricacies that lead to
this deadlock.

Cheers
Didier PH Martin 
Received on Friday, 27 September 2002 17:03:43 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 26 April 2012 12:47:11 GMT