Foundational Specifications

12
@azaroth42 Foundational Specifications Rob Sanderson [email protected] Foundational Specifications International Image Interoperability Framework

Transcript of Foundational Specifications

Page 1: Foundational Specifications

@azaroth42

Fou

nd

atio

nal

Spec

ific

atio

ns

Rob [email protected]

Foundational Specifications

InternationalImageInteroperabilityFramework

Page 2: Foundational Specifications

@azaroth42

Fou

nd

atio

nal

Spec

ific

atio

ns

A Communitythat develops APIs,

…shh … secret third line…implements them in Software,

and exposes interoperable Content

Page 3: Foundational Specifications

@azaroth42

Fou

nd

atio

nal

Spec

ific

atio

ns

A Communitythat develops APIs,

based on Web Standards,implements them in Software,

and exposes interoperable Content

Page 4: Foundational Specifications

@azaroth42

Fou

nd

atio

nal

Spec

ific

atio

ns

Web Standards

• Linked Open Data• JSON-LD• Linked Data Platform• Media Fragments• Open Annotation• Activity Streams• Webmention

Just putting the puzzle pieces togetherwith a little glue to make it stick

Page 5: Foundational Specifications

@azaroth42

Fou

nd

atio

nal

Spec

ific

atio

ns

Linked Open Data

• Use URIs to name things

• Use HTTP URIs

• Provide useful information

• Link to other things

Be part of the web, not just on the web

Page 6: Foundational Specifications

@azaroth42

Fou

nd

atio

nal

Spec

ific

atio

ns

JSON-LD

Developer friendly way to express Linked Data

{

“@context”: ”http://iiif.io/api/presentation/2/context.json”,

“@id”: “http://example.org/iiif/book1/manifest”,

“@type”: “sc:Manifest”,

“label”: “Book 1”,

“metadata”: [

{“label”: “Author”, “value”: “A. Authorus”}

],

“license”: ”http://example.org/rights/license.html”,

“sequences”: [ … ]

}

Page 7: Foundational Specifications

@azaroth42

Fou

nd

atio

nal

Spec

ific

atio

ns

Linked Data Platform

• Information management protocol for Linked Data

• REST principles

• Containers

• JSON-LD (and Turtle)

• Non Linked Data

• Can create links automatically

Page 8: Foundational Specifications

@azaroth42

Fou

nd

atio

nal

Spec

ific

atio

ns

Media Fragments

• URI Fragments identify part of the resource

• … for Timed Media

• Area in space

• Duration in time

• Image API

• Presentation API

• Future Audio/Video API

Page 9: Foundational Specifications

@azaroth42

Fou

nd

atio

nal

Spec

ific

atio

ns

Open Annotation

• Current: W3C Community Group specification

• Coming: W3C Technical Recommendation

• Presentation API

– Painting resources

– ”Regular” annotations

• Search API

– Transcription/OCR

– But really any annotation

Page 10: Foundational Specifications

@azaroth42

Fou

nd

atio

nal

Spec

ific

atio

ns

Activity Streams

• Semantic description of an “activity”

• Describe: Who, What, On/With What, Where, When

• Logging/Description, not Notification/Protocol

• Presentation, Search:

– Collections for Paging

– Synchronization

– Other use cases?

Page 11: Foundational Specifications

@azaroth42

Fou

nd

atio

nal

Spec

ific

atio

nsWebmention

• Very simple specification for notifications

• Source URL mentions Target URL

Page 12: Foundational Specifications

@azaroth42

Fou

nd

atio

nal

Spec

ific

atio

ns

References

• TimBL on LOD: https://www.w3.org/DesignIssues/LinkedData.html

• JSON-LD: https://www.w3.org/TR/json-ld/

• Linked Data Platform: https://www.w3.org/TR/ldp/

• Media Fragments: https://www.w3.org/TR/media-frags/

• Open Annotation: https://www.w3.org/TR/annotation-model/

• Activity Streams: https://www.w3.org/TR/activitystreams-core/

• Webmention: https://www.w3.org/TR/webmention/