- From: Markus Lanthaler <markus.lanthaler@gmx.net>
- Date: Wed, 13 Nov 2013 19:55:48 +0100
- To: <public-hydra@w3.org>, "'W3C Web Schemas Task Force'" <public-vocabs@w3.org>
- Cc: "'Thad Guidry'" <thadguidry@gmail.com>, "'Sam Goto'" <goto@google.com>, "'Dan Brickley'" <danbri@google.com>
On Wednesday, November 13, 2013 7:46 PM, Dan Brickley wrote: > On 13 November 2013 18:27, Markus Lanthaler wrote: > > Yes, but that's still the same API, i.e., Netflix'. What's not clear to me > > at the moment is whether you interested in cross-service relationships like > > finding a movie on Hulu and playing it on Netflix. The latest draft you > > published a couple of days suggests you aren't. So why would the approach is > > proposed not work in this case? > > I'd suggest that would be a product design / business decision amongst > implementors. If you have a standard way to know that item123151 on > Hulu and item6234623 on Netflix are both versions of the film known to > Wikipedia as http://www.wikidata.org/wiki/Q108745 then you have most > of the raw materials for this. Whether some product/application builds > such service-hopping features is quite another matter. Fully agreed. That's why I have such a hard time understand Sam's "action -> entities problem". -- Markus Lanthaler @markuslanthaler
Received on Wednesday, 13 November 2013 18:56:25 UTC