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

Re: Schema.org v1.6 release candidate: Roles, various fixes, site navigation improvements

From: Guha <guha@google.com>
Date: Mon, 9 Jun 2014 18:58:18 -0700
Message-ID: <CAPAGhv-L922PhrKS9=CDpHh65+qms9+AnCjpny-3gZPFPkjotQ@mail.gmail.com>
To: "Peter F. Patel-Schneider" <pfpschneider@gmail.com>
Cc: Dan Brickley <danbri@google.com>, W3C Web Schemas Task Force <public-vocabs@w3.org>
On Mon, Jun 9, 2014 at 5:40 PM, Peter F. Patel-Schneider <
pfpschneider@gmail.com
<https://mail.google.com/mail/?view=cm&fs=1&tf=1&to=pfpschneider@gmail.com>>
wrote:

> It seems to me that now consumers of schema.org information have to be
> prepared to accept roles everywhere, whereas before they could expect to
> see actual values (except for strings as things, of course).  Are there any
> limits as to where Roles can occur?  Can properties of Roles be role'd?
>

In theory, yes to both questions, but as with all things in schema.org, we
focus on making the common use case easy as opposed to worrying about
preventing the misuse cases. We went through many different options, all
most all of which avoided this issue you bring up, but unfortunately, we
found that they were much harder to comprehend for those not familiar with
KR concepts.

We allow a certain degree of polymorphism, with strings as valid values of
attributes that expect objects. We are taking this a step further.


>
> How should a consumer of schema.org information count up values?  Suppose
> I have Joe Montana as a direct athlete of the 49er as well as an athlete
> role with athlete Joe Montana?  Is that one or two members?  Suppose there
> are multiple athlete roles with Joe Montana.  How should these be counted?
>
> I would say that how you want to count is completely a function of the
application you want to build. If you are trying to allocate an array to
hold values, probably two. If you want to answer the question of how many
athletes have played with the 49ers, probably one. Again, I don't expect
many sites will want to have both Montana and a role with Montana as values
for the 49ers.


>
> Of lesser importance, the comments in the cited document are different
> from the comments in the appspot.com pages.  The ones in the appspot.com
> pages are much better.  (The document seems to preclude roles being used
> for intermittent situations and for things like CEOs.)
>
> Good catch. We will fix that.


> peter
>
>
>
> On 06/09/2014 01:39 PM, Dan Brickley wrote:
>
>> There is a temporary review build of schema.org v1.6 for your
>> consideration.
>>
>> The main improvement is the addition of a minimalistic Role mechanism,
>> alongside other
>> navigation and bug fixes.
>>
>> Draft release notes copied below. See also
>> https://docs.google.com/a/google.com/document/d/1RSe6zr-
>> -DuIk9AzJyuMfOzw4_kc-DwPbgx2IH9LiCzs/edit?disco=AAAAAJnB6Ew#
>> for background on the Role design.
>>
>>
>
Received on Tuesday, 10 June 2014 01:58:46 UTC

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