RE: longdesc Re: Clarification of rational for deprecation...

-----Message d'origine-----
De Charles McCathieNevile

> ( Quel glandage... just manually edit it llike I do :P )

Sure will. :)

Your arguments (not quoted for the sake of brevity) are all very defendable
and show indeed that @longdesc as an attribute pointing to a resource is
better.

On the CMS side:

>> Also, it would be simpler to implement in industrial CMS's, who are 
>> notoriously bad at providing easy longdesc mechanisms.

>I am not sure that this is the case. (I agree CMS' have done a terrible job
>so far, but I don't see how the current model is easier or harder than your
>proposed one).

In a CMS, what can be done nowadays is this:
1. I create a page that features an image that should require a @longdesc
2. I have to go back to the CMS's "new page" feature to create a longdesc
page for this image. This longdesc page should not be publicly listed the
way other pages are listed, because it is not autonomous content per se and
is not the same as any other article.
3. Then I go back to my article and find a way to write the @longdesc for
this image (not the easiest)

I'm not saying it could not be easy. I did tweak the templates my CMS is
using so that images can have almost-automatic @longdescs if they exist. But
I'm saying it's complicated on an industrial basis. Much more than laying
out plain content in the page itself.

But, true, the problem is more ATAG than HTML.

Consider me a +1 on the @longdesc without changing it to a <longdesc> or
<div longdesc="">, then.

--
Best regards,
Stéphane Deschamps
  Web HCI expert
  orange / france telecom group 



*********************************
This message and any attachments (the "message") are confidential and intended solely for the addressees. 
Any unauthorised use or dissemination is prohibited.
Messages are susceptible to alteration. 
France Telecom Group shall not be liable for the message if altered, changed or falsified.
If you are not the intended addressee of this message, please cancel it immediately and inform the sender.
********************************

Received on Wednesday, 6 February 2008 13:15:32 UTC