- From: Dan Brickley <danbri@google.com>
- Date: Wed, 24 Sep 2014 20:15:58 +0100
- To: "Peter F. Patel-Schneider" <pfpschneider@gmail.com>
- Cc: Vicki Tardif Holland <vtardif@google.com>, "Jason Johnson (BING)" <jasjoh@microsoft.com>, W3C Web Schemas Task Force <public-vocabs@w3.org>, Gregg Kellogg <gregg@greggkellogg.net>
On 24 September 2014 19:59, Peter F. Patel-Schneider <pfpschneider@gmail.com> wrote: > Intriguing. > > Is there going to be a non-trivial theory of sports. For example, will > there be sub-sports? At this point, I suggest just an URL attachment point for well known identifiers. Baby steps... Dan > peter > > > On 09/24/2014 11:19 AM, Dan Brickley wrote: >> >> >> On 24 Sep 2014 18:48, "Vicki Tardif Holland" <vtardif@google.com >> <mailto:vtardif@google.com>> wrote: >> > >> > >> > On Wed, Sep 24, 2014 at 1:37 PM, Gregg Kellogg <gregg@greggkellogg.net >> <mailto:gregg@greggkellogg.net>> wrote: >> >> >> >> A "namedPosition" property would be fine, as long as the range is not >> schema:Text. IMO, something like this should use URIs for such enumerated >> values. Schema.org always allows falling back to text. >> > >> > >> > I am looking at http://sdo-sports.appspot.com/OrganizationRole. The >> range >> is URL or text. I agree that URIs should be used to have any hope of >> understanding what the value means. >> >> Yes, I'm also updating 'sport' property similarly. >> >> Dan >> >
Received on Wednesday, 24 September 2014 19:16:25 UTC