From f9e3bfbb107d91b2e69e4363ba389570d45f009f Mon Sep 17 00:00:00 2001 From: Glen Robson Date: Thu, 26 Mar 2026 00:42:01 +0000 Subject: [PATCH 1/2] Adding example anno-page and anno-collection --- source/presentation/4.0/index.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/source/presentation/4.0/index.md b/source/presentation/4.0/index.md index f48720f3f..b87ae6159 100644 --- a/source/presentation/4.0/index.md +++ b/source/presentation/4.0/index.md @@ -313,12 +313,15 @@ Annotation Pages are used to group Annotations. In cases where many annotations Each Annotation Page can be embedded or externally referenced. Clients should process the Annotation Pages and their items in the order given in the Container. Publishers may choose to expedite the processing of embedded Annotation Pages by ordering them before external pages, which will need to be dereferenced by the client. Order can be significant, however. Annotations are assigned an ascending [z-index](https://developer.mozilla.org/en-US/docs/Web/CSS/z-index) from the first annotation encountered. Annotations with a higher z-index will render in front of those with a lower z-index when displayed on a Canvas. +{% include code_example.html src="09_anno_page_1.json" %} + ### Annotation Collection Annotation Collections represent groupings of Annotation Pages that should be managed as a single whole, regardless of which Container or resource they target. This allows, for example, all of the Annotations that make up a particular translation of the text of a book to be collected together. A client might then present a user interface that allows all of the Annotations in an Annotation Collection to be displayed or hidden according to the user’s preference. For Annotation Collections with many Annotations, there will be many pages. The Annotation Collection refers to the first and last page, and then the pages refer to the previous and next pages in the ordered list. Each page is part of the Annotation Collection. +{% include code_example.html src="09_anno_collection.json" %} ## Content Resources From 0529a76feda6dd0b7c8b09e5ea6ce0bc0c307753 Mon Sep 17 00:00:00 2001 From: Glen Robson Date: Thu, 26 Mar 2026 00:46:21 +0000 Subject: [PATCH 2/2] Adding Annotation example --- source/presentation/4.0/index.md | 52 +------------------------------- 1 file changed, 1 insertion(+), 51 deletions(-) diff --git a/source/presentation/4.0/index.md b/source/presentation/4.0/index.md index b87ae6159..ce140baf0 100644 --- a/source/presentation/4.0/index.md +++ b/source/presentation/4.0/index.md @@ -255,57 +255,7 @@ Annotations are grouped within the [`items`][prezi-40-model-items] property of a The required properties of Annotations, as used in IIIF, are [`id`][prezi-40-model-id], [`type`][prezi-40-model-type], [`target`][prezi-40-model-target] and [`motivation`][prezi-40-model-motivation]. Most Annotations also have the [`body`][prezi-40-model-body]. See the [Annotation Documentation](model/#Annotation) for more detail. - -> TODO: JSON examples for Anno, Anno Page and Anno Coll'n ? -{: .warning} - - - - - +{% include code_example.html src="09_anno_page_1.json" from=14 to=28 %} ### Annotation Page