An XML Schema for the Controlling Multiple Streams for Telepresence (CLUE) Data Model
RFC 8846
Internet Engineering Task Force (IETF) R. Presta
Request for Comments: 8846 S P. Romano
Category: Standards Track University of Napoli
ISSN: 2070-1721 January 2021
An XML Schema for the Controlling Multiple Streams for Telepresence
(CLUE) Data Model
Abstract
This document provides an XML schema file for the definition of CLUE
data model types. The term "CLUE" stands for "Controlling Multiple
Streams for Telepresence" and is the name of the IETF working group
in which this document, as well as other companion documents, has
been developed. The document defines a coherent structure for
information associated with the description of a telepresence
scenario.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force
(IETF). It represents the consensus of the IETF community. It has
received public review and has been approved for publication by the
Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 7841.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
https://www.rfc-editor.org/info/rfc8846.
Copyright Notice
Copyright (c) 2021 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction
2. Terminology
3. Definitions
4. XML Schema
5. <mediaCaptures>
6. <encodingGroups>
7. <captureScenes>
8. <simultaneousSets>
9. <globalViews>
10. <captureEncodings>
11. <mediaCapture>
11.1. captureID Attribute
11.2. mediaType Attribute
11.3. <captureSceneIDREF>
11.4. <encGroupIDREF>
11.5. <spatialInformation>
11.5.1. <captureOrigin>
11.5.2. <captureArea>
11.6. <nonSpatiallyDefinable>
11.7. <content>
11.8. <synchronizationID>
11.9. <allowSubsetChoice>
11.10. <policy>
11.11. <maxCaptures>
11.12. <individual>
11.13. <description>
11.14. <priority>
11.15. <lang>
11.16. <mobility>
11.17. <relatedTo>
11.18. <view>
11.19. <presentation>
11.20. <embeddedText>
11.21. <capturedPeople>
11.21.1. <personIDREF>
12. Audio Captures
12.1. <sensitivityPattern>
13. Video Captures
14. Text Captures
15. Other Capture Types
16. <captureScene>
16.1. <sceneInformation>
16.2. <sceneViews>
16.3. sceneID Attribute
16.4. scale Attribute
17. <sceneView>
17.1. <mediaCaptureIDs>
17.2. sceneViewID Attribute
18. <encodingGroup>
18.1. <maxGroupBandwidth>
18.2. <encodingIDList>
18.3. encodingGroupID Attribute
19. <simultaneousSet>
19.1. setID Attribute
19.2. mediaType Attribute
19.3. <mediaCaptureIDREF>
19.4. <sceneViewIDREF>
19.5. <captureSceneIDREF>
20. <globalView>
21. <people>
21.1. <person>
21.1.1. personID Attribute
21.1.2. <personInfo>
21.1.3. <personType>
22. <captureEncoding>
22.1. <captureID>
22.2. <encodingID>
22.3. <configuredContent>
23. <clueInfo>
24. XML Schema Extensibility
24.1. Example of Extension
25. Security Considerations
26. IANA Considerations
26.1. XML Namespace Registration
26.2. XML Schema Registration
26.3. Media Type Registration for "application/clue_info+xml"
26.4. Registry for Acceptable <view> Values
26.5. Registry for Acceptable <presentation> Values
26.6. Registry for Acceptable <sensitivityPattern> Values
26.7. Registry for Acceptable <personType> Values
27. Sample XML File
28. MCC Example
29. References
29.1. Normative References
29.2. Informative References
Acknowledgements
Authors' Addresses
1. Introduction
This document provides an XML schema file for the definition of CLUE
data model types. For the benefit of the reader, the term "CLUE"
stands for "Controlling Multiple Streams for Telepresence" and is the
name of the IETF working group in which this document, as well as
other companion documents, has been developed. A thorough definition
Show full document text