Fwd: Re http://www.w3.org/2001/tag/group/track/actions/510

Looking back through the the archive I see sent this to the TAG list instead of the
 the HTML working group list. My apologies.
I had wondered why nothing else had happened in response.

This is a serious bug and one which apparently remains in http://dev.w3.org/html5/md-LC/

Tim

Begin forwarded message:

> From: Tim Berners-Lee <timbl@w3.org>
> Date: 2011-04-19 19:14:53 GMT+02:00
> To: TAG List <www-tag@w3.org>
> Subject: Re http://www.w3.org/2001/tag/group/track/actions/510
> 
> Reading http://dev.w3.org/html5/md/#examples
> 
> Taking an action from the TAG meeting:
> re: action http://www.w3.org/2001/tag/group/track/actions/510
> 
> This note passes on concern the TAG had about the appalling
> URIs generated in the procedures described in the HTML5 spec at
> http://dev.w3.org/html5/md/#examples
> 
> In the example, the HCARD data is to be parsed to produce RDF data with a predicate whose URI is
> http://www.w3.org/1999/xhtml/microdata#http://microformats.org/profile/hcard%23:adr
> That is an appalling URI, for a number of reasons.
> 
> 1. It is horribly long
> 
> 2. It is constructed including two other URIS, so that there is a combination of two authorities, so it will only be supported if the w3.org and mictorformats.org sites coordinate the generation of new microformats.   It makes W3C responsible for supporting things added in microformats.org which, while W3c may need to do this special cases should not be built into the semantics of the HTML language.
> 
> 3. Because it has a hash in he middle instead of at the end, typical serializers won't be able to use namespace prefix on output, so any files which use these URLs  will by ugly, unreadable, and large.
> 
> There may be other serious flaws with the RDF mapping described there, but that one jumps out.
> 
> Tim
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>