++ +SPDX and ARIA’s
+aria-descriptionare normative, as they promote accessibility and scene transcripts: please startaria-descriptionwith a verb to aid transcripts.
The following metadata are non-normative but encouraged, since they are popular and cheap to parse:
+ +og:*: .....)dc:*: .....){ and },ARIA (aria-description) is the most important to support, as it promotes accessibility and allows scene transcripts. Please start aria-description with a verb to aid transcripts.
@@ -1526,7 +1534,7 @@ Instead, it encourages browsers to scan nodes for the following custom propertieExample: object ‘tryceratops’ with
aria-description: is a huge dinosaurus standing on a #mountaingenerates transcript#tryceratops is a huge dinosaurus standing on a #mountain, where the hashtags are clickable XR Fragments (activating the visible-links in the XR browser).
* = these are interchangable (only one needs to be defined)
-There’s no silver bullet when it comes to metadata, so one should support where the metadata is/goes.
+There’s no silver bullet when it comes to metadata, so XR Fragment-implementations should support where the metadata is/goes.
These attributes can be scanned and presented during an
diff --git a/doc/RFC_XR_Fragments.md b/doc/RFC_XR_Fragments.md index d056ae5..a2fe499 100644 --- a/doc/RFC_XR_Fragments.md +++ b/doc/RFC_XR_Fragments.md @@ -956,11 +956,16 @@ Instead, it encourages browsers to scan nodes for the following custom propertie * [SPDX](https://spdx.dev/) license information * [ARIA](https://www.w3.org/WAI/standards-guidelines/aria/) attributes (`aria-*: .....`) + +> SPDX and ARIA's `aria-description` are normative, as they promote accessibility and scene transcripts: please start `aria-description` with a verb to aid transcripts. + +The following metadata are non-normative but encouraged, since they are popular and cheap to parse: + +* [RDF/JSON-LD](https://json-ld.org) like [this example](https://mvmd.org/standards/gltf/) or via glTF's [KHR_xmp_json_ld extension](https://github.com/KhronosGroup/glTF/tree/main/extensions/2.0/Khronos/KHR_xmp_json_ld) * [Open Graph](https://ogp.me) attributes (`og:*: .....`) * [Dublin-Core](https://www.dublincore.org/specifications/dublin-core/application-profile-guidelines/) attributes(`dc:*: .....`) * [BibTex](https://bibtex.eu/fields) when known bibtex-keys exist with values enclosed in `{` and `},` -**ARIA** (`aria-description`) is the most important to support, as it promotes accessibility and allows scene transcripts. Please start `aria-description` with a verb to aid transcripts. > Example: object 'tryceratops' with `aria-description: is a huge dinosaurus standing on a #mountain` generates transcript `#tryceratops is a huge dinosaurus standing on a #mountain`, where the hashtags are clickable XR Fragments (activating the visible-links in the XR browser). @@ -980,7 +985,7 @@ Individual nodes can be enriched with such metadata, but most importantly the sc > \* = these are interchangable (only one needs to be defined) -There's no silver bullet when it comes to metadata, so one should support where the metadata is/goes. +There's no silver bullet when it comes to metadata, so XR Fragment-implementations should support where the metadata is/goes. > These attributes can be scanned and presented during an `href` or `src` eye/mouse-over. diff --git a/doc/RFC_XR_Fragments.xml b/doc/RFC_XR_Fragments.xml index d649dca..10e3f53 100644 --- a/doc/RFC_XR_Fragments.xml +++ b/doc/RFC_XR_Fragments.xml @@ -1295,11 +1295,16 @@ Instead, it encourages browsers to scan nodes for the following custom propertiehreforsrceye/mouse-over.+
SPDX license information- +
ARIA attributes (aria-*: .....)SPDX and ARIA's aria-description are normative, as they promote accessibility and scene transcripts: please start aria-description with a verb to aid transcripts. +The following metadata are non-normative but encouraged, since they are popular and cheap to parse: + ++
-RDF/JSON-LD likethis example or via glTF'sKHR_xmp_json_ld extension Open Graph attributes (og:*: .....)Dublin-Core attributes(dc:*: .....)BibTex when known bibtex-keys exist with values enclosed in { and },ARIA (aria-description) is the most important to support, as it promotes accessibility and allows scene transcripts. Please start aria-description with a verb to aid transcripts. Example: object 'tryceratops' with aria-description: is a huge dinosaurus standing on a #mountain generates transcript #tryceratops is a huge dinosaurus standing on a #mountain, where the hashtags are clickable XR Fragments (activating the visible-links in the XR browser). Individual nodes can be enriched with such metadata, but most importantly the scene node: @@ -1357,7 +1362,7 @@ Instead, it encourages browsers to scan nodes for the following custom propertie
* = these are interchangable (only one needs to be defined) -There's no silver bullet when it comes to metadata, so one should support where the metadata is/goes. +
diff --git a/doc/shell.nix b/doc/shell.nix index 72df7e8..3ff4bf4 100644 --- a/doc/shell.nix +++ b/doc/shell.nix @@ -6,6 +6,7 @@ mmark xml2rfc + python312Packages.lxml wkhtmltopdf-bin imagemagickThese attributes can be scanned and presented during an href or src eye/mouse-over.