The IIIF specifications are implemented using JSON-LD, a JSON serialization pattern for RDF. JSON-LD has the advantage of being, at the same time, both developer readable and tractable, as well as being Linked Data. This allows for easy extensions without fear of term collisions as everything is mapped to a globally unique URI, and to be able to link into other systems as part of the global information graph. The costs of doing this are minimal, mostly the definition and reference to a context document in each JSON document.
There are, however, some side effects of working with JSON-LD, that implementers should be aware of. Some of the issues are due to the RDF model, and others are specific to JSON-LD.
As of 2018, new specifications and updates to existing specifications will adopt JSON-LD 1.1 rather than JSON-LD 1.0. This brings many benefits including the ability to more precisely scope the effect of context definitions, and to have additional control over the exact JSON serialization.
The IIIF process does not consider the mappings from the JSON to the selected RDF ontology terms to be governed by semantic versioning. They are provided as a convenience for Linked Data implementers, rather than being a requirement for all adopters of IIIF. The JSON structure and the names of the keys are governed by semantic versioning, as changing them would break compatibility with the typical JSON based client.
This decision may change in the future, if there are significant Linked Data based clients built around IIIF. Any such development should be announced on iiif-discuss so that the community becomes aware of it.
The JSON-LD frames described below are also not considered as governed by semantic versioning, and are provided as a convenience for implementers.
Formats and Languages
It is possible to associate a language with a literal in JSON-LD using an object with two keys,
@value, described in the Presentation API. It is also possible to describe the format of a literal using
@type. However, due to restrictions in RDF 1.1, it is not possible to use both of these features together to have a literal with both format and language declared.
During the design of the Presentation API version 2.0, it was determined that the correct solution was to be explicit about language as it cannot be determined heuristicly, and provide requirements to make the detection of HTML as easy as possible. In the future, if RDF provides a method to have both format and language associated with the same literal, these restrictions will be lifted. Other options were evaluated, including having a resource with
format keys which was determined to be too intrusive compared to what regular JSON would look like, and using HTML with an
xml:lang attribute and the
rdf:HTML datatype, however this makes the choice of language much more complex as the values need to be parsed with an HTML parser, rather than using the JSON structure. As internationalization of the values is a primary use case, the current method was the solution chosen.
In version 3.0 of the Presentation API, a pattern called “language maps” has been adopted. This allows the code for the language to be used as a key in a JSON object, with a list of strings in that language as the value for that key. This reduces the complexity of the language structure, and further cements the decision to promote language over format.
Term Expansion/Compaction Issues
Unintended Expansion of URI Schemes
The JSON-LD term expansion algorithm, as implemented by most JSON-LD libraries, cannot distinguish between a term with a namespace defined in the context and a real URI scheme. For example, if a context document defined a mapping from
http://www.tracker.com/, most JSON-LD libraries will expand
http://www.tracker.com///iiif.io/ by simply replacing
http: in the value. This issue only occurs if the URI scheme name is defined in the context.
All IIIF APIs are subject to this issue for
service entries, which conflicts with the Service URI scheme used mostly by printers. The Presentation and Search APIs are also subject to this issue for
resource entries in Annotations, which conflict with the provisional Resource URI scheme. The recommendation for implementers is to not use URIs with these schemes when describing IIIF resources.
This python code will check for conflicts in a context document.
Greedy Compaction of Terms
Term compaction in JSON-LD is the process of taking a full URI and a context, and trying to create the appropriate compact form for the serialization. For example, if the URI is
http://example.com/ns/term, and the context has a mapping from
http://example.com/ns/, then the URI will be compacted to
eg:term. Most JSON-LD libraries use an algorithm that tries to create the shortest term in the JSON serialization, however this has unintended side effects when there are terms which happen to be truncated forms of other terms, as the algorithm cannot distinguish between mappings added for the purposes of creating namespaces and those added for defining the keys of the JSON format.
The IIIF Image API was subject to this issue for the size features until version 2.1 was released. In particular, there was a definition of
iiif:size, and the size related features were named according to the pattern:
iiif:sizeByX, and thus
sizes:ByX was the shortest legal, if unintended, compaction. For version 2.1,
iiif:size was renamed to
iiif:hasSize to avoid this issue. See also the note on Semantic Versioning and JSON-LD below.
JSON-LD Frames are a method of determining the layout of a JSON-LD serialization, in particular which resource should be at the root of the JSON structure and whether information about the resource should be embedded in a particular location or not. This has practical applications for IIIF specifications, and especially for the IIIF Presentation API such as ensuring that the Manifest resource is at the root of the JSON file and that Canvases are serialized as part of the Sequence rather than within a Range, among others.
More information about JSON-LD frames can be found at the JSON-LD site.
Image API Frame
A minimal frame for the IIIF Image API information response.
Presentation API Frames
Frames for the main resources defined by the IIIF Presentation API.
- Presentation 2.x Frames:
The following code uses the Python PyLD implementation of JSON-LD to read in example manifest data, parse it and then re-serialize using the manifest frame.
from pyld.jsonld import compact, frame import urllib, json, pprint manifest = json.load(urllib.urlopen("http://iiif.io/api/presentation/3.0/example/fixtures/1/manifest.json")) pprint.pprint( compact( frame(manifest, "http://iiif.io/api/presentation/3/manifest_frame.json"), "http://iiif.io/api/presentation/3/context.json") )