Re: Schema.org Actions - an update and call for review

On Wed, Nov 13, 2013 at 12:55 PM, Markus Lanthaler <markus.lanthaler@gmx.net
> wrote:

> 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
>
>
Sam works for Google.  They build and provide aggregating service-hopping
features into Search Results... ALL THE TIME.

Hence his need to understand a greater scope of effort of
supportedProperties against something like when a search user types "watch
breaking bad" and his team has to create a holistic view for this user.

The view would be that large wrapper around the entity "breaking bad" with
many "watch now" or "rent me now" or "rent me from date(x) to date(z)"
relationships to all the services out there.

He then needs to provide an API for that large wrapper or view for his
consumers... and hence his questions about "How the hell do I model a
"service wrapper" for the future" ?  ... the "service wrapper" just needs
to be disguised easily as the class, I think... of supportedProperties for
the future that can change.

Notifying users of changes will depend on the context of the consumer and
how they are consuming the services through the API, I would think.  I do
not think that 1 size fits all regarding change notification, but I could
be wrong in Google's and Sam's use case.

-- 
-Thad
+ThadGuidry <https://www.google.com/+ThadGuidry>
Thad on LinkedIn <http://www.linkedin.com/in/thadguidry/>