- From: Ivan Herman <ivan@w3.org>
- Date: Thu, 20 Jan 2011 15:53:42 +0100
- To: nathan@webr3.org
- Cc: RDFA Working Group <public-rdfa-wg@w3.org>, Manu Sporny <msporny@digitalbazaar.com>
Received on Thursday, 20 January 2011 14:54:06 UTC
I must admit I am lost:-( If the source is that crazy hTtP://something, what should be the output? Is it http://something or should it keep the hTtP stuff? Ivan On Jan 19, 2011, at 23:26 , Nathan wrote: > Hi All, > > It appears that all the major browser vendors do URI/URL normalization on relative refs, and values in common html attribute (@href and @src) - meaning that the URI/IRIs people can pull from RDFa when in an environment don't match the non-normalized RDF URI References intended. > > I've thrown together a quick HTML only page to illustrate: > http://webr3.org/urinorm/html > > And also an XHTML+RDFa 1.0 page here: > http://webr3.org/urinorm/2 > > Also pyRDFa and check.rdfa.info which fully normalizes values, and pyRDFa which seems to have conflicting functionality, producing htTp:// vs http:// depending on whether the value has needed path resolution (whilst treating the rest of the URI as case sensitive, as per RDF specs). > > May be worth checking to see what you're own libraries do with the /2 example. > > Best, > > Nathan > ---- Ivan Herman, W3C Semantic Web Activity Lead Home: http://www.w3.org/People/Ivan/ mobile: +31-641044153 PGP Key: http://www.ivan-herman.net/pgpkey.html FOAF: http://www.ivan-herman.net/foaf.rdf
Received on Thursday, 20 January 2011 14:54:06 UTC