A Canvas has a region of interest that contains the place name “Paris”. You would like to associate this instance of “Paris” with the geocoordinates for a central point in Paris, France that clients can use for representing the targeted fragment in world map based user interfaces, such as Leaflet or Google Maps. This could mean simply showing a non-interactive point on a web map, but often more data from the resource is displayed in connection with the point as a result of available functionality within the MapUI, such as a pop-up that appears showing metadata from the resource upon clicking the point.
A multitude of real world resources benefit from geographic data, many of which are already represented in IIIF digital collections. New and old maps, travel journals, newspapers, manuscripts, poems and diaries are just a subset of cultural heritage artifacts that have geographic characteristics. These traits bring human context to the material and offer a recognizable, comfortable setting for discovering connections between disparate resources.
The third party GeoJSON-LD context is included in addition to the IIIF Presentation API 3.0 context. The GeoJSON-LD context supplies the vocabulary terms for the Annotation bodies since the IIIF Presentation API 3.0 context does not describe those terms. When the
@context property is used as an array with multiple contexts, the IIIF Presentation API 3.0 context must be the last item in the array.
properties object is generic and can be nearly anything. It is used to pass metadata along with the geocoordinates. This has implications on clients and parsers that must discern what data to use. For example, if the targeted resource has a
label property and the
properties object has a
label property, the consuming interface must make a choice on which to prioritize for presentation purposes. In the image from the Use Case section, the “Label” uses the GeoJSON
label property(lines 80-83) instead of the
label property from the Annotation or Canvas.
geometry can be more than just a
Applications that strictly follow Linked Data practices will find that nested GeoJSON coordinate arrays are incompatible with the processing model of JSON-LD 1.0. The JSON-LD 1.1 processing model does not have this restriction. Be aware if you plan to serialize JSON-LD into other semantic data formats or markup languages such as RDF.
The Manifest has one Canvas with one Image, and the Canvas has the same size dimensions as the Image. The Canvas has one Annotation Page with one Annotation targeting the region of interest where “Paris” appears using the #xywh Fragment Selector syntax. The Annotation
body is GeoJSON-LD, which is supported by a number of open source mapping systems. A client can parse the Annotation from the Canvas and pass the Annotation
body into MapUI systems resulting in rendered geometric shapes on a world map. Often, data from the resource such as an image URL, label or description is connected with those shapes via
properties in GeoJSON. Since the image used is a IIIF Fixture following IIIF Image API 3.0, you can see the targeted fragment by supplying the values used in the #xywh selector to the image URL.
- [Represent Canvas Fragment as Multiple Geographic Points on a Web Map][TBD]
- [Represent Manifest as a Geographic Point on a Web Map][TBD]
- [Represent Manifest as a Geographic Polygon on a Web Map][TBD]
- [Fragment Selectors]
- [Tagging Annotation]