W3C home > Mailing lists > Public > public-vocabs@w3.org > May 2014

Re: Indicating main entity / primaryTopic - proposal to use 'schema.org/about'

From: Jarno van Driel <jarnovandriel@gmail.com>
Date: Tue, 20 May 2014 19:23:35 +0200
Message-ID: <CADK2AU3jgczqguXRow=RogKBBm2QoZqZxuH8kVUMBmzYH2fqCA@mail.gmail.com>
To: Dan Brickley <danbri@google.com>
Cc: Jason Douglas <jasondouglas@google.com>, W3C Web Schemas Task Force <public-vocabs@w3.org>
or:

<body itemscope itemtype="http://schema.org/CollectionPage">
    <link itemprop="about" href="https://www.freebase.com/m/03lty">

    <div itemprop="mainContentOfPage" itemscope itemtype="
http://schema.org/ItemList">
        [...]
    </div>
</body>


2014-05-20 19:19 GMT+02:00 Jarno van Driel <jarnovandriel@gmail.com>:

> OK, that markup surprises me (probable has more to do with me).
>
> I always imagined writing something like:
>
> <body itemscope itemtype="http://schema.org/ItemPage">
>     <link itemprop="about" href="https://www.freebase.com/m/0crgbp8">
>
>     <div itemprop="mainContentOfPage" itemscope itemtype="
> http://schema.org/Product">
>         [...]
>     </div>
> </body>
>
>
> 2014-05-20 19:01 GMT+02:00 Dan Brickley <danbri@google.com>:
>
> On 20 May 2014 17:30, Jason Douglas <jasondouglas@google.com> wrote:
>> > I think you buried the lede in the github link at the bottom.  :)
>> ( https://gist.github.com/anonymous/cf7e24f6378b176aa010 )
>>
>> Ok, let's jump into the markup. It does flush out some issues -
>>
>>
>> > In terms of markup would it be reasonable to do this?
>>
>> Slight tweaks (discussing hashes and slashes with Dan Scott and
>> Stephane Corlosquet in IRC...):
>>
>>  <html vocab="http://schema.org/">
>>    <head>
>>      <link property="about" href="#main_item"/>
>>    </head>
>>    <body>
>>      <div resource="#main_item" typeof="MusicEvent">
>>        ...
>>      </div>
>>    </body>
>>  </html>
>>
>> (this adds a '/' in the @vocab url, and # within @resource attribute)
>>
>> > and rely on an implicit WebPage subject?
>>
>> Looks fine from RDFa point of view. Even though "implicit WebPage" is
>> a schema.org convention, generic RDFa 1.1 parsing would attach the
>> 'about' property to the default base URL, which would be the page.
>>
>> As for Microdata I'm not sure the best pattern, but this with more
>> RDFa-ish structure in the <head> might be bearable:
>>
>> <html>
>>    <head>
>>      <link rel="http://schema.org/about" href="#main_item"/>
>>    </head>
>>    <body>
>>      <div id="main_item" itemscope itemtype="http://schema.org/MusicEvent
>> ">
>>        ...
>>      </div>
>>    </body>
>>  </html>
>>
>>
>> FWIW another everything in the body pattern that works for RDFa (but
>> dips into RDFa 1.1 beyond the Lite subset) is:
>>
>> <div vocab="http://schema.org/" typeof="Person">
>>  <link rev="about" href=""/>
>>  <span property="name">John Smith</span>
>> </div>
>>
>> Which brings me to another issue that's never far away - we have a lot
>> of ways of saying quite similar but different things(*):
>>
>> <div vocab="http://schema.org/" typeof="Person">
>>  <link rel="url sameAs officialWebPage" rev="about" href=""/>
>>  <span property="name">John Smith</span>
>> </div>
>>
>> At least this is pretty compact markup, but we owe the world an
>> account of how at least 'url', 'sameAs' and 'about' interact.
>>
>> e.g. for any x, y where  x--sameAs-->y, is y--about-->x going to be true?
>>
>> sameAs's definition: "URL of a reference Web page that unambiguously
>> indicates the item's identity. E.g. the URL of the item's Wikipedia
>> page, Freebase page, or official website." ... which covers the
>> official website use case.
>>
>>
>> Dan
>>
>>
>>
>> (*) officialWebPage is used by Yandex e.g. see
>> http://help.yandex.com/webmaster/supported-schemas/review-car.xml but
>> similar ideas surfaced here in the social/profile/account discussion
>>
>>
>
Received on Tuesday, 20 May 2014 17:24:03 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:29:41 UTC