hydra for web annotations
DESCRIPTION
Recent activity in adding actions to schema.org and the Hydra CG allow for new mechanisms to automatically provision applications to interact with web services. Coupled with semantic markup of web-pages using RDFa or microdata, actions can provide a mechanism annotating web pages specifically provisioned for this, in cooperation with the publishing service. JSON-LD enables a common language to be used among services, so that clients can have a single format for communicating actions to a service, even if the details vary between different service providers. Annotating web pages not specifically provisioned for actions may be accomplished in a similar way by using semantic markup inherent in HTML5 documents. Using an operation overlay, annotation operations (and really any other type of action) cold be supported by a third-party annotation service, which implicitly adds markup to a page (using JQuery, for example) which describes alternative service endpoints for sending such operations. When a common overlay service is used by many users, the annotations and other operations performed within a community may become generally available.TRANSCRIPT
Hydra for Web Annotations
Gregg Kellogg W3C Annotation Workshop, San Francisco CA
2 April 2014
What is Hydra?• W3C Community
Group for Linked APIs
• REST + Linked Data
• “At the intersection of web schemas and RESTful web applications” © http://vonwong.com
Automated API Provisioning• Problem: How do I use an API without specifically
coding for it?
• Answer: Use vocabulary to define operations on classes and properties
• Proposition: Annotations are the result of operations on entities or the relationships between entities.
• Those results are also entities, which may be operated upon.
Use Case: Q/A• Given profile page for a
Sports Personality, how can I interact with that entity?
• follow
• (dis)like
• share
• question
• suggest relation
Links and Operations• Define operations on entities, types of entities, or their
properties.
• When does a property link to an entity?
• How do you use pagination to reference and collect linked entities?
• What operations can I perform on an entity, or property of that entity?
• Where does authentication/authorization intersect with generic API interactions?
