Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Web Annotation Ontology in IIIF Manifest @context #5833

Open
3 tasks
joncameron opened this issue May 16, 2024 · 2 comments
Open
3 tasks

Web Annotation Ontology in IIIF Manifest @context #5833

joncameron opened this issue May 16, 2024 · 2 comments

Comments

@joncameron
Copy link
Contributor

joncameron commented May 16, 2024

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

  • Determine if http://www.w3.org/ns/anno.jsonld is required
  • Determine why the validator is flagging this
  • Remove http://www.w3.org/ns/anno.jsonld if desired
@joncameron
Copy link
Contributor Author

joncameron commented May 21, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants