Recipe #309 annotation collections

[robcast]

PR for #309

[glenrobson]

Add partOf in the manifest.
Link to the annotations rather than embed them on the page.
Remove Europeana provider
Move annotation collection example above the manifest as its so short

[glenrobson]

Comments from cookbook editors:

• use case: add comma after “algorithm”

implementation notes:

• “The AnnotationCollection is a separate document that references a chain of one or more separate AnnotationPages containing the Annotations” - could potentially be ambiguos to a reader whether the annotationcollections or the annotionpages contain the annotation pages?
• for consistency, should refer to as “Annotation Collections” (not “the” in front) or “an AnnotationCollection”, but not “AnnotationCollections” or “The AnnotationCollections”. Same with AnnotationPage
  should to SHOULD?
• that Annotations that should be shown on a Canvas… > that Annotations intended to be shown on a Canvas …

Comments from Glen:

• Could you have a look at the title as currently it is IIIF specific. Maybe something like "Grouping annotations into collections"
• Could you move the links to the two annotation pages above the manifest JSON and below the AnnotationCollection.
• Add JSON-LD link to the AnnotationCollection
• Highlight the AnnotationCollection in the manifest
• Can you include the label in the embedded annotation collection e.g:

"annotations": [
        {
          "id": "https://preview.iiif.io/cookbook/309-annotation-collections/recipe/0309-annotation-collection/anno_p2.json",
          "type": "AnnotationPage",
          "partOf": [
            {
              "id": "https://preview.iiif.io/cookbook/309-annotation-collections/recipe/0309-annotation-collection/anno_coll.json",
              "type": "AnnotationCollection",
              "label": {
                   "en": [ "Newspaper layout markup"   ]
              },
              "total": 8
            }
          ],
          "prev": "https://preview.iiif.io/cookbook/309-annotation-collections/recipe/0309-annotation-collection/anno_p1.json"
        }
      ]

As I think this will save a round trip for the client.

[cubap]

The title seems more like a tutorial than a recipe. If I were looking for this, I would be searching for terms from the use case

[cubap]

Perhaps lead with one of the examples as the case and then the technical terms followed by the analogous use case examples.

[cubap]

This is a little odd where it is expressing guidance for viewer designers. The language of a recipe (I think) should be to the Manifest host, explaining how to express presentation preferences to the viewers. The advice is solid, however.

[cubap]

This is a lot to take in. I wouldn't delay posting it, but a diagram may be helpful here, in the flavor of those provided in the APIs.

[glenrobson]

From the cookbook:

From navPlace x NavDate:
config='data-line="39-63,73-97,107-131,141-165,175-200"'

[glenrobson]

Comments from Patrick and I:

• Use case is clear

As there are lots of links between the Manifest, AnnotationPage and AnntationCollection it might be helpful to add a Diagram similar to the one on the PresentationAPI to show how the different files link together. Maybe a cut down version of: https://iiif.io/api/assets/images/data-model.png

Remove Annotation with a Non-Rectangular Polygon annotating an irregular shape on a Canvas as related.

Otherwise we were happy for it to go through to the TRC.

@robcast for info the other cookbook editors may comment on this pull request async as it proved difficult to find a time where we could all meet.