Deploy the FileAnnotations extension to the beta cluster.
|Stalled||MarkTraceur||T144302 Release FileAnnotations on the Beta Cluster|
|Resolved||None||T146118 Use a query to find representative images instead of assuming P18 exists for WD items|
|Resolved||MarkTraceur||T145450 Separate FileAnnotator class from code in fileannotations.js that should run on page load|
|Open||Prtksxna||T145455 FileAnnotator should handle edit API failures (simple way to reproduce: disallow a URL with SpamBlacklist)|
|Open||None||T145458 Editing a file annotation requires very careful mouse movement|
|Resolved||Bawolff||T146174 Security review of FileAnnotations|
Storage in Wikibase? Or T107595: [RFC] Multi-Content Revisions?
I'm at the iannotate conference right now -- is there documentation on the annotation format you are using? (Or anything in particular you need help with?)
Note that the W3C annotation spec includes an API component: https://www.w3.org/TR/annotation-protocol/
It would be great if we could publish our annotations in this standard way.
But, if this takes a while, we should at least start by embedding the annotations in our HTML (which seems easier to implement): https://www.w3.org/TR/annotation-html/ (specifically https://www.w3.org/TR/annotation-html/#mixing-rdfa-with-embedded-rdf-content)
Note that the wikidata folks seem likely to be able to publish annotations as a proper JSON-LD object without too much effort: T44063: [Epic] Provide a plain linked data interface for accessing entities. It may still be easier to embed them in HTML, but we haven't actually had positive experiences with embedded RDFa on the Parsoid side -- mostly that nobody pays attention to it. The tooling for JSON-LD looks a little better.