Michael Dyck:

para 1 says:
"A user wishes to provide internationalization information for a document that they don't conrol, ..."
Change "conrol" to "control".

Missing use case for annotating annotations in a threaded system

From Michael Dyck:

para 1 says: "If the user requests it, then it this enables an export functionality ..."
Change "then it this" to "then this".

Currently 2.1.4 packs in too many requirements, split into two.

From Felix Sasaki:
I have to add just one question to this: in the use case document or a different location, is there a description of actors? I was thinking of e.g.

1. content architect: providing annotations for several (potentially thousands of documents)
2. a content author: using the templates made by content architects and adapting them to her needs
3. a content quality evaluator: in selected pieces of content making exceptions to 1) and 2)

Art Barstow of Nokia commented that there were no use cases that covered resources such as maps. Non traditional publications should also be covered in the use case document, including annotating audio, video, image, and other data. That the comment can also be of any format should be highlighted as well (currently expressed in 2.1.4, though the title is misleading)

From a browser vendor's perspective, it would be good if the document was more clear as to how, for example, <a> elements, custom data, and fragment identifiers are insufficient in achieving each of the use cases. It would also be good if the document could show how applications are hacking around the limitations in browsers today.

Adding the information above would go a long way to adding more credibility towards showing that this is a real problem and limitation in the Web platform.

I would urge you to take a look at http://usecases.responsiveimages.org/, which was used to convince browser vendors that there were serious limitations in the platform with regards to images. Something similar would go a long way with respect to annotations... it will also make it more clear as to whether this needs an actual in-browser solution or if this is just going to be a data format (e.g., something build on top of JSON-LD, XML, or whatever).

Need to have the alert/notification/push system as a use case.

It's annoying to manually rename all of the examples when a new use case is added.
Write a little script to replace {% (gender) %} with a gender name and increment letters