- From: Robert Sanderson <azaroth42@gmail.com>
- Date: Thu, 21 May 2020 12:27:12 -0700
- To: Rainer Simon <aboutgeo@gmail.com>
- Cc: "public-openannotation@w3.org" <public-openannotation@w3.org>
Received on Thursday, 21 May 2020 19:27:37 UTC
We discussed similar sorts of things during the working group, but concluded that any user interaction specific data would not be interoperable and left it out. As soon as someone has the annotation data, they can copy it and modify it, and thus flags like this are the domain of the system or environment from which the annotations are served, not the annotations themselves. HTH, Rob On Thu, May 21, 2020 at 12:24 PM Rainer Simon <aboutgeo@gmail.com> wrote: > Hi, > > I’m currently working on a new edition of my image annotation client > Annotorious [1], [2] and ran into the following use case. I wonder if > there’s a recommendation on how to deal with this from the spec perspective: > > Implementers want to be able to flag individual annotations as either > ‘editable’ or ‘not editable’. Not editable would simply mean that users > would not be able to change, add or remove annotation bodies (tags, > comments, etc.) and the UI would render a read-only presentation > accordingly.. > > Is there a way to represent such a boolean metadata flag in a > spec-compliant way? > > Thanks, > Rainer > > [1] http://github.com/recogito/annotorious > [2] http://github.com/recogito/annotorious-openseadragon > -- > --- > Sent from my Fairphone > -- Rob Sanderson Semantic Architect The Getty Trust Los Angeles, CA 90049
Received on Thursday, 21 May 2020 19:27:37 UTC