Presentation 4 #2316
Presentation 4 #2316
Conversation
Lights, Audio, UnitValue and associated properties
Temporarily disabling internal link checking
Add interactionMode description to model
| The members of a Collection are typically listed in the `items` property or in a series of Collection Pages. The members _MAY_ include both other Collections and Manifests, in order, to form a tree-structured hierarchy. Collections without any members are allowed but discouraged. For example, a collection that had its last member removed might still be valuable to maintain as an empty collection. | ||
|
|
||
| If there are too many members in the collection to fit within a single document, then the members _MAY_ be listed in Collection Pages. A reference to the first page of members is given in the `first` property, and the last page in the `last` property. In this case, the Collection _MUST NOT_ use the `items` property. Collections with pages _MUST_ have at least two pages, otherwise the members should be included in `items` on the Collection. Collection Pages _MUST NOT_ be embedded within the Collection for the same reason. | ||
|
|
There was a problem hiding this comment.
MUST have at least two pages, otherwise the members should be included
Is this to avoid having first and last pointing to the same resource?
I wonder if this is a SHOULD; for dynamically-generated collections, you could be flip-flopping between items having two pages and a list of items. E.g.,
| {: #position} | ||
|
|
||
| It is important to be able to position the (textual) body of an annotation within the Container's space that the annotation also targets. For example, a description of part of an image in a Canvas should be positioned such that it does not obscure the image region itself and labels to be displayed as part of a Scene should not be rendered such that the text is hidden by the three dimensional geometry of the model. If this property is not supplied, then the client should do its best to ensure the content is visible to the user. | ||
|
|
There was a problem hiding this comment.
Needs something to not give the impression that you have to "paint" renderings of textual bodies into the Container; if position not supplied the client will almost certainly render the body outside of a Canvas (e.g., in a side panel) and may even do similar for Scenes too.
| { "provides": [ "closedCaption" ] } | ||
| ``` | ||
|
|
||
| !!! warning "This breaks the graph as the file doesn't provide X in all contexts" |
There was a problem hiding this comment.
True, but... a machine-readable subtitles file, or a human-readable transcript file will very rarely be usable in any other context; it is a transcript of a particular thing, or is a set of subtitles for a particular thing, even when not linked to that thing; it still provides the function even when separated from the thing it is providing the function for.
(waves hands...)
There was a problem hiding this comment.
It's either this, or that same list become values for motivation (with some alterations)
"motivation": [ "providingSubtitles" ]
(sorry)
Rationalise ### headings in P4 index
Previews:
spec: https://preview.iiif.io/api/prezi-4/presentation/4.0/
model: https://preview.iiif.io/api/prezi-4/presentation/4.0/model/
properties: https://preview.iiif.io/api/prezi-4/presentation/4.0/properties/