- From: Ivan Herman <ivan@w3.org>
- Date: Wed, 16 Nov 2011 16:40:44 +0100
- To: W3C RDFWA WG <public-rdfa-wg@w3.org>
FYI and for archiving on the tracker Begin forwarded message: > Resent-From: public-html-data-tf@w3.org > From: Henri Sivonen <hsivonen@iki.fi> > Date: November 16, 2011 14:27:44 GMT+01:00 > To: public-html-data-tf@w3.org > Cc: w3c@adambarth.com > Subject: Re: Parsing Microdata into RDF Graphs: URI Comparison > archived-at: <http://www.w3.org/mid/CAJQvAudbB55EDCGXF5anHdXeSdLKv06rfBs=7DzxdYXi7kH5WA@mail.gmail.com> > list-id: <public-html-data-tf.w3.org> > > On Sun, Oct 30, 2011 at 8:50 AM, Jeni Tennison <jeni@jenitennison.com> wrote: >> I wonder if you could help here. Do you know of examples where the HTML URL resolution algorithm produces different results from the RFC-3987 resolution algorithm? > > The RFC's algorithm doesn't consider the encoding of the document the > URL is in as an input to the algorithm. The HTML algorithm does. So if > the URL being resolved contains non-ASCII characters and the context > of the URL was not UTF-8 or UTF-16-encoded, the results between the > HTML algorithm and the RFC algorithm would differ. > > There might be other differences around edge cases that the RFC > considers invalid. > >> Is there a publicly available test suite that you know of or a tool that you know does HTML URL resolution correctly that could be used to generate accurate tests? > > I don't know. Adam Barth (CCed) might know. > > -- > Henri Sivonen > hsivonen@iki.fi > http://hsivonen.iki.fi/ > ---- Ivan Herman, W3C Semantic Web Activity Lead Home: http://www.w3.org/People/Ivan/ mobile: +31-641044153 FOAF: http://www.ivan-herman.net/foaf.rdf
Received on Wednesday, 16 November 2011 15:38:07 UTC