Skip to content

Commit 63fa3d1

Browse files
author
Rob Sanderson
committed
allow position on SpecificResource
1 parent c1f261c commit 63fa3d1

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

source/presentation/4.0/model.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1972,14 +1972,14 @@ The value of `placeholderContainer` _MUST_ be a JSON object with the `id` and `t
19721972
### position
19731973
{: #position}
19741974

1975-
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.
1975+
It is important to be able to position the 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. The body resource _MUST_ be either a `TextualBody` or a `SpecificResource`.
19761976

19771977
The value of this property _MUST_ be a JSON object conforming to the `SpecificResource` pattern of the Web Annotation Model. The Specific Resource _MUST_ have a `source` property that refers to a Container, and a `selector` that describes a point or region within the Container.
19781978

1979-
> TODO: Should this be allowed on SpecificResource used as `body` of an Annotation?
1980-
1981-
* A TextualBody _MAY_ have the `position` property.<br/>
1982-
Clients _SHOULD_ process the `position` property on TextualBody instances.
1979+
* A Textual Body _MAY_ have the `position` property.<br/>
1980+
Clients _SHOULD_ process the `position` property on Textual Body instances.
1981+
* A Specific Resource _MAY_ have the `position` property.<br/>
1982+
Clients _SHOULD_ process the `position` property on Specific Resource instances.
19831983
* Other classes _MUST NOT_ have the `position` property.<br/>
19841984
Clients _MUST_ ignore the `position` property on all other classes.
19851985

0 commit comments

Comments
 (0)