Add Annotation usecase about sharing outside of a file or an app

[gautierchomel]

Existing use cases occur in controlled environments, such as ePubs sold with annotations or annotations shared within the app. This adds a new use case: the annotation file is made available somewhere, and someone downloads it. This would also probably cover sending annotations through email.

Diff

[iherman]

For the export case, there is a major overlap with §5.3 Annotation used in the publishing workflow. From the point of view of this document, only the action of export is relevant, all other parts (like the fact of paying or not for the content) is irrelevant; it does not seem to add new requirements.

§5.3 has an ambiguous formulation for what is, actually, and import:

The EPUB creator associates the annotation set with the EPUB file in an editing tool that supports this specification, goes through the annotations, and corrects the EPUB.

My proposal would be (to avoid overlaps) is to expand §5.3 referring to other possible usage of the main actions, namely exporting/importing the annotations. It is also a good idea to emphasize that the annotations can include metadata, like the creator's name and address (something which is part of this proposal, but is not in the current document).

[iherman]

Actually, I also realized that there are also lots of overlaps with §5.4 (Classroom example.)

[gautierchomel]

Monetising could imply the need for a protection method. But it may also be necessary in a classroom context.