- From: Peter F. Patel-Schneider <pfpschneider@gmail.com>
- Date: Mon, 09 Jun 2014 17:40:25 -0700
- To: Dan Brickley <danbri@google.com>, W3C Web Schemas Task Force <public-vocabs@w3.org>
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? 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? 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.) 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 00:40:55 UTC