From 7398e18bf89d4a2569f23619007e9ed3b272368e Mon Sep 17 00:00:00 2001
From: tomcrane <tom@nanoplanet.com>
Date: Fri, 25 Oct 2024 12:43:45 +0100
Subject: [PATCH] placeholder sections in prezi4 incl. physical dimensions

---
 source/presentation/4.0/index.md | 84 +++++++++++++++++++++++++++++---
 1 file changed, 76 insertions(+), 8 deletions(-)

diff --git a/source/presentation/4.0/index.md b/source/presentation/4.0/index.md
index 38b43e277..247b3f7ba 100644
--- a/source/presentation/4.0/index.md
+++ b/source/presentation/4.0/index.md
@@ -245,6 +245,8 @@ Example Annotation that positions a model at a point within a Scene:
 
 #### URI Fragments
 
+(move up, include xywh)
+
 The point may instead be defined using a short-hand form of a URI Fragment at the end of the `id` of the Scene as the `target` of the Annotation. The name of the fragment parameter is `xyz` and its value is the x, y and z values separated by commas. Each value can be expressed as either an integer or a floating point number.
 
 The annotation above could be expressed as its fragment-based equivalent:
@@ -305,6 +307,10 @@ content state intended to:
  - modify the Container in a particular context (`scope`, storytelling)
  - contribute additional information permanently (rerum **inbox** - move to protocol doc)
 
+### Using Content State
+
+(not in section 6)
+
 ### reset
 
 "diff", "original state" etc
@@ -314,8 +320,17 @@ behavior: sequence
 
 ## Selectors
 
+preamble - cover all the use cases
+
 ### SpecificResource
 
+(This heading should be more descriptive)
+
+fragments/segments/parts of resources
+SvgSelector
+xywh
+
+
 ### PointSelector
 
 
@@ -493,6 +508,8 @@ Painting a Scene into another while excluding import of several types of resourc
 
 ## Advanced Association Features
 
+(This needs to be sprinkled throughout above - especially as SpecificResource must be introduced early for 3D)
+
 ### Nesting
 
 A Canvas can be painted into a Scene as an Annotation, but the 2D nature of Canvases requires special consideration due to important differences between Canvases and Scenes. A Canvas describes a bounded 2D space with finite `height` and `width` measured in pixels with a pixel origin at the top-left corner of the Canvas, while Scenes describe a boundless 3D space with x, y, and z axes of arbitrary coordinate units and a coordinate origin at the center of the space. It is important to note that in many cases the pixel scale used by a Canvas or a 2D image content resource will not be in proportion to the desired 3D coordinate unit scale in a Scene. 
@@ -520,33 +537,77 @@ Example placing top-left at (0, 1, 0); bottom-left at (0, 0, 0); bottom-right at
 ```
 
 
-### Segments
-
 ### Embedded Content
 
+e.g., painting TextualBody on Canvas
+
+
+### Comment Annotations
+
+(move to Annotation section)
+
+
 ### Choice of Alternative Resources
 
+(move to Annotation section)
+
+
 ### Non Rectangular Segments
 
+SvgSelector - move to SpecificResource too ^^
+
+
 ### Style
 
+Move to SpecificResource
+
+
 ### Rotation
 
-### Comment Annotations
 
-### Hotspot Linking
+### Hotspot Linking and Activation
 
-### Activation
+Move to SpecificResource
 
-### Using Content State
 
- - modify the Container in a particular context (`scope`, storytelling)
 
+## Conveying Physical Dimensions
+
+(why is this important!?)
+
+(move the props to vocab doc)
+
+### spatialScale
+
+### temporalScale
+
+
+```
+{
+    "spatialScale": {
+        "factor": 22.0,
+        "units": "m"
+    },
+
+    
+    // this would be rarely used
+    "temporalScale": {
+        "factor": 0.00001
+    }
+
+}
+```
 
+`factor`	Required	A floating point ratio.
+`units`	    Required	A real-world measuring unit. Always seconds for temporalScale. Possible values for spatialScale include: "m", "ft". (is that it?)
 
-### Physical Dimension Service
+For a Canvas, it's the physical "size" of each cartesian integer unit.
+For a Scene, it's the physical size of the unit vector. 
+For a timeline it's the ratio of time in the recording to time in the real world.
 
 
+(define props in the Vocabulary doc)
+
 
 ## HTTP Requests and Responses
 
@@ -559,6 +620,13 @@ Example placing top-left at (0, 1, 0); bottom-left at (0, 0, 0); bottom-right at
 ### Authentication
 
 
+## Accessibility
+
+(new section)
+
+`provides`
+
+
 ## Appendices
 
 ### Summary of Property Requirements