W3C home > Mailing lists > Public > public-swd-wg@w3.org > July 2007

Re: [RDFa] ISSUE-9: META and LINK in the body

From: Mark Birbeck <mark.birbeck@x-port.net>
Date: Thu, 5 Jul 2007 10:05:26 +0100
Message-ID: <640dd5060707050205t1e114871lf7499a7b9e369e2c@mail.gmail.com>
To: "Ben Adida" <ben@adida.net>
Cc: RDFa <public-rdf-in-xhtml-tf@w3.org>, "SWD WG" <public-swd-wg@w3.org>

HI Ben,

All fair points.

+1 for simply leaving this out of our current drafts (as opposed to
ruling it out altogether, since as you say, there may be dialects of
RDFa that can cope with this in the future).

By the way, even though IE doesn't move the mark-up, it's still not
straightforward to parse, since <meta>, "some text" and </meta> are
seen by IE as three separate sibling nodes. Once you start having to
hack like that, you do wonder whether it's the right thing to be
doing. :)



On 04/07/07, Ben Adida <ben@adida.net> wrote:
> Hi all,
> ISSUE-9 was initially about nested META and LINK, but I'll use common
> sense here and extend this issue to include the crux of what we're
> thinking about right now, which is to kill LINK and META in the body
> altogether, at least in XHTML1.1+RDFa.
> I'm tempted to agree with Mark that LINK and META should no longer
> appear in the body. That said, to play devil's advocate for a second, I
> note that LINK and META do *not* get repositioned in the DOM when the
> doc is served as application/xhtml+xml. I want to make sure we have all
> data points in mind before we strike those from the spec.
> In particular, I want to point out that *if* we do this, then we're
> almost certainly forced to either have @href everywhere or @resource
> everywhere to reenable the expression of certain triples, since
> effectively we'll now want to place the @href/@resource on the parent
> element of where the LINK used to be. We'll also have to consider what
> to do to make it easier to do the following:
> =====
> <p>
> <meta property="foaf:name">Mark Birbeck</meta>
> ...
> </p>
> =====
> Maybe we think it's unlikely that the above will occur as is, that the P
> has to be related to the rest of the page, so it will likely be:
> =====
> <p rel="dc:creator">
> <span property="foaf:name">Mark Birbeck</span>
> ...
> </p>
> =====
> where the @rel automatically stripes and sets a bnode subject.
> I just want to put these issues out there so we're all thinking
> carefully about the consequences of our actions as we speed towards
> finalizing our spec!
> -Ben

  Mark Birbeck, formsPlayer

  mark.birbeck@x-port.net | +44 (0) 20 7689 9232
  http://www.formsPlayer.com | http://internet-apps.blogspot.com

  standards. innovation.
Received on Thursday, 5 July 2007 09:05:42 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:31:44 UTC