Open 2SC1815J opened 6 years ago
Here are a couple of related issues:
https://github.com/IIIF/iiif-stories/issues/75 https://github.com/IIIF/iiif-stories/issues/76
As per https://github.com/IIIF/iiif-stories/issues/75#issuecomment-363874243 I deployed this to all of the wdl.org pages for testing: <link rel="alternate" type="application/ld+json;profile="http://iiif.io/api/presentation/2/context.json"" …>
As far as I know, there are two patterns experimentally adopted. I keep track of the discussion in the discovery group.
The NCSU Libraries adopts the following pattern. (by @jronallo) eg. https://d.lib.ncsu.edu/collections/catalog/0002030
<script type="application/ld+json">
{
"@context": [
"http://www.w3.org/ns/anno.jsonld",
"http://iiif.io/api/presentation/3/context.json"
],
"type": "Annotation",
"motivation": "highlighting",
"target": {
"id": "https://d.lib.ncsu.edu/collections/catalog/0002030/manifest",
"type": "Manifest"
}
}
</script>
ref. https://github.com/IIIF/discovery/issues/20 https://docs.google.com/document/d/1LKhEWWuYF-8KLkKcW_u2GlvX0epohwc7OYOVjICie5M/
The World Digital Library adopts the following pattern. (by @acdha) eg. https://www.wdl.org/en/item/11826/
<link rel="alternate"
type="application/ld+json;profile="http://iiif.io/api/presentation/2/context.json""
href="https://www.wdl.org/en/item/11826/manifest">
<a type="application/ld+json;profile="http://iiif.io/api/presentation/2/context.json""
href="https://www.wdl.org/en/item/11826/manifest">https://www.wdl.org/en/item/11826/manifest</a>
If we can have a consensus that web pages containing links to IIIF manifests will mark up such links in some specified patterns, manifest link detection mechanisms will become more robust and the philosophy of interoperability will be more realized.
For example:
<meta name="iiif-manifest-url" content="http://example.org/iiif/book1/manifest" />
<a href="default_target?manifest=http://example.org/iiif/book1/manifest" data-iiif-manifest-url="http://example.org/iiif/book1/manifest"><img src="logo.png" /></a>