Context40

source/_includes/links.md

@@ -318,12 +318,15 @@
 [prezi40]: {{ site.api_url | absolute_url }}/presentation/4.0/
 [prezi40-terminology]: {{ site.api_url | absolute_url }}/presentation/4.0/model/#terminology
 
+[prezi40-model]: {{ site.api_url | absolute_url }}/presentation/4.0/model/
+
+[prezi40-ldce]: {{ site.api_url | absolute_url }}/presentation/4.{{ site.data.apis.presentation.latest.minor }}/#json-ld-and-extensions "Linked Data Context and Extensions"
+
+[prezi40-context-collisions]: {{ site.api_url | absolute_url }}/presentation/4.{{ site.data.apis.presentation.latest.minor }}/#term-collisions-between-contexts
+
 <!-- Link definitions for Presentation API 4.0 model references -->
 <!-- Generated by scripts/link_code_references.py -->
 
-[prezi40-ldce]: {{ site.api_url | absolute_url }}/presentation/4.{{ site.data.apis.presentation.latest.minor }}/model#json-ld-and-extensions "Linked Data Context and Extensions"
-[prezi40-context-collisions]: {{ site.api_url | absolute_url }}/presentation/4.{{ site.data.apis.presentation.latest.minor }}/model#term-collisions-between-contexts
-
 [prezi-40-model-Agent]: {{ site.api_url | absolute_url }}/presentation/4.0/model/#Agent
 [prezi-40-model-AmbientAudio]: {{ site.api_url | absolute_url }}/presentation/4.0/model/#AmbientAudio
 [prezi-40-model-AmbientLight]: {{ site.api_url | absolute_url }}/presentation/4.0/model/#AmbientLight

source/index.md

@@ -26,7 +26,7 @@ api_current_table:
 
 | API                  | Draft Version (Status) |
 | -------------------- | ---------------------- |
-| Presentation API | [4.0.0][prezi40] (Release candidate) |
+| Presentation API | [4.0.0 Base][prezi40] and [4.0.0 Model][prezi40-model] (Release candidate) |
 {: .api-table}
 
 ### Feedback requested

source/presentation/4.0/index.md

@@ -141,7 +141,7 @@ The purpose of the IIIF Presentation API specification is to provide a [model](m
 
 The IIIF Presentation API is concerned with enabling user experiences---providing enough information to present objects in compatible software, and leaving the meaning of the objects to external descriptive metadata standards.
 
-This document acts as an introduction to the specification through a set of typical (but non-exhaustive) use cases. The [Presentation API 4.0 Data Model](model) document provides the formal specification of the model and terms used in this introduction.
+This document acts as an introduction to the specification through a set of typical (but non-exhaustive) use cases. **The [Presentation API 4.0 Data Model](model) document provides the formal specification of the model and terms used in this introduction.**
 
 ## IIIF Use cases
 
@@ -1109,6 +1109,7 @@ The value of [`provides`][prezi-40-model-provides] is an array of strings, taken
 ]
 ```
 
+>
 **Key Points**
 * The `provides` property is placed on the annotation and not on the target of the annotation.
 * The property is primarily used to define accessibility features, but can be used to define other types of functionality, such as `transcript`.

source/presentation/4.0/model.md

@@ -2644,7 +2644,12 @@ The value _MUST_ be a JSON Object with the `id` and `type` properties. The value
 
 {% include api/code_header.html %}
 ``` json-doc
-{ "source": "https://example.org/museum/images/1" }
+{ 
+  "source": {
+    "@id": "https://example.org/museum/images/1",
+    "@type": "Image"
+  }
+}
 ```
 
 
@@ -2959,7 +2964,7 @@ The value of this property _MUST_ be a non-negative integer.
 ### transform
 {: #transform}
 
-An ordered list of 3D transform operations (translation, rotation, and scale) to be performed on a resource prior to painting that resource into a Scene. Transforms _MUST_ be applied to the resource in the order given. The resulting state of the resource after applying a transform _MUST_ be the input state for the subsequent transform in the ordered list. Therefore, transforms are not independent, and different orders of the same set of transforms can produce different results. The list of transforms _MAY_ include multiple transforms of the same type, e.g., multiple rotation operations.
+An ordered list of transformation operations (Transform instances) to be performed on a resource prior to painting that resource into a Container. The Transforms _MUST_ be applied to the resource in the order given. The resulting state of the resource after applying a transform _MUST_ be the input state for the subsequent transform in the ordered list. Therefore, transforms are not independent, and different orders of the same set of transforms can produce different results. The list of transforms _MAY_ include multiple transforms of the same type, e.g., multiple rotation operations.
 
 The value of this property _MUST_ be array of JSON objects, each of which _MUST_ be a Transform.