The experience with Annotation during the initial phases of implementing this syntax was positive. We found it prudent to investigate Annotation again using IIIF Presentation API 3.0. Implementation Description Below you will see an empty Manifest geolocated via a geographic polygon. There is an Annotation Page containing a single Annotation with coordinates to central Paris, […]
Category: IIIF
Having found success with IIIF Presentation API 3 Annotation, we look to see if services can support GeoJSON-LD. Implementation Description Below you will see an empty Manifest geolocated via a GeoJSON service. The body of that service is a GeoJSON-LD Point. Example JSON { “@context”:[ “http://geojson.org/geojson-ld/geojson-context.jsonld”, “http://iiif.io/api/presentation/3/context.json” ], “id”:”http://www.example.org/manifest/3″, “type”:”Manifest”, “label”:{ “en”:[ “Example IIIF Presentation […]
Annotation was successful during the first phase of using IIIF Presentation API 3.0 for geolocating an entire Web entity. Another piece is to ensure that we could provide geolocated assertion upon an entity fragment, since situations like inset maps are common and need specific geospatial information that does not apply to the entire entity. Implementation […]
The experience with Annotation during the initial phases of implementing this syntax was positive. We found it prudent to investigate Annotation again using IIIF Presentation API 3.0. Implementation Description Below you will see an empty Manifest geolocated via a geographic polygon. There is an Annotation Page containing a single Annotation with coordinates to central Paris, […]
The shortcomings of the Annotation syntax meant looking for another option. The other option of intertwining syntax is IIIF Presentation API 2.1 services. Initial investigation led to a supported GeoJSON extension, which meant there was already a foundation set for working with GeoJSON under the scope of the API. Implementation Description Below you will see […]
As with any standards committee or best practices group, there is a subgroup tasked with providing examples for the internal community as well as external implementers. For IIIF, this group is the Cookbook group. Examples exist in the public Cookbook that properly format data assertions and combine them with resources in order to enhance those resources. […]
The OCDH has been involved with the International Image Interoperability Framework™ (IIIF) since its beginning. We are adept with Annotation to supply supplementary data to data resources that are owned by others. We have our own public open annotation store and Web API known as RERUM to support this ecosystem of assertions. The scope of IIIF encompasses […]
Categories
Structural REform
The world of annotations is one of unstructured targeting. There is an existing piece of data somewhere in the world and an annotation targets it. At a higher level we work with data objects called Manifest. The manifests we work with follow the construct created by the IIIF frame work (https://iiif.io/api/presentation/2.1/#manifest). An important attribute of […]
Categories
A IIIF Concordance
As IIIF Manifests increasingly contain transcription annotations, the tools that are able to handle these documents must also treat text content as a first-class citizen. In our TPEN software, users regularly generate new annotations with text content that is included in the manifest documents made available for every project. In addition, TPEN allows for the […]
Come one, come all. What is this Rerum of which we Tweet? Rerum is an open and free repository for all sorts of digital things. Digital anchors for real world objects and encoded assertions from real world people are stored without prejudice. It’s a data ecosystem to bring those unique digital solutions to scholarly demands […]