From b4d6a7796cd4ef3622556fb23e3f413c87abfe38 Mon Sep 17 00:00:00 2001 From: Trip Kirkpatrick Date: Fri, 25 Oct 2024 11:58:00 -0400 Subject: [PATCH] =?UTF-8?q?Took=20a=20first=20pass=20at=20the=20text=20?= =?UTF-8?q?=F0=9F=93=9D?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- recipe/0229-behavior-ranges/index.md | 40 ++++++++++++++-------------- 1 file changed, 20 insertions(+), 20 deletions(-) diff --git a/recipe/0229-behavior-ranges/index.md b/recipe/0229-behavior-ranges/index.md index 09d0e6fc9..080bc1db0 100644 --- a/recipe/0229-behavior-ranges/index.md +++ b/recipe/0229-behavior-ranges/index.md @@ -1,47 +1,47 @@ --- -title: Name of Recipe -id: -1 +title: Two Uses of Behavior with Ranges +id: 229 layout: recipe -tags: [tbc] +tags: structure summary: "tbc" viewers: + - Annona + - Theseus + - Aviary + - Ramp topic: - - basic + - structure --- ## Use Case -Describe the use case that the pattern is intended to solve. -Why is this pattern important? +In watching a single-file IIIF video resource you will display in a client, visitors could benefit from the ability to navigation within it visually, a bit like having thumbnail scrubbing. You're not able to segment the video, and you prefer visual navigation to a textual table of contents. ## Implementation Notes -What do you need to know to use this pattern? -How do you implement the pattern? +The cookbook discusses elsewhere ways to use the `behavior` property for determining paging in a book (9, 11), viewing direction for a visual resource (10), visibility of `tagging` Annotations (21), tables of contents (24, 64, 65), collection structure (30), and how to indicate an alternate view of book contents such as for a foldout (35). + +This recipe shows two ways that `behavior` can act in a Range to tell a client how navigation should work. (There isn't going to be a discussion of Ranges per se here; for that, you should read [the spec][prezi3-range].) + +The first way is to use `behavior` with a value of `no-nav` to tell a client explicitly to not include a portion of the resource in navigation, by adding -## Restrictions -When is this pattern is usable / not usable? Is it deprecated? If it uses multiple specifications, which versions are needed, etc.? -Delete this section if it is not needed. -If you don't know what the restrictions might be initially, just leave the following line: -**Unknown - Help Needed** +## Restrictions + +None known. ## Example -Describe the solution in prose and provide an example. -The example json document must be an external document, and imported with the following: +The first nine seconds of the video are marked, in the first subsidiary Range, with `no-nav` because they contain no meaningful video and audio. (In an authentic environment, "meaningful" is up for discussion.) Subsequent peer Ranges divide the video into 10 segments, each assigned a `thumbnail` property and a thumbnail image. While in an authentic environment these might be created from moments that are structurally, semantically, pedagogically, or otherwise significant, here they are merely an equal amount of running time except for the final one. -{% include manifest_links.html viewers="UV, Mirador, Tify, Curation" manifest="manifest.json" %} +{% include manifest_links.html manifest="manifest.json" %} -{% include jsonviewer.html src="manifest.json" %} +{% include jsonviewer.html src="manifest.json" config='data-line="10-13"'%} The direct link to the fixture is a useful convenience. ## Related Recipes -Provide a bulleted list of related recipes and why they are relevant. - -{% include acronyms.md %} {% include links.md %}