Posts Tagged ‘actions’
In Part 3 of this series, Jarek Wilkiewicz details activating the small Knowledge Graph (built on Cayley) with Schema.org Actions. He begins by explaining how Actions can be thought of as a combination of “Entities” (things) and “Affordances” (uses). As he defines it, “An affordance is a quality of an object, or an environment, which allows an individual to perform an action.”
For example, an action, might be using the “ok Google” voice command on a mobile device. The even more specific example that Wilkiewicz gives in the video (spoiler alert) is that of using the schema.org concept of potentialAction to trigger the playing of a specific artist’s music in a small music store’s mobile app.
To learn more, and to meet Jarek Wilkiewicz and his Google colleague, Shawn Simister, in person, register for the Semantic Technology & Business Conference where they will present “When 2 Billion Freebase Facts is Not Enough.”
This week saw schema.org introduce vocabulary that enables websites to describe the actions they enable and how these actions can be invoked, in the hope that these additions will help unleash new categories of applications, according to a new post by Dan Brickley.
This represents an expansion of the vocabulary’s focus point from describing entities to taking action on these entities. The work has been in progress, Brickley explains here, for the last couple of years, building on the http://schema.org/Action types added last August by providing a way of describing the capability to perform actions in the future.
The three action status type now includes PotentialActionStatus for a description of an action that is supported, ActiveActionStatus for an in-progress action, and CompletedActionStatus, for an action that has already taken place.
The Facebook Developer Blog recently announced that the company will be cutting back on Open Graph actions in an effort to reduce spam: “Over the past six months we’ve launched new channels, such as App Center with our improved recommendations engine, to drive distribution to the highest quality apps. As part of these ongoing updates, today we’re releasing improvements to how we present Open Graph stories in news feed and on timeline to drive growth and engagement to your app. In order to provide users with experiences that meet their expectations, we will no longer approve custom actions that publish stories as people consume content. These apps must use the appropriate built-in actions or create a different sharing experience. We are also deprecating a handful of features that led to low quality user experiences.”
Kim-Mai Cutler of TechCrunch noted, “Now apps must use authorized actions like ‘Listen,’ ‘Read,’ ‘Watch,’ ‘Like,’ or ‘Follow’ if they want to automatically publish into the ticker or news feed as they consume content. Developers can still create custom actions like ‘run’ or ‘cook’, but a user has to click a button in order for that activity to be shared. The company is also giving additional distribution to news feed updates that have locations or photos tied to them, since these stories can get 70 percent more clicks if they have decent visuals. Facebook’s Henry Zhang wrote that these stories can see up to 50 times more ‘Likes’ than other stories.”
Image: Courtesy Facebook