W3C home > Mailing lists > Public > public-vocabs@w3.org > June 2012

Re: schema.org/sameThingAs proposal

From: Ed Summers <ehs@pobox.com>
Date: Wed, 27 Jun 2012 09:36:20 -0400
Message-ID: <CABzDd=75dR+y3unev+4xBh2BPzmnCfyf67zLCzYtaGWXDkDVBA@mail.gmail.com>
To: Dan Brickley <danbri@danbri.org>
Cc: public-vocabs@w3.org
Thanks for the update Dan!

On Fri, Jun 22, 2012 at 11:21 AM, Dan Brickley <danbri@danbri.org> wrote:
> For a motivating scenario, see IMDB's current schema.org descriptions
> (copied here from the Wiki page),
> <h4>Stars:</h4>
> <a href="/name/nm0010930/"   itemprop="actor">Douglas Adams</a>,
> <a  href="/name/nm0048982/"   itemprop="actor">Tom Baker</a>
> and <a  href="/name/nm3035100/"   itemprop="actor">Hans Peter Brondmo</a>
> </div>

So how would sameThingAs be used in this example?

I'm finding it a bit hard to disambiguate between the use of
schema:url and schema:sameThingAs. I don't see how calling it
sameThingAs makes it easier to "reconstitute a useful
entity-relationship data graph from markup"; if anything I think it
could make it harder, since now you have to look for two itemprops
(schema:url and schema:sameThingAs) instead of one. Can you flesh out
the difference a bit more either here, or on the wiki page?

One argument that could potentially be made is that 'url' is (in name)
constrained to resolvable, mostly http URIs ... whereas sameThingAs
could point at URIs (URNs, etc). But I'm not sure this is a terribly
convincing argument :-)

Received on Wednesday, 27 June 2012 13:36:49 UTC

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