Posts Tagged ‘Jarek Wilkiewicz’

Add schema.org Actions to Your Own Knowledge Graph (Video — Part 3)

[Editor's note: this is Part 3 of a series. See Part 1 and Part 2]

schema dot org logoIn 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.”

How to Build Your Own Knowledge Graph (Video – Part 1)

Photo of Jarek WilkiewiczStraight out of Google I/O this week, came some interesting announcements related to Semantic Web technologies and Linked Data. Included in the mix was a cool instructional video series about how to “Build a Small Knowledge Graph.” Part 1 was presented by Jarek Wilkiewicz, Knowledge Developer Advocate at Google (and SemTechBiz speaker).

Wilkiewicz fits a lot into the seven-and-a-half minute piece, in which he presents a (sadly) hypothetical example of an online music store that he creates with his Google colleague Shawn Simister. During the example, he demonstrates the power and ease of leveraging multiple technologies, including the schema.org vocabulary (particularly the recently announced ‘Actions‘), the JSON-LD syntax for expressing the machine readable data, and the newly launched Cayley, an open source graph database (more on this in the next post in this series).

Read more