Add scope as activating annotation shortcut to model#2446
Add scope as activating annotation shortcut to model#2446JulieWinchester wants to merge 3 commits intoprezi-4from
Conversation
source/presentation/4.0/model.md
Outdated
| The scope of a Specific Resource is the context in which it should be interpreted, viewed, or used. For the purposes of IIIF, it is a pointer to one or more resources that are intended to be used by the client for the user to view or interact with the resource. In a Scene, this would typically be an instance of a Camera that should be activated and selected to set up the correct viewpoint. This specification does not establish specific expectations for references to other classes. | ||
| The scope of an Annotation or Specific Resource is the context in which it should be interpreted, viewed, or used. For the purposes of IIIF, it is a pointer to one or more resources that are intended to be used by the client for the user to view or interact with the resource. | ||
|
|
||
| Clients _MUST_ process `scope` as a short-hand expression of an Annotation with `motivation` "activating" with `action` "show," "enable," and "select," where the `source` of the activating Annotation `body` is the Resource referenced by `scope` and the `target` is the Annotation or Specific Resource for which `scope` is specified. In a Scene, `scope` would typically be applied to a Content Resource or commenting Annotation and would reference a Camera that should be activated and selected to set the correct viewpoint in response to user interaction with that resource. This specification does not establish specific expectations for references to other classes. |
There was a problem hiding this comment.
revised wording: with action values: show, enable, and select, ...
source/presentation/4.0/model.md
Outdated
| The scope of a Specific Resource is the context in which it should be interpreted, viewed, or used. For the purposes of IIIF, it is a pointer to one or more resources that are intended to be used by the client for the user to view or interact with the resource. In a Scene, this would typically be an instance of a Camera that should be activated and selected to set up the correct viewpoint. This specification does not establish specific expectations for references to other classes. | ||
| The scope of an Annotation or Specific Resource is the context in which it should be interpreted, viewed, or used. For the purposes of IIIF, it is a pointer to one or more resources that are intended to be used by the client for the user to view or interact with the resource. | ||
|
|
||
| Clients _MUST_ process `scope` as a short-hand expression of an Annotation with `motivation` "activating" with `action` "show," "enable," and "select," where the `source` of the activating Annotation `body` is the Resource referenced by `scope` and the `target` is the Annotation or Specific Resource for which `scope` is specified. In a Scene, `scope` would typically be applied to a Content Resource or commenting Annotation and would reference a Camera that should be activated and selected to set the correct viewpoint in response to user interaction with that resource. This specification does not establish specific expectations for references to other classes. |
There was a problem hiding this comment.
Would "Annotation or Specific Resource on which the scope is specified" be clearer?
There was a problem hiding this comment.
could we simplify this a bit? - Clients MUST process scope as shorthand for an Annotation where the motivation is "activating"; the action is "show", "enable", and "select"; the body is the resource referenced by scope; and the target is the Annotation or Specific Resource for which scope is specified.
Also, it might be easier for readers if we move the Scene example above the MUST statement.
|
Ok, I've updated the paragraph in response to the comments, it now reads:
Re: the third "where" statement about |
Should this part "This specification does not establish specific expectations for references to other classes." go at the end, maybe after a line break? |
|
I agree with @kirschbombe it would be good to retain that caveat. |
|
@kirschbombe and @mikeapp : done, moved the caveat to its own paragraph. |
5 participants
No description provided.