Is FileAnnotations still something we want to deploy on beta cluster? Or is that just blocked on subtasks ?

It's currently stalled awaiting some form of Wikibase on Commons, we decided it would be better to use that for storage rather than re-write the extension after it's released.

That makes sense. Thank you!

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.

In T144302#3240898, @cscott wrote:

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.

Indeed

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.

Stalled because of wait for Wikibase on Commons, which is part of Structured Data on Commons

In T144302#3666472, @Ramsey-WMF wrote:

Stalled because of wait for Wikibase on Commons, which is part of Structured Data on Commons

@Ramsey-WMF: Three years later, is that still the case? If it is, is there a specific task that this one is blocked on?