W3C home > Mailing lists > Public > public-html-data-tf@w3.org > October 2011

Re: Data blocks, not marked up content

From: Stéphane Corlosquet <scorlosquet@gmail.com>
Date: Fri, 7 Oct 2011 10:54:48 -0400
Message-ID: <CAGR+nnFChs2Wk=YWhuUaEx=q9u=2OcD=jR_LH8HmoU=R6Yt=YA@mail.gmail.com>
To: Lin Clark <lin.w.clark@gmail.com>
Cc: Jeni Tennison <jeni@jenitennison.com>, public-html-data-tf <public-html-data-tf@w3.org>
On Fri, Oct 7, 2011 at 10:50 AM, Lin Clark <lin.w.clark@gmail.com> wrote:

>
>> Another limitation of <link> and <meta> is that they cannot be nested. So
>> while they are handy for adding properties to an existing item in content
>> flow, they are not the best approach for more stand alone snippets like the
>> ones Gavin posted, where nesting is preferable and more human friendly. To
>> avoid nesting and keep a flat set of HTML elements in <head>, you could use
>> @about (à la N Triples) or @itemref which would lead to
>> more complicated markup.
>>
>>
> I'm not sure I see the limitation here. You can wrap <div> or <span> tags
> around the <link> and <meta> elements to nest them. The <div> or <span> is
> an item, while the <meta> or <link> contain string properties.
>

sorry for being not clear. I was replying in the context of having this
markup in <head>. Yes, you can wrap <link> and <meta> with <div> in the
body, but this is not a portable syntax as this won't be valid markup if
moved in the <head>.

hope that's more clear? :)

Steph.
Received on Friday, 7 October 2011 14:55:17 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 7 October 2011 14:55:17 GMT