W3C home > Mailing lists > Public > public-rdfa-wg@w3.org > June 2010

Re: Fragments in <base href>

From: Mark Birbeck <mark.birbeck@webbackplane.com>
Date: Tue, 22 Jun 2010 14:30:07 +0100
Message-ID: <AANLkTins1dLvEQU89_jyH5eS5nobTSLJAM13IlGR17lg@mail.gmail.com>
To: Toby Inkster <tai@g5n.co.uk>
Cc: public-rdfa-wg@w3.org
Hi Toby,

It's this one:

  <> xhv:test <> .

You get the base path by creating an absolute path based on the value
in 'base'. And even if the base URI has a fragment identifier, the
fragment identifier is dropped.

I.e.,:

  assert.areEqual(
    absolute("http://example.net/#foo", ""),
    "http://example.net/"
  );

This is definitely mentioned in the RDFa 1.0 spec, although I don't
have time to look for it at the moment.

Regards,

Mark


On Tue, Jun 22, 2010 at 11:15 AM, Toby Inkster <tai@g5n.co.uk> wrote:
> So how is the following to be interpreted?
>
>        <html>
>                <head rel=":test" resource="">
>                        <base href="http://example.net/#foo" />
>                </head>
>        </html>
>
> I can imagine arguments in favour of:
>
>        <#foo> xhv:test <> .
>        <#foo> xhv:test <#foo> .
>        <> xhv:test <> .
>
> I think this needs clarification; not just in RDFa 1.1, but also as an
> errata for RDFa 1.0.
>
> --
> Toby A Inkster
> <mailto:mail@tobyinkster.co.uk>
> <http://tobyinkster.co.uk>
>
>
Received on Tuesday, 22 June 2010 13:30:42 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 04:55:06 GMT