Welcome to WebHeadStart.org

Web Technologies

Sponsored By

WebHeadStart.org is currently in beta.
Please pardon our appearance as we work to provide you with the most comprehensive reference on today's web technologies.

Interested in advertising on WebHeadStart? Become an advertising partner today!

[WWW-HTML Mailing List Archive Home] [Messages By Thread] [Messages By Date]

Re: XHTML 2 current WD makes achieving WCAG 1.0-A compliance impossible; a proof

From: Steven Pemberton <steven.pemberton@cwi.nl>
Date: Thu, 12 Oct 2006 13:21:46 +0200
To: mark.birbeck@x-port.net
Cc: www-html@w3.org, RDFa <public-rdf-in-xhtml-tf@w3.org>
Message-ID: <op.tha26kqcsmjzpq@acer3010.lan>

On Thu, 12 Oct 2006 11:44:31 +0200, Mark Birbeck <mark.birbeck@x-port.net>  
wrote:
> I'm worried that you are worried! :)

That's a relief then!

> However, that was only one of Cecil's points. The other was the use of
> @title on <link>, and my point is simply that, although our rules
> indicate that this is possible:
>
>   <link rel="meta" href="OurICRAPolicy.rdf">
>     <meta property="title">ICRA</meta>
>   </link>
>
> there has been some discussion over on RDFa about changing the meaning
> of this.

Ah, I see. In other words, for the case of <link>. So you still agree that  
this is OK:

	<p>
		<meta property="title">Not pain but <em xml:lang="fr">pain</em></meta>

> I'm therefore saying that Cecil's post is a very useful
> reminder of why we need to ensure that the mark-up I've just used
> yields the correct triples to support his use-case.

Agreed. It would be unfortunate if it worked for some elements, and not  
others.

Fears allayed.

Thanks!

Steven
Received on Thursday, 12 October 2006 11:22:00 GMT
Valid XHTML 1.0! Valid CSS! Site Map | Privacy Policy | Terms of Use | WebHeadStart.org © 2005 All Rights Reserved.