Hi guys, i am not sure exactly what this implies can we parse this into actions for us? Gio
---------- Forwarded message ---------- From: Martin Hepp <[email protected]> Date: Sat, Oct 29, 2011 at 11:27 AM Subject: Fwd: Canonicalizing relative URLs seen in URL type properties? To: Giovanni Tummarello <[email protected]> Please relay this to your Microdata parser guys. It is important that Microdata content being imported to Sindice is compliant with this; otherwise somw queries will not trigger. Martin Begin forwarded message: > From: Philip Jägenstedt <[email protected]> > Date: October 26, 2011 10:16:18 AM GMT+02:00 > To: "Martin Hepp" <[email protected]> > Cc: [email protected] > Subject: Re: Canonicalizing relative URLs seen in URL type properties? > > On Tue, 25 Oct 2011 18:46:11 +0200, Martin Hepp > <[email protected]> wrote: > >> Hi Philip, >> >> I am still unconvinced that normalizing property values is a good thing, >> because it would mean >> >> a) you have to execute an http GET for handling every single property value >> or >> b) implement the normalization rules for any of the URI schemes out there >> (e.g. FTP, mailto, ...) - and what about non-registered public schemes? > > You need to implement the "resolve a URL" algorithm [1] which takes care of > all of this and does not have any scheme-specific rules AFAICT. > >> IMO, it would be better to treat URIs as identifiers simply as strings, with >> maybe minimal character encoding normalization. >> >> Also, I must say that the different handling of URI normalization depending >> on whether used for itemtype, itemprop, or href/item value reminds me of the >> worst features of RDFa in terms of complexity. > > The only values that are resolved are the property values in the href/src > attributes on a, area, audio, embed, iframe, img, link, object, source, > track, and video elements. Not doing this would make microdata useless for > marking up relative URLs, while trying to be "consistent" and resolving all > URLs would also mean resolving the itemprop tokens (which can be absolute > URLs), which just doesn't make any sense in the microdata model. > > In any event, feel free to file spec bugs for things that are confusing or > that you want changed. That's what I do and sometimes I get my way. > > [1] > http://www.whatwg.org/specs/web-apps/current-work/multipage/urls.html#resolve-a-url > > -- > Philip Jägenstedt > Core Developer > Opera Software
