You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: source/presentation/4.0/index.md
+22-31Lines changed: 22 additions & 31 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -998,7 +998,7 @@ This example is a Manifest with two Timelines, each of which represent a tempora
998
998
999
999
>
1000
1000
**Key Points**
1001
-
*t vs. instant / verbose vs. append to URI???
1001
+
*In the external annotation for the song lyrics, we append `#t=3.5,6.8`to the target URI to define the temporal extent in the target timeline that corresponds to the song lyric.
1002
1002
{: .note}
1003
1003
1004
1004
!!! warning TODO: The above should be a green class rgb(244,252,239) to distinguish from properties
@@ -1102,11 +1102,11 @@ This example is a Manifest with one Canvas that represents the temporal extent o
@@ -2640,46 +2640,37 @@ Responses _SHOULD_ be compressed by the server as there are significant performa
2640
2640
2641
2641
# Accessibility
2642
2642
2643
-
Some IIIF resources have associated resources, such as closed-caption files for video, audio descriptions for images, or tactile graphics for visual materials, that improve access to the content for a wider range of users. These linked resources play a specific accessibility-related role relative to the resource they describe or supplement. [add fwd ref above in subtitles use case]
2643
+
Some IIIF resources have associated resources, such as closed-caption files for video, audio descriptions for images, or tactile graphics for visual materials, that improve access to the content for a wider range of users. These linked resources play a specific accessibility-related role relative to the resource they describe or supplement. See [A/V Use Case 5: Movie with subtitles](link to section) above.
2644
2644
2645
2645
IIIF uses the `provides` property on supplementing annotations to define the specific accessibility functionality that a linked resource enables for its target, describing why and how a client might use it rather than what the resource is by type or format. For example, a text file linked from a video might provide closedCaptions, or an audio file associated with a Canvas might provide an audioDescription.
2646
2646
2647
-
The value of provides _MUST_ be an array of strings. Each string _MUST_ be taken from the IIIF Provides registry (or the table of defined values in the model doc?).
2647
+
The value of provides _MUST_ be an array of strings. Each string _MUST_ be taken from the [IIIF Registry of Accessibility Values][schema-accessibility].
2648
2648
2649
2649
Annotations MAY include the provides property only when the annotation has the supplementing motivation.
2650
2650
Clients SHOULD ignore the provides property on resources with any other motivation.
This document is not subject to [semantic versioning][notes-versioning].
31
+
Changes will be tracked within the document.
32
+
33
+
**Editors:**
34
+
35
+
{% include api/editors.md editors=page.editors %}
36
+
37
+
{% include copyright.md %}
38
+
39
+
## Abstract
40
+
{:.no_toc}
41
+
This document lists a set of allowed values for the Presentation API `provides` property that have been identified as useful for implementations, especially related to accessibility. They may be defined by the IIIF community, or outside of it.
This is one of a number of [IIIF registries][registry]. It lists a set of allowed values for the Presentation API `provides` property that have been identified as useful for implementations, especially related to accessibility. They may be defined by the IIIF community, or outside of it.
49
+
50
+
### 1.1. Disclaimer
51
+
52
+
The inclusion of entries in this document that are outside of the IIIF domain _MUST NOT_ be interpreted as endorsement, support, or approval from the editors, the IIIF community or any individual. This annex is provided as a registry to advertise the existence of these extensions and attempt to ensure some consistency between implementations for common but not universal requirements.
53
+
54
+
### 1.2. Inclusion Process
55
+
56
+
The process for having a new entry added to this registry is [described here][registry-process].
57
+
58
+
## 2. Requirements for Inclusion
59
+
60
+
## 3. Registry
61
+
62
+
This table summarizes the known values available for use with the [Presentation API][prezi-api]`provides` propery, which defines accessibility functionality that a linked resource enables for its target, describing why and how a client might use it rather than what the resource is by type or format. The current approved values are defined by Schema.org's [Accessibility Properties for Discoverability Vocabulary][schema-accessibility] and the IIIF Community.
63
+
64
+
| Value | Description | Source |
65
+
| ------------------------------ ||
66
+
|`closedCaptions`| ... | Schema.org |
67
+
|`alternativeText`| ... | Schema.org |
68
+
|`audioDescription`| ... | Schema.org |
69
+
|`longDescription`| ... | Schema.org |
70
+
|`signLanguage`| ... | Schema.org |
71
+
|`highContrastAudio`| ... | Schema.org |
72
+
|`highContrastDisplay`| ... | Schema.org |
73
+
|`braille`| ... | Schema.org |
74
+
|`tactileGraphic`| ... | Schema.org |
75
+
|`transcript`| ... | Schema.org |
76
+
|`translation`| ... | IIIF |
77
+
|`subtitles`| ... | IIIF |
78
+
{: .api-table}
79
+
80
+
81
+
## Appendices
82
+
83
+
### A. Acknowledgements
84
+
85
+
Thanks to the members of the [IIIF][iiif-community] for their continuous engagement, innovative ideas and feedback.
0 commit comments