Merge branch 'master' into clover-supports-46

recipe/0002-mvm-audio/index.md

@@ -23,7 +23,7 @@ The simplest viable manifest for audio content. This pattern presents a single a
 
 ## Implementation Notes
 
-The implementation is identical to the [image example][0001], except that the content is audio and the canvas has the `duration` property instead of the `height` and `width` properties.
+The implementation is identical to the [image example][0001], except that the content is audio and the canvas has the `duration` property instead of the `height` and `width` properties. The value of the `duration` property [must be a floating point number](https://iiif.io/api/presentation/3.0/#duration). If the duration value you have is an integer, it therefore needs to be written with at least a decimal point and a trailing zero: `1985.0` rather than `1985`.
 
 ## Example
 

recipe/0003-mvm-video/index.md

@@ -23,7 +23,7 @@ The simplest viable manifest for video content. This pattern presents a single v
 
 ## Implementation Notes
 
-The implementation is identical to the [image example][0001], except that the content is video and the canvas has a duration as well as a height and width.
+The implementation is identical to the [image example][0001], except that the content is video and the canvas has the `duration` property instead of the `height` and `width` properties. The value of the `duration` property [must be a floating point number](https://iiif.io/api/presentation/3.0/#duration). If the duration value you have is an integer, it therefore needs to be written with at least a decimal point and a trailing zero: `1985.0` rather than `1985`.
 
 ## Example
 

recipe/0003-mvm-video/manifest.json

@@ -8,7 +8,7 @@
         "id": "{{ id.path }}/canvas",
         "type": "Canvas",
         "height": 360,
-        "width": 640,
+        "width": 480,
         "duration": 572.034,
         "items": [
           {

recipe/0007-string-formats/index.md

@@ -27,7 +27,7 @@ To alert a consuming application that your content is HTML, the first character
 
 ## Restrictions
 
-For security reasons, clients allow only `a`, `b`, `br`, `i`, `img`, `p`, `small`, `span`, `sub`, and `sup` tags, and may remove any or all of those. For more details of permitted and prohibited markup, see [the specification](https://iiif.io/api/presentation/3.0/#45-html-markup-in-property-values).
+For security reasons, clients are expected to allow only `a`, `b`, `br`, `i`, `img`, `p`, `small`, `span`, `sub`, and `sup` tags, and may remove any or all of those. For more details of permitted and prohibited markup, see [the specification](https://iiif.io/api/presentation/3.0/#45-html-markup-in-property-values).
 
 ## Example
 

recipe/0017-transcription-av/index.md

@@ -5,8 +5,6 @@ layout: recipe
 tags: [audio, video, presentation, transcript]
 summary: "Transcripts as alternative representation of A/V content"
 viewers:
- - UV
- - Mirador
  - Ramp
 topic: AV
 property: rendering
@@ -35,13 +33,9 @@ None.
 
 In this example, the Manifest is using a single A/V file; therefore, it is equivalent to link the transcript at the Manifest level or at the Canvas level and we do it at the Canvas level to complement the example in [Providing Alternative Representations][0046].
 
-In Mirador, a given transcript is made available within the sidebar menu, which can be toggled open by using the 'Sidebar toggle' (hamburger) button on the top left corner of the viewer.
+In Ramp, the transcript file is made available to download on the right of the player controls. Click the filename listed in the menu to download the transcript file.
 
-In Universal Viewer, to access the transcript use the 'Download' link on the bottom left corner of the viewer.
-
-In Ramp, the transcript file is made available to download under the player controls. Click the filename listed in the menu to download the transcript file.
-
-{% include manifest_links.html viewers="UV, Mirador, Ramp" manifest="manifest.json" %}
+{% include manifest_links.html viewers="Ramp" manifest="manifest.json" %}
 {% include jsonviewer.html src="manifest.json" config='data-line="39-50"'%}
 
 # Related recipes

recipe/0053-seeAlso/index.md

@@ -18,7 +18,7 @@ You have a IIIF manifest resource along with additional machine-readable metadat
 
 ## Implementation Notes
 
-This property is used for pointing a viewer to the URI of a non-IIIF resource with information about the IIIF resource to which it is attached. Most frequently, the non-IIIF resource will be structured metadata, and to be most effective, the target resource should be a machine-readable format such as XML, JSON, or RDF. The `type` value for `seeAlso` is usually `dataset`. Manifest creators or editors should look in [the IIIF Registry of Profiles](https://iiif.io/api/registry/profiles/#3-registry) to see if a consistent URI exists for use as the `seeAlso` property's `id` value.
+This property is used for pointing a viewer to the URI of a non-IIIF resource with information about the IIIF resource to which it is attached. Most frequently, the non-IIIF resource will be structured metadata, and to be most effective, the target resource should be a machine-readable format such as XML, JSON, or RDF. The `type` value for `seeAlso` is usually `dataset`. Manifest creators or editors should look in [the IIIF Registry of Profiles](https://iiif.io/api/registry/profiles/#3-registry) to see if a consistent URI exists for use as the `seeAlso` property's `profile` value.
 
 Three other properties may seem similar, so it's worth highlighting the differences. 
 
@@ -41,7 +41,7 @@ None
 
 In this example, a MODS XML file is provided for the program as a whole, and as such the `seeAlso` property attaches to the Manifest. If such data files were available for each view or page separately, each Canvas would be a logical place for the corresponding `seeAlso` instance.
 
-A consistent URI to use for the `id` value for MODS can be found in [the IIIF Registry of Profiles](https://iiif.io/api/registry/profiles/#3-registry).
+A consistent URI to use for the `profile` value for MODS can be found in [the IIIF Registry of Profiles](https://iiif.io/api/registry/profiles/#3-registry).
 
 To see the property in action in Mirador, toggle the sidebar by activating the three-line ("hamburger") menu in the upper left-hand corner of the content window. You should then, in the "Related" area, see the link in the "Related" section under the "See also" subheading.
 

recipe/0234-provider/index.md

@@ -34,7 +34,7 @@ None known.
 
 In this example, we reuse the front page of a kabuki playbill that was contributed to the IIIF Cookbook by UCLA Library Digital Collections. The `id` for them as an Agent is the US Library of Congress authority ID for the UCLA Library, the `homepage` is their actual homepage, the `logo` is also for the library as a whole, and the `seeAlso` is the US Library of Congress MADS/XML. In your use of this property, you might want to and be able to unify the information in the property differently.
 
-Only Mirador implements `provider`, and only partially. The property must be on the Manifest level, Mirador will only display the text from a `label` under `provider`, and the information will only be found in the list of manifests.
+Only Mirador implements `provider`, and only partially. The property must be on the Manifest level, Mirador will only display the text from a `label` and the image from a  `logo` under `provider`, and the information will only be found in the list of manifests.
 
 {% include manifest_links.html viewers="Mirador" manifest="manifest.json" %}