This page tracks a proposal to revise schema.org's approach to past, present and future Actions in Schema.org.
This work stems from a collaboration amongst the schema.org partners, and supercedes the earlier drafts linked below. Lead editor is Sam Goto <firstname.lastname@example.org> in collaboration with Yaar Schnitman <email@example.com>, Thor Mitchel <firstname.lastname@example.org>, Jason Douglas <email@example.com> and Steve Macbeth <Steve.Macbeth@microsoft.com>. Comments and discussion is welcomed via the W3C firstname.lastname@example.org email list.
Overview (extracted from the pdf)
This document proposes the introduction of intents to the schema.org vocabulary, in the form of a new Class of Things, called Actions.
Actions are used to describe an ability/intent to perform a certain operation (proposed) or an operation that already happened (completed). Each action has corresponding arguments/slots/parameters that are well defined.
Actions define a standard programmatic pre-defined interface between parties (e.g. which arguments "Watching a Movie" takes), and ActionHandlers helps with the mechanisms (e.g. invoking an action via an android intent vs a HTTP GET).
Actions allows the machine-readable brokering language between intent providers, registries and intent consumers.
We use case grammar and framenet to define the semantic roles that are relevant to each verb (e.g. LendAction has a borrower slot).
- TODO(goto): Explore/Design constraints (actions -> entities mappings)
- TODO(goto): Publish Thing.operation (entity -> actions mappings)
- TODO(goto): Publish ActionHandler
- TODO(goto): Publish ActionStatus
- TODO(goto): Publish bug fixes/typos
Publish synsets hierarchy to disambiguate
Publish base Action class and base parameters
Next step (alongside public-vocabs discussion) is to generate a machine-readable schema definition. Dan Brickley will do this.
Some RDFa examples should be added.
See PDF for details.
- Schema.org/Action Draft 4
File:Actions in Schema.org - Draft 3.pdf (pdf)
A revised proposal based on schema.org team discussions, November 2012; see Schema.org Actions (minimal draft) PDF
An RDFS/RDFa schema specifying this (with minor changes) is available in the webschemas mercurial repo
A proposal was made in April 2012, see announcement or full proposal.