Open joncameron opened 1 month ago
May not pose a problem in real-world uses. Would require a change to iiif_manifest gem, where it's being manually inlined for each manifest.
Could also reach out in IIIF Slack to see if there's any guidance there.
Places where this context is added in iiif_manifest
:
https://github.com/samvera/iiif_manifest/blob/75a3702d58982b37bb9ce327dcd6686273a6ccbb/lib/iiif_manifest/v3/manifest_builder/iiif_service.rb#L82
https://github.com/samvera/iiif_manifest/blob/75a3702d58982b37bb9ce327dcd6686273a6ccbb/lib/iiif_manifest/v3/manifest_builder/iiif_service.rb#L93
Description
Avalon currently writes
http://www.w3.org/ns/anno.jsonld
into the @context of all IIIF manifests. Running the IIIF validator against our manifests, the error "Top level @context is not known" appears. This seems odd because seeming this should be valid in the spec (https://iiif.io/api/presentation/3.0/#46-linked-data-context-and-extensions).https://presentation-validator.iiif.io/validate?version=3.0&url=https://media.dlib.indiana.edu/media_objects/c821gr848/manifest.json
Is the validator wrong? And do we need to include this in the @context? I don't see it in other IIIF examples, and it could be implicit in IIIF Presentation 3. If it's superfluous it could be removed from our manifests.
Example: https://media.dlib.indiana.edu/media_objects/vx021n34x/manifest.json https://presentation-validator.iiif.io/validate?version=3.0&url=https://media.dlib.indiana.edu/media_objects/c821gr848/manifest.json
Done Looks Like
http://www.w3.org/ns/anno.jsonld
is requiredhttp://www.w3.org/ns/anno.jsonld
if desired