On Feb 9, 2011, at 07:40 , Toby Inkster wrote: > On Tue, 08 Feb 2011 16:34:54 +0000 > Nathan <nathan@webr3.org> wrote: > >> I was just suggesting that we changed the value space of @profile to >> be absolute-URI, because then regardless of whether somebody wrote >> http://a.b.c/e or http://a.b.c/e#f or http://a.b.c/e#g in @profile, >> it would always be seen as http://a.b.c/e . > > My suggestion: > > - consumers MUST support fragment identifiers in profile URIs > (by simply trimming them off); and I do not even think we should specify trimming; this is something that is done by HTTP anyway. I agree with the MUST > - publishers MUST NOT publish documents referring to profile MUST->SHOULD I see no reason the so strongly disallow them. Except for... > URIs with fragment identifiers. > > This gives future RDFa Working Groups an extension point: they can > assign meaning to a fragment ID on a profile. ... this of course but, I must admit, I simply do not see any use case for this so again, why bother that much? :-) Ivan > > -- > Toby A Inkster > <mailto:mail@tobyinkster.co.uk> > <http://tobyinkster.co.uk> > ---- 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 Wednesday, 9 February 2011 07:57:49 UTC