Hello, Benjamin – thanks for your response! I was a little concerned when I didn’t hear anything at all, so -- glad to hear something, even if it took a while.
Your plan to make the new annotator “thing” (code? tool?) more minimal (and hopefully thus easier to use with a variety of tools) makes a lot of sense, and I can see that Annotator.js 2.x has a fair bit of baggage that you might not want to carry along. I find it very reassuring that one goal is to make annotation data from Annotator.js is compatible with the new thing (even if that requires transformation or import). That makes me feel much more comfortable with using the existing annotator.js 2.x code and Readux plugins in the short term, which I know will provide the functionality I want, even though annotator.js 2.x feels like sort of a dead end in some ways. For what it’s worth, I’ll likely also be looking into making my new annotation compatible with IIIF Presentation and Annotation, which is currently based on Open Annotation but will be shifting to the new W3C Web Annotation model in the next version (although I understand Open Annotation and Web Annotation are very similar). I’m looking forward to hearing more about the goals and the way forward for the new annotator project, and once it gets a bit further along I expect I will have some use cases and test data to work with for trying it out and thinking about migrations. :-) Thanks, Rebecca
