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

Are annotations designed to be co-authored or just exported? #10

Open
lrosenthol opened this issue Sep 19, 2024 · 2 comments
Open

Are annotations designed to be co-authored or just exported? #10

lrosenthol opened this issue Sep 19, 2024 · 2 comments

Comments

@lrosenthol
Copy link

When designing an annotation model around the Web Annots Data Model, one thing that needs to be considered is whether there is an expectation that more than one user can author a given annotation - or possibly "comment on a comment", or even just "like it".

This current design does not provide for those co-authoring/shared reviewing scenarios. If that is what is intended, please feel free to close this issue. however, if you do wish to support that use case, then there are bunch of changes required.

@llemeurfr
Copy link
Contributor

I don't think that the W3C Web Annotation Data Model considers "annotations about annotations".
With RDF everything is possible, but the target of an annotation is a source (web resource) plus selector, and the selector is a fragment of the source. I see no place for creating linked annotations here.

I agree that the use case is interesting.
I must warn that implementing this use case in reading systems would be highly complex (UX/UI + technical implementation).

@lrosenthol
Copy link
Author

The Web Annot model fully supports commenting on comments. IIRC there is even an example of how to do so. It works by having the target of the annotation be another annotation (instead of a piece of text or other part of an asset).

But yes, doing so would add requirements for RS, no question.

This may not be something you need for v1 of your proposal, but I would think it should at least be tracked for the future.

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