New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Specifying when/where an Action may be performed #1741
Comments
This got used at Google https://developers.google.com/actions/media/tv-movies-specification (we document use of at least ActionAccessSpecification, MediaSubscription, actionAccessibilityRequirement, authenticator, availabilityEnds, availabilityStarts, category, eligibleRegion, expectsAcceptanceOf, requiresSubjection. ) |
Hi, Can we in any way add "eligibleRegion" and "ineligibleRegion" markup in my Sports video content or is the specific for Music, TV Show and Movies? |
Just a generic comment: While I think the reuse of such properties is a quick and pragmatic solution, it is one step further towards changing the definition of a property from a global one (identical for all types with which it is being used) to a frame-based/local definition, where a property's meaning is actually defined at the level of the type. In some cases, this is no big deal, as a broader textual definition will do. But in general it makes the vocabulary less maintainable. I think I suggested a few years ago to introduce a defined mechanism for this, with a default definition and text for a property at the global level and the possibility to override the definition (at least the text) at the level of a particular type. |
What if availabilityEnds is unspecified? Should it be null or should we use the SQL 12/31/9999, 12/30/9999 solution? |
Many Action links, particularly for consuming media, are limited by time and/or region based on the complexities of licensing. For example, a user may only be able to listen to a song after a certain date or read a book in a certain country. To help authors describe the access restrictions for performing an Action, I am proposing adding the following:
expectsAcceptanceOf: This property already exists. We would add it to ActionAccessSpecification to allow authors to say an Offer must be accepted before the Action can be performed. This is used in cases where users must purchase or rent access to the item.
ConsumeAction
to specify the requirements needed to access the Action.An example may look like:
The text was updated successfully, but these errors were encountered: