rfc8846xml2.original.xml   rfc8846.xml 
<?xml version="1.0" encoding="us-ascii"?> <?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd"> <!DOCTYPE rfc SYSTEM "rfc2629-xhtml.ent">
<?rfc toc="yes" ?>
<?rfc compact="yes" ?>
<?rfc subcompact="no"?>
<?rfc sortrefs="yes" ?>
<?rfc symrefs="yes" ?>
<?rfc rfcedstyle="yes" ?>
<rfc docTitle="draft-ietf-clue-data-model-schema-17"
submissionType="IETF"
consensus="yes"
category="std" ipr="trust200902">
<front> <rfc xmlns:xi="http://www.w3.org/2001/XInclude" submissionType="IETF" consensus=
<title abbrev="draft-ietf-clue-data-model-schema-17"> "true" category="std" ipr="trust200902" number="8846" docName="draft-ietf-clue-d
An XML Schema for the CLUE data model ata-model-schema-17" obsoletes="" updates="" xml:lang="en" tocInclude="true" sor
</title> tRefs="true" symRefs="true" version="3">
<!-- xml2rfc v2v3 conversion 2.37.3 -->
<front>
<author initials="R." surname="Presta" fullname="Roberta Presta"> <!--[rfced] We have updated the short title that appears in the running header
<organization>University of Napoli</organization> as follows; please let us know if this is agreeable or if you prefer
<address> otherwise. Also note that the title of the document has been updated as
<postal> follows. The abbreviation has been expanded per Section 3.6 of RFC 7322
<street>Via Claudio 21</street> (“RFC Style Guide”). Please review.
<code>80125</code>
<city>Napoli</city>
<country>Italy</country>
</postal>
<email>roberta.presta@unina.it</email>
</address>
</author>
<author initials="S P" surname="Romano" fullname="Simon Pietro Romano">
<organization>University of Napoli</organization>
<address>
<postal>
<street>Via Claudio 21</street>
<code>80125</code>
<city>Napoli</city>
<country>Italy</country>
</postal>
<email>spromano@unina.it</email>
</address>
</author>
<date month="August" year="2016"/> Short title
<area>ART</area> Original:
<workgroup>CLUE Working Group</workgroup> draft-ietf-clue-data-model-schema-17
<!-- [rfced] Please insert any keywords (beyond those that appear in Current:
the title) for use on http://www.rfc-editor.org/rfcsearch.html. --> XML Schema for CLUE Data Model
<keyword>CLUE</keyword>
<keyword>Telepresence</keyword>
<keyword>Data Model</keyword>
<keyword>Framework</keyword>
<abstract> ***
<t> Main title
Original:
An XML Schema for the CLUE data model
Current:
An XML Schema for the Controlling Multiple
Streams for Telepresence (CLUE) Data Model
-->
<title abbrev="An XML Schema for the CLUE Data Model">
An XML Schema for the Controlling Multiple
Streams for Telepresence (CLUE) Data Model
</title>
<seriesInfo name="RFC" value="8846"/>
<author initials="R." surname="Presta" fullname="Roberta Presta">
<organization>University of Napoli</organization>
<address>
<postal>
<street>Via Claudio 21</street>
<code>80125</code>
<city>Napoli</city>
<country>Italy</country>
</postal>
<email>roberta.presta@unina.it</email>
</address>
</author>
<author initials="S P." surname="Romano" fullname="Simon Pietro Romano">
<organization>University of Napoli</organization>
<address>
<postal>
<street>Via Claudio 21</street>
<code>80125</code>
<city>Napoli</city>
<country>Italy</country>
</postal>
<email>spromano@unina.it</email>
</address>
</author>
<date month="June" year="2020"/>
<area>ART</area>
<workgroup>CLUE Working Group</workgroup>
<keyword>CLUE</keyword>
<keyword>Telepresence</keyword>
<keyword>Data Model</keyword>
<keyword>Framework</keyword>
<abstract>
<t>
This document provides an XML schema file This document provides an XML schema file
for the definition of CLUE data model types. The term "CLUE" stands for for the definition of CLUE data model types. The term "CLUE" stands for
"ControLling mUltiple streams for tElepresence" and is the name of "Controlling Multiple Streams for Telepresence" and is the name of
the IETF working group in which this document, as well as other the IETF working group in which this document, as well as other
companion documents, has been developed. The document defines a coherent companion documents, has been developed. The document defines a coherent
structure for information associated with the description of a structure for information associated with the description of a
telepresence scenario. telepresence scenario.
</t> </t>
</abstract> </abstract>
</front>
</front> <middle>
<middle>
<!-- Introduction --> <section anchor="sec-intro" numbered="true" toc="default">
<section title="Introduction" anchor="sec-intro"> <name>Introduction</name>
<t> <t>
This document provides an XML schema file This document provides an XML schema file
for the definition of CLUE data model types. For the benefit of the for the definition of CLUE data model types. For the benefit of the
reader, the term 'CLUE' stands for reader, the term "CLUE" stands for
"ControLling mUltiple streams for tElepresence" and is the name of "Controlling Multiple Streams for Telepresence" and is the name of
the IETF working group in which this document, as well as other the IETF working group in which this document, as well as other
companion documents, has been developed. companion documents, has been developed.
A thorough definition of the CLUE A thorough definition of the CLUE
framework can be found in <xref target="I-D.ietf-clue-framework"/>. framework can be found in <xref target="RFC8845" format="default"/>.
</t> </t>
<t> <t>
The schema is based on information contained in The schema is based on information contained in
<xref target="I-D.ietf-clue-framework"/>. <xref target="RFC8845" format="default"/>.
It encodes information and constraints defined in the It encodes information and constraints defined in the
aforementioned document in order to provide a formal representation aforementioned document in order to provide a formal representation
of the concepts therein presented. of the concepts therein presented.
<!--
The schema definition is intended to be modified according to changes
applied to the above mentioned CLUE document.
-->
</t> </t>
<t> <t>
<!--[rfced] Please clarify "The document aims at the definition". Is
the intended meaning perhaps 'outlines' or 'specifies' the
definition?
Original:
The document aims at the definition of a coherent structure for
information associated with the description of a telepresence
scenario.
Perhaps:
The document specifies the definition of a coherent structure for
information associated with the description of a telepresence
scenario.
-->
The document aims at the definition of a coherent structure for The document aims at the definition of a coherent structure for
information associated with the description of a telepresence information associated with the description of a telepresence
scenario. Such information is used within the CLUE protocol messages scenario. Such information is used within the CLUE protocol messages
(<xref target="I-D.ietf-clue-protocol"/>) enabling the dialogue between <xref target="RFC8847" format="default"/>, enabling the dialogue between
a Media Provider and a Media Consumer. CLUE protocol messages, indeed, a Media Provider and a Media Consumer. CLUE protocol messages, indeed,
are XML messages allowing (i) a Media Provider to advertise its are XML messages allowing (i) a Media Provider to advertise its
telepresence capabilities in terms of media captures, capture scenes, telepresence capabilities in terms of media captures, capture scenes,
and other features envisioned in the CLUE framework, according to the and other features envisioned in the CLUE framework, according to the
format herein defined and (ii) a Media Consumer to request the format herein defined and (ii) a Media Consumer to request the
desired telepresence options in the form of capture encodings, desired telepresence options in the form of capture encodings,
represented as described in this document. represented as described in this document.
</t> </t>
<t> </section>
<section anchor="sec-teminology" numbered="true" toc="default">
<name>Terminology</name>
<t>
The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQU
IRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL
NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>
RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>",
"<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" in this document are to
be interpreted as
described in BCP&nbsp;14 <xref target="RFC2119"/> <xref target="RFC8174"/>
when, and only when, they appear in all capitals, as shown here.
</t> </t>
</section> </section>
<!-- Terminology --> <section anchor="sec-definitions" numbered="true" toc="default">
<section title="Terminology" anchor="sec-teminology"> <name>Definitions</name>
<t>
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in
this document are to be interpreted as described in
<xref target="RFC2119"/>.
</t>
</section>
<!-- Definitions --> <!-- [rfced] Several of the definitions are for the same
<section title="Definitions" anchor="sec-definitions"> terms as in RFC-to-be 8845, but the definitions do not exactly
<t> This document refers to the same definitions used in match. Would you like the definitions to be updated to exactly match?
<xref target="I-D.ietf-clue-framework"/>, except for the "CLUE (If so, please let us know which to use.)
Participant" definition. Alternatively, one document could contain the information, and the
We briefly recall herein some of the main terms used in the document. other could refer to it, e.g., "The definitions in RFC 8845 apply here."
</t> Examples:
<t> This document (current):
<list style="hanging"> Render: The process of reproducing the received Streams - for
instance, displaying the remote video on the Media Consumer's
screens or playing the remote audio through loudspeakers.
vs.
<t hangText="Audio Capture:"> RFC-to-be 8845 (current):
Media Capture for audio. Denoted as ACn in the examples in this Render: The process of generating a representation from media, such
document. as displayed motion video or sound emitted from loudspeakers.
</t>
<t hangText="Capture:">Same as Media Capture.</t> This document (current):
Stream Characteristics: The union of the features used to describe a
Stream in the CLUE environment and in the SIP/SDP environment.
vs.
<t hangText="Capture Device:">A device that converts physical input, RFC-to-be 8845 (current):
such as audio, video or text, into an electrical signal, in most Stream Characteristics: The media stream attributes commonly used in
cases to be fed into a media encoder. non-CLUE SIP/SDP environments (such as media codec, bitrate,
</t> resolution, profile/level, etc.) as well as CLUE-specific
attributes, such as the Capture ID or a spatial location.
-->
<t hangText="Capture Encoding:">A specific encoding of a Media Capture, <t>This document refers to the same definitions used in
to be sent by a Media Provider to a Media Consumer via RTP. <xref target="RFC8845" format="default"/>, except for the "CLUE
Participant" definition.
We briefly recall herein some of the main terms used in the document.
</t> </t>
<dl newline="false" spacing="normal">
<t hangText="Capture Scene:">A structure representing a spatial region <dt>Audio Capture:</dt> <dd>Media Capture for audio. Denoted as "ACn" i
n the examples in this
document.
</dd>
<dt>Capture:</dt><dd>Same as Media Capture.</dd>
<dt>Capture Device:</dt><dd>A device that converts physical input,
such as audio, video, or text, into an electrical signal, in most
cases to be fed into a media encoder.
</dd>
<dt>Capture Encoding:</dt><dd>A specific encoding of a Media Capture,
to be sent by a Media Provider to a Media Consumer via RTP.
</dd>
<dt>Capture Scene:</dt>
<dd>A structure representing a spatial region
captured by one or more Capture Devices, each capturing media captured by one or more Capture Devices, each capturing media
representing a portion of the region. The spatial region represented representing a portion of the region. The spatial region represented
by a Capture Scene MAY correspond to a real region in physical space, by a Capture Scene <bcp14>MAY</bcp14> correspond to a real region in physical space,
such as a room. A Capture Scene includes attributes and one or more such as a room. A Capture Scene includes attributes and one or more
Capture Scene Views, with each view including one or more Media Capture Scene Views, with each view including one or more Media
Captures. Captures.
</t> </dd>
<dt>Capture Scene View:</dt>
<t hangText="Capture Scene View:"> A list of Media Captures of the same <dd> A list of Media Captures of the same
media type that together form one way to represent the entire media type that together form one way to represent the entire
Capture Scene. Capture Scene.
</t> </dd>
<!--[rfced] Should a brief definition of "CLUE Participant" be added
<t hangText="CLUE Participant:"> to the following since all of the other terms in this list
This term is imported from the CLUE protocol include a definition?
(<xref target="I-D.ietf-clue-protocol"/>) document.
</t>
<t hangText="Consumer:">Short for Media Consumer.</t>
<t hangText="Encoding or Individual Encoding:"> Original:
CLUE Participant: This term is imported from the CLUE protocol
([I-D.ietf-clue-protocol]) document.
-->
<dt>CLUE Participant:</dt>
<dd>
This term is imported from the CLUE protocol document
<xref target="RFC8847" format="default"/>.
</dd>
<dt>Consumer:</dt>
<dd>Short for Media Consumer.</dd>
<dt>Encoding or Individual Encoding:</dt>
<dd>
A set of parameters representing a way to encode a Media Capture to A set of parameters representing a way to encode a Media Capture to
become a Capture Encoding. become a Capture Encoding.
</t> </dd>
<dt>Encoding Group:</dt>
<t hangText="Encoding Group:"> <dd>
A set of encoding parameters representing a total A set of encoding parameters representing a total
media encoding capability to be sub-divided across potentially media encoding capability to be subdivided across potentially
multiple Individual Encodings. multiple Individual Encodings.
</t> </dd>
<t hangText="Endpoint">A CLUE-capable device which is the logical point <!--[rfced] There is one instance of 'Participant' (capitalized) in
of final termination through receiving, decoding and rendering, the sentence below; is this referring to the 'CLUE Participant'?
and/or initiation through capturing, encoding, and sending of media If so, may we add 'CLUE'? If not, and this is a general term, may
streams. An endpoint consists of one or more physical devices we lowercase 'participant'?
which source and sink media streams, and exactly one
<xref target="RFC4353"/> Original:
An endpoint consists of one or more physical devices
which source and sink media streams, and exactly one [RFC4353]
Participant (which, in turn, includes exactly one SIP User Agent). Participant (which, in turn, includes exactly one SIP User Agent).
Endpoints can be anything from multiscreen/multicamera rooms to
handheld devices.</t>
<t hangText="Media:">Any data that, after suitable encoding, can be Perhaps:
An endpoint consists of one or more physical devices
that source and sink media streams and exactly one
participant [RFC4353] (which, in turn, includes exactly
one SIP User Agent).
-->
<dt>Endpoint:</dt>
<dd>A CLUE-capable device that is the logical point
of final termination through receiving, decoding, and rendering
and/or initiation through capturing, encoding, and sending of media
streams. An endpoint consists of one or more physical devices
that source and sink media streams and exactly one
Participant <xref target="RFC4353" format="default"/> (which, in turn, includ
es exactly one SIP User Agent). Endpoints can be anything from multiscreen/mult
icamera rooms to
handheld devices.</dd>
<dt>Media:</dt>
<dd>Any data that, after suitable encoding, can be
conveyed over conveyed over
RTP, including audio, video or timed text.</t> RTP, including audio, video, or timed text.</dd>
<dt>Media Capture:</dt>
<t hangText="Media Capture:">A source of Media, such as from one or <dd>A source of Media, such as from one or
more Capture Devices or constructed from other Media streams. more Capture Devices or constructed from other Media streams.
</t> </dd>
<dt>Media Consumer:</dt>
<t hangText="Media Consumer:"> <dd>
A CLUE-capable device that intends to receive Capture Encodings. A CLUE-capable device that intends to receive Capture Encodings.
</t> </dd>
<dt>Media Provider:</dt>
<t hangText="Media Provider:"> <dd>
A CLUE-capable device that intends to send Capture Encodings. A CLUE-capable device that intends to send Capture Encodings.
</t> </dd>
<dt>Multiple Content Capture (MCC):</dt>
<t hangText="Multiple Content Capture:"> <dd>
A Capture that mixes and/or switches other Captures of a single A Capture that mixes and/or switches other Captures of a single
type (e.g., all audio or all video.) Particular Media Captures type (e.g., all audio or all video.) Particular Media Captures
may or may not be present in the resultant Capture Encoding may or may not be present in the resultant Capture Encoding
depending on time or space. Denoted as MCCn in the example cases depending on time or space. Denoted as "MCCn" in the example cases
in this document. in this document.
</t> </dd>
<dt>Multipoint Control Unit (MCU):</dt>
<t hangText="Multipoint Control Unit (MCU):">A CLUE-capable device <dd>A CLUE-capable device
that connects that connects
two or more endpoints together into one single multimedia two or more endpoints together into one single multimedia
conference <xref target="RFC7667"/>. An MCU includes an conference <xref target="RFC7667" format="default"/>.
<xref target="RFC4353"/> like Mixer,
without the <xref target="RFC4353"/> requirement to send media to
each participant.
</t>
<t hangText="Plane of Interest:"> <!--[rfced] How may we rephrase this sentence in order to avoid
The spatial plane containing the most relevant subject matter. hyphenating "[RFC4353]-like Mixer"?
</t>
<t hangText="Provider:">Same as Media Provider.</t> Original:
An MCU includes an [RFC4353] like Mixer,
without the [RFC4353] requirement to send media to each
participant.
<t hangText="Render: ">The process of reproducing the received Streams Perhaps:
like, for instance, displaying of the remote video on the Media An MCU includes a Mixer, similar to those in [RFC4353],
Consumer's screens, or playing of the remote audio through but without the requirement to send media to each
participant.
-->
An MCU includes an
<xref target="RFC4353" format="default"/> like Mixer,
without the <xref target="RFC4353" format="default"/> requirement to send med
ia to
each participant.
</dd>
<dt>Plane of Interest:</dt>
<dd>
The spatial plane containing the most relevant subject matter.
</dd>
<dt>Provider:</dt>
<dd>Same as Media Provider.</dd>
<dt>Render: </dt>
<dd>The process of reproducing the received Streams --
for instance, displaying the remote video on the Media
Consumer's screens or playing the remote audio through
loudspeakers. loudspeakers.
</t> </dd>
<dt>Scene:</dt>
<t hangText="Scene:">Same as Capture Scene.</t> <dd>Same as Capture Scene.</dd>
<dt>Simultaneous Transmission Set:</dt>
<t hangText="Simultaneous Transmission Set:"> <dd>
A set of Media Captures that can be transmitted simultaneously A set of Media Captures that can be transmitted simultaneously
from a Media Provider. from a Media Provider.
</t> </dd>
<dt>Single Media Capture:</dt>
<t hangText="Single Media Capture:"> <dd>
A capture which contains media from a single A capture that contains media from a single
source capture device, e.g., an audio capture from a single source capture device, e.g., an audio capture from a single
microphone, a video capture from a single camera. microphone or a video capture from a single camera.
</t> </dd>
<dt>Spatial Relation:</dt>
<t hangText="Spatial Relation:"> <dd>
The arrangement in space of two objects, in contrast to relation in The arrangement of two objects in space, in contrast to relation in
time or other relationships. time or other relationships.
</t> </dd>
<dt>Stream:</dt>
<t hangText="Stream:"> <dd>
A Capture Encoding sent from a Media Provider to a Media Consumer A Capture Encoding sent from a Media Provider to a Media Consumer
via RTP <xref target="RFC3550"/>. via RTP <xref target="RFC3550" format="default"/>.
</t> </dd>
<dt>Stream Characteristics:</dt>
<t hangText="Stream Characteristics:">The union of the features used to <dd>The union of the features used to
describe describe
a Stream in the CLUE environment and in the SIP-SDP environment.</t> a Stream in the CLUE environment and in the SIP/SDP environment.</dd>
<dt>Video Capture:</dt>
<t hangText="Video Capture:">A Media Capture for video.</t> <dd>A Media Capture for video.</dd>
</dl>
</list> </section>
</t>
</section>
<!-- Schema File --> <section anchor="sec-schema" numbered="true" toc="default">
<section title="XML Schema" anchor="sec-schema"> <name>XML Schema</name>
<t> <t>
This section contains the CLUE data model schema definition. This section contains the CLUE data model schema definition.
</t> </t>
<t> <t>
The element and attribute definitions are formal representations of the The element and attribute definitions are formal representations of the
concepts concepts
needed to describe the capabilities of a Media Provider and the streams needed to describe the capabilities of a Media Provider and the streams
that are requested by a Media Consumer given the Media Provider's that are requested by a Media Consumer given the Media Provider's
ADVERTISEMENT (<xref target="I-D.ietf-clue-protocol"/>). ADVERTISEMENT <xref target="RFC8847" format="default"/>.
</t> </t>
<t>The main groups of information are:</t>
<t>The main groups of information are:</t> <ul empty="true" spacing="normal">
<list style="empty"> <li>
<t>&lt;mediaCaptures&gt;: the list of media captures available <dl newline="false" spacing="normal">
(<xref target="sec-media-captures"/>)</t> <dt>&lt;mediaCaptures&gt;:</dt><dd>the list of media captures available
<t>&lt;encodingGroups&gt;: the list of encoding groups (<xref target="sec-media-captures" format="default"/>)</dd>
(<xref target="sec-encoding-groups"/>)</t>
<t>&lt;captureScenes&gt;: the list of capture scenes
(<xref target="sec-capture-scenes"/>)</t>
<t>&lt;simultaneousSets&gt;: the list of simultaneous transmission
sets (<xref target="sec-simultaneous-sets"/>)</t>
<t>&lt;globalViews&gt;: the list of global views sets
(<xref target="sec-global-views"/>)</t>
<t>&lt;people&gt;: meta data about the participants represented
in the telepresence session (<xref target="sec-participants"/>)</t>
<t>&lt;captureEncodings&gt;: the list of instantiated capture
encodings (<xref target="sec-capture-encodings"/>)</t>
</list> <dt>&lt;encodingGroups&gt;:</dt><dd>the list of encoding groups
<t> (<xref target="sec-encoding-groups" format="default"/>)</dd>
All of the above refers to concepts that have been
introduced in <xref target="I-D.ietf-clue-framework"/> <dt>&lt;captureScenes&gt;:</dt><dd>the list of capture scenes
(<xref target="sec-capture-scenes" format="default"/>)</dd>
<dt>&lt;simultaneousSets&gt;:</dt><dd>the list of simultaneous transmiss
ion
sets (<xref target="sec-simultaneous-sets" format="default"/>)</dd>
<dt>&lt;globalViews&gt;:</dt><dd>the list of global views sets
(<xref target="sec-global-views" format="default"/>)</dd>
<dt>&lt;people&gt;:</dt><dd>metadata about the participants represented
in the telepresence session (<xref target="sec-participants" format="default"/
>)</dd>
<dt>&lt;captureEncodings&gt;:</dt><dd>the list of instantiated capture
encodings (<xref target="sec-capture-encodings" format="default"/>)</dd>
</dl></li>
</ul>
<t>
All of the above refer to concepts that have been
introduced in <xref target="RFC8845" format="default"/>
and further detailed in this document. and further detailed in this document.
</t> </t>
<figure> <!--[rfced] Is it intentional that the entities &lt; and &gt;
<artwork> are used in Section 4, but they are not used elsewhere in the
<![CDATA[ document (for the same text)? For example:
Section 4:
by IANA in the "CLUE Schema &lt;personType&gt; registry"
Section 21.1.3:
by IANA in the "CLUE Schema <personType> registry",
-->
<!--[rfced] FYI, two lines within the XML schema exceed
the 69-character limit, so we inserted a line break as
follows. Please review and and let us know if any further
changes are needed.
Original:
schemaLocation=
"http://www.iana.org/assignments/xml-registry/schema/vcard-4.0.xsd"/>
Current:
schemaLocation=
"https://www.iana.org/assignments/xml-registry/schema/
vcard-4.0.xsd"/>
-->
<sourcecode type="xml"><![CDATA[
<?xml version="1.0" encoding="UTF-8" ?> <?xml version="1.0" encoding="UTF-8" ?>
<xs:schema <xs:schema
targetNamespace="urn:ietf:params:xml:ns:clue-info" targetNamespace="urn:ietf:params:xml:ns:clue-info"
xmlns:tns="urn:ietf:params:xml:ns:clue-info" xmlns:tns="urn:ietf:params:xml:ns:clue-info"
xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns="urn:ietf:params:xml:ns:clue-info" xmlns="urn:ietf:params:xml:ns:clue-info"
xmlns:xcard="urn:ietf:params:xml:ns:vcard-4.0" xmlns:xcard="urn:ietf:params:xml:ns:vcard-4.0"
elementFormDefault="qualified" elementFormDefault="qualified"
attributeFormDefault="unqualified" attributeFormDefault="unqualified"
version="1.0"> version="1.0">
<!-- Import xcard XML schema --> <!-- Import xCard XML schema -->
<xs:import namespace="urn:ietf:params:xml:ns:vcard-4.0" <xs:import namespace="urn:ietf:params:xml:ns:vcard-4.0"
schemaLocation= schemaLocation=
"http://www.iana.org/assignments/xml-registry/schema/vcard-4.0.xsd"/> "https://www.iana.org/assignments/xml-registry/schema/
vcard-4.0.xsd"/>
<!-- ELEMENT DEFINITIONS --> <!-- ELEMENT DEFINITIONS -->
<xs:element name="mediaCaptures" type="mediaCapturesType"/> <xs:element name="mediaCaptures" type="mediaCapturesType"/>
<xs:element name="encodingGroups" type="encodingGroupsType"/> <xs:element name="encodingGroups" type="encodingGroupsType"/>
<xs:element name="captureScenes" type="captureScenesType"/> <xs:element name="captureScenes" type="captureScenesType"/>
<xs:element name="simultaneousSets" type="simultaneousSetsType"/> <xs:element name="simultaneousSets" type="simultaneousSetsType"/>
<xs:element name="globalViews" type="globalViewsType"/> <xs:element name="globalViews" type="globalViewsType"/>
<xs:element name="people" type="peopleType"/> <xs:element name="people" type="peopleType"/>
<xs:element name="captureEncodings" type="captureEncodingsType"/> <xs:element name="captureEncodings" type="captureEncodingsType"/>
skipping to change at line 370 skipping to change at line 481
<!-- mandatory fields --> <!-- mandatory fields -->
<xs:element name="captureSceneIDREF" type="xs:IDREF"/> <xs:element name="captureSceneIDREF" type="xs:IDREF"/>
<xs:choice> <xs:choice>
<xs:sequence> <xs:sequence>
<xs:element name="spatialInformation" <xs:element name="spatialInformation"
type="tns:spatialInformationType"/> type="tns:spatialInformationType"/>
</xs:sequence> </xs:sequence>
<xs:element name="nonSpatiallyDefinable" type="xs:boolean" <xs:element name="nonSpatiallyDefinable" type="xs:boolean"
fixed="true"/> fixed="true"/>
</xs:choice> </xs:choice>
<!-- for handling multi-content captures: --> <!-- for handling multicontent captures: -->
<xs:choice> <xs:choice>
<xs:sequence> <xs:sequence>
<xs:element name="synchronizationID" type="xs:ID" <xs:element name="synchronizationID" type="xs:ID"
minOccurs="0"/> minOccurs="0"/>
<xs:element name="content" type="contentType" minOccurs="0"/> <xs:element name="content" type="contentType" minOccurs="0"/>
<xs:element name="policy" type="policyType" minOccurs="0"/> <xs:element name="policy" type="policyType" minOccurs="0"/>
<xs:element name="maxCaptures" type="maxCapturesType" <xs:element name="maxCaptures" type="maxCapturesType"
minOccurs="0"/> minOccurs="0"/>
<xs:element name="allowSubsetChoice" type="xs:boolean" <xs:element name="allowSubsetChoice" type="xs:boolean"
minOccurs="0"/> minOccurs="0"/>
</xs:sequence> </xs:sequence>
<xs:element name="individual" type="xs:boolean" fixed="true"/> <xs:element name="individual" type="xs:boolean" fixed="true"/>
</xs:choice> </xs:choice>
<!-- optional fields --> <!-- optional fields -->
<xs:element name="encGroupIDREF" type="xs:IDREF" minOccurs="0"/> <xs:element name="encGroupIDREF" type="xs:IDREF" minOccurs="0"/>
<xs:element ref="description" minOccurs="0" maxOccurs="unbounded"/> <xs:element ref="description" minOccurs="0"
maxOccurs="unbounded"/>
<xs:element name="priority" type="xs:unsignedInt" minOccurs="0"/> <xs:element name="priority" type="xs:unsignedInt" minOccurs="0"/>
<xs:element name="lang" type="xs:language" minOccurs="0" <xs:element name="lang" type="xs:language" minOccurs="0"
maxOccurs="unbounded"/> maxOccurs="unbounded"/>
<xs:element name="mobility" type="mobilityType" minOccurs="0" /> <xs:element name="mobility" type="mobilityType"
minOccurs="0" />
<xs:element ref="presentation" minOccurs="0" /> <xs:element ref="presentation" minOccurs="0" />
<xs:element ref="embeddedText" minOccurs="0" /> <xs:element ref="embeddedText" minOccurs="0" />
<xs:element ref="view" minOccurs="0" /> <xs:element ref="view" minOccurs="0" />
<xs:element name="capturedPeople" type="capturedPeopleType" <xs:element name="capturedPeople" type="capturedPeopleType"
minOccurs="0"/> minOccurs="0"/>
<xs:element name="relatedTo" type="xs:IDREF" minOccurs="0"/> <xs:element name="relatedTo" type="xs:IDREF" minOccurs="0"/>
</xs:sequence> </xs:sequence>
<xs:attribute name="captureID" type="xs:ID" use="required"/> <xs:attribute name="captureID" type="xs:ID" use="required"/>
<xs:attribute name="mediaType" type="xs:string" use="required"/> <xs:attribute name="mediaType" type="xs:string" use="required"/>
skipping to change at line 413 skipping to change at line 526
<!-- POLICY TYPE --> <!-- POLICY TYPE -->
<xs:simpleType name="policyType"> <xs:simpleType name="policyType">
<xs:restriction base="xs:string"> <xs:restriction base="xs:string">
<xs:pattern value="([a-zA-Z0-9])+[:]([0-9])+"/> <xs:pattern value="([a-zA-Z0-9])+[:]([0-9])+"/>
</xs:restriction> </xs:restriction>
</xs:simpleType> </xs:simpleType>
<!-- CONTENT TYPE --> <!-- CONTENT TYPE -->
<xs:complexType name="contentType"> <xs:complexType name="contentType">
<xs:sequence> <xs:sequence>
<xs:element name="mediaCaptureIDREF" type="xs:IDREF" <xs:element name="mediaCaptureIDREF" type="xs:string"
minOccurs="0" maxOccurs="unbounded"/> minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="sceneViewIDREF" type="xs:IDREF" <xs:element name="sceneViewIDREF" type="xs:string"
minOccurs="0" maxOccurs="unbounded"/> minOccurs="0" maxOccurs="unbounded"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" <xs:any namespace="##other" processContents="lax" minOccurs="0"
maxOccurs="unbounded"/> maxOccurs="unbounded"/>
</xs:sequence> </xs:sequence>
<xs:anyAttribute namespace="##other" processContents="lax"/> <xs:anyAttribute namespace="##other" processContents="lax"/>
</xs:complexType> </xs:complexType>
<!-- MAX CAPTURES TYPE --> <!-- MAX CAPTURES TYPE -->
<xs:simpleType name="positiveShort"> <xs:simpleType name="positiveShort">
<xs:restriction base="xs:unsignedShort"> <xs:restriction base="xs:unsignedShort">
<xs:minInclusive value="1"> <xs:minInclusive value="1">
</xs:minInclusive> </xs:minInclusive>
</xs:restriction> </xs:restriction>
</xs:simpleType> </xs:simpleType>
<xs:complexType name="maxCapturesType"> <xs:complexType name="maxCapturesType">
<xs:simpleContent> <xs:simpleContent>
<xs:extension base="positiveShort"> <xs:extension base="positiveShort">
<xs:attribute name="exactNumber" <xs:attribute name="exactNumber"
type="xs:boolean"/> type="xs:boolean"/>
</xs:extension> </xs:extension>
</xs:simpleContent> </xs:simpleContent>
</xs:complexType> </xs:complexType>
<!-- CAPTURED PEOPLE TYPE --> <!-- CAPTURED PEOPLE TYPE -->
<xs:complexType name="capturedPeopleType"> <xs:complexType name="capturedPeopleType">
<xs:sequence> <xs:sequence>
<xs:element name="personIDREF" type="xs:IDREF" maxOccurs="unbounded"/> <xs:element name="personIDREF" type="xs:IDREF"
maxOccurs="unbounded"/>
</xs:sequence> </xs:sequence>
</xs:complexType> </xs:complexType>
<!-- PEOPLE TYPE --> <!-- PEOPLE TYPE -->
<xs:complexType name="peopleType"> <xs:complexType name="peopleType">
<xs:sequence> <xs:sequence>
<xs:element name="person" type="personType" maxOccurs="unbounded"/> <xs:element name="person" type="personType" maxOccurs="unbounded"/>
</xs:sequence> </xs:sequence>
</xs:complexType> </xs:complexType>
<!-- PERSON TYPE --> <!-- PERSON TYPE -->
<xs:complexType name="personType"> <xs:complexType name="personType">
<xs:sequence> <xs:sequence>
<xs:element name="personInfo" type="xcard:vcardType" maxOccurs="1" <xs:element name="personInfo" type="xcard:vcardType"
minOccurs="0"/> maxOccurs="1" minOccurs="0"/>
<xs:element ref="personType" minOccurs="0" maxOccurs="unbounded" /> <xs:element ref="personType" minOccurs="0"
maxOccurs="unbounded" />
<xs:any namespace="##other" processContents="lax" minOccurs="0" <xs:any namespace="##other" processContents="lax" minOccurs="0"
maxOccurs="unbounded"/> maxOccurs="unbounded"/>
</xs:sequence> </xs:sequence>
<xs:attribute name="personID" type="xs:ID" use="required"/> <xs:attribute name="personID" type="xs:ID" use="required"/>
<xs:anyAttribute namespace="##other" processContents="lax"/> <xs:anyAttribute namespace="##other" processContents="lax"/>
</xs:complexType> </xs:complexType>
<!-- PERSON TYPE ELEMENT --> <!-- PERSON TYPE ELEMENT -->
<xs:element name="personType" type="xs:string"> <xs:element name="personType" type="xs:string">
<xs:annotation> <xs:annotation>
<xs:documentation> <xs:documentation>
Acceptable values (enumerations) for this type are managed Acceptable values (enumerations) for this type are managed
by IANA in the "CLUE Schema &lt;personType&gt; registry", by IANA in the "CLUE Schema &lt;personType&gt; registry",
accessible at TBD-IANA. accessible at https://www.iana.org/assignments/clue.
</xs:documentation> </xs:documentation>
</xs:annotation> </xs:annotation>
</xs:element> </xs:element>
<!-- VIEW ELEMENT --> <!-- VIEW ELEMENT -->
<xs:element name="view" type="xs:string"> <xs:element name="view" type="xs:string">
<xs:annotation> <xs:annotation>
<xs:documentation> <xs:documentation>
Acceptable values (enumerations) for this type are managed Acceptable values (enumerations) for this type are managed
by IANA in the "CLUE Schema &lt;view&gt; registry", by IANA in the "CLUE Schema &lt;view&gt; registry",
accessible at TBD-IANA. accessible at https://www.iana.org/assignments/clue.
</xs:documentation> </xs:documentation>
</xs:annotation> </xs:annotation>
</xs:element> </xs:element>
<!-- PRESENTATION ELEMENT --> <!-- PRESENTATION ELEMENT -->
<xs:element name="presentation" type="xs:string"> <xs:element name="presentation" type="xs:string">
<xs:annotation> <xs:annotation>
<xs:documentation> <xs:documentation>
Acceptable values (enumerations) for this type are managed Acceptable values (enumerations) for this type are managed
by IANA in the "CLUE Schema &lt;presentation&gt; registry", by IANA in the "CLUE Schema &lt;presentation&gt; registry",
accessible at TBD-IANA. accessible at https://www.iana.org/assignments/clue.
</xs:documentation> </xs:documentation>
</xs:annotation> </xs:annotation>
</xs:element> </xs:element>
<!-- SPATIAL INFORMATION TYPE --> <!-- SPATIAL INFORMATION TYPE -->
<xs:complexType name="spatialInformationType"> <xs:complexType name="spatialInformationType">
<xs:sequence> <xs:sequence>
<xs:element name="captureOrigin" type="captureOriginType" <xs:element name="captureOrigin" type="captureOriginType"
minOccurs="0"/> minOccurs="0"/>
<xs:element name="captureArea" type="captureAreaType" minOccurs="0"/> <xs:element name="captureArea" type="captureAreaType"
minOccurs="0"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" <xs:any namespace="##other" processContents="lax" minOccurs="0"
maxOccurs="unbounded"/> maxOccurs="unbounded"/>
</xs:sequence> </xs:sequence>
<xs:anyAttribute namespace="##other" processContents="lax"/> <xs:anyAttribute namespace="##other" processContents="lax"/>
</xs:complexType> </xs:complexType>
<!-- POINT TYPE --> <!-- POINT TYPE -->
<xs:complexType name="pointType"> <xs:complexType name="pointType">
<xs:sequence> <xs:sequence>
<xs:element name="x" type="xs:decimal"/> <xs:element name="x" type="xs:decimal"/>
<xs:element name="y" type="xs:decimal"/> <xs:element name="y" type="xs:decimal"/>
<xs:element name="z" type="xs:decimal"/> <xs:element name="z" type="xs:decimal"/>
</xs:sequence> </xs:sequence>
</xs:complexType> </xs:complexType>
<!-- CAPTURE ORIGIN TYPE --> <!-- CAPTURE ORIGIN TYPE -->
<xs:complexType name="captureOriginType"> <xs:complexType name="captureOriginType">
<xs:sequence> <xs:sequence>
<xs:element name="capturePoint" type="pointType"></xs:element> <xs:element name="capturePoint" type="pointType"></xs:element>
<xs:element name="lineOfCapturePoint" type="pointType" <xs:element name="lineOfCapturePoint" type="pointType"
minOccurs="0"> minOccurs="0">
</xs:element> </xs:element>
</xs:sequence> </xs:sequence>
<xs:anyAttribute namespace="##any" processContents="lax"/> <xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType> </xs:complexType>
<!-- CAPTURE AREA TYPE --> <!-- CAPTURE AREA TYPE -->
<xs:complexType name="captureAreaType"> <xs:complexType name="captureAreaType">
<xs:sequence> <xs:sequence>
<xs:element name="bottomLeft" type="pointType"/> <xs:element name="bottomLeft" type="pointType"/>
<xs:element name="bottomRight" type="pointType"/> <xs:element name="bottomRight" type="pointType"/>
<xs:element name="topLeft" type="pointType"/> <xs:element name="topLeft" type="pointType"/>
skipping to change at line 582 skipping to change at line 698
<xs:anyAttribute namespace="##other" processContents="lax"/> <xs:anyAttribute namespace="##other" processContents="lax"/>
</xs:extension> </xs:extension>
</xs:complexContent> </xs:complexContent>
</xs:complexType> </xs:complexType>
<!-- AUDIO CAPTURE TYPE --> <!-- AUDIO CAPTURE TYPE -->
<xs:complexType name="audioCaptureType"> <xs:complexType name="audioCaptureType">
<xs:complexContent> <xs:complexContent>
<xs:extension base="tns:mediaCaptureType"> <xs:extension base="tns:mediaCaptureType">
<xs:sequence> <xs:sequence>
<xs:element ref="sensitivityPattern" minOccurs="0" /> <xs:element ref="sensitivityPattern" minOccurs="0" />
<xs:any namespace="##other" processContents="lax" minOccurs="0" <xs:any namespace="##other" processContents="lax" minOccurs="0"
maxOccurs="unbounded"/> maxOccurs="unbounded"/>
</xs:sequence> </xs:sequence>
<xs:anyAttribute namespace="##other" processContents="lax"/> <xs:anyAttribute namespace="##other" processContents="lax"/>
</xs:extension> </xs:extension>
</xs:complexContent> </xs:complexContent>
</xs:complexType> </xs:complexType>
<!-- SENSITIVITY PATTERN ELEMENT --> <!-- SENSITIVITY PATTERN ELEMENT -->
<xs:element name="sensitivityPattern" type="xs:string"> <xs:element name="sensitivityPattern" type="xs:string">
<xs:annotation> <xs:annotation>
<xs:documentation> <xs:documentation>
Acceptable values (enumerations) for this type are managed by IANA Acceptable values (enumerations) for this type are managed by
in the "CLUE Schema &lt;sensitivityPattern&gt; registry", accessible IANA in the "CLUE Schema &lt;sensitivityPattern&gt; registry",
at TBD-IANA. accessible at https://www.iana.org/assignments/clue.
</xs:documentation> </xs:documentation>
</xs:annotation> </xs:annotation>
</xs:element> </xs:element>
<!-- VIDEO CAPTURE TYPE --> <!-- VIDEO CAPTURE TYPE -->
<xs:complexType name="videoCaptureType"> <xs:complexType name="videoCaptureType">
<xs:complexContent> <xs:complexContent>
<xs:extension base="tns:mediaCaptureType"> <xs:extension base="tns:mediaCaptureType">
<xs:sequence> <xs:sequence>
<xs:any namespace="##other" processContents="lax" minOccurs="0" <xs:any namespace="##other" processContents="lax" minOccurs="0"
skipping to change at line 708 skipping to change at line 824
<xs:any namespace="##other" processContents="lax" minOccurs="0" <xs:any namespace="##other" processContents="lax" minOccurs="0"
maxOccurs="unbounded"/> maxOccurs="unbounded"/>
</xs:sequence> </xs:sequence>
<xs:attribute name="encodingGroupID" type="xs:ID" use="required"/> <xs:attribute name="encodingGroupID" type="xs:ID" use="required"/>
<xs:anyAttribute namespace="##any" processContents="lax"/> <xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType> </xs:complexType>
<!-- ENCODING ID LIST TYPE --> <!-- ENCODING ID LIST TYPE -->
<xs:complexType name="encodingIDListType"> <xs:complexType name="encodingIDListType">
<xs:sequence> <xs:sequence>
<xs:element name="encodingID" type="xs:string" maxOccurs="unbounded"/> <xs:element name="encodingID" type="xs:string"
maxOccurs="unbounded"/>
</xs:sequence> </xs:sequence>
</xs:complexType> </xs:complexType>
<!-- SIMULTANEOUS SETS TYPE --> <!-- SIMULTANEOUS SETS TYPE -->
<xs:complexType name="simultaneousSetsType"> <xs:complexType name="simultaneousSetsType">
<xs:sequence> <xs:sequence>
<xs:element name="simultaneousSet" type="simultaneousSetType" <xs:element name="simultaneousSet" type="simultaneousSetType"
maxOccurs="unbounded"/> maxOccurs="unbounded"/>
</xs:sequence> </xs:sequence>
</xs:complexType> </xs:complexType>
skipping to change at line 798 skipping to change at line 915
<xs:element ref="simultaneousSets" minOccurs="0"/> <xs:element ref="simultaneousSets" minOccurs="0"/>
<xs:element ref="globalViews" minOccurs="0"/> <xs:element ref="globalViews" minOccurs="0"/>
<xs:element ref="people" minOccurs="0"/> <xs:element ref="people" minOccurs="0"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" <xs:any namespace="##other" processContents="lax" minOccurs="0"
maxOccurs="unbounded"/> maxOccurs="unbounded"/>
</xs:sequence> </xs:sequence>
<xs:attribute name="clueInfoID" type="xs:ID" use="required"/> <xs:attribute name="clueInfoID" type="xs:ID" use="required"/>
<xs:anyAttribute namespace="##other" processContents="lax"/> <xs:anyAttribute namespace="##other" processContents="lax"/>
</xs:complexType> </xs:complexType>
</xs:schema> </xs:schema>
]]> ]]></sourcecode>
</artwork> <t>
</figure> The following sections describe the XML schema in more detail. As a general
<t>
Following sections describe the XML schema in more detail. As a general
remark, please notice that optional elements that don't define what remark, please notice that optional elements that don't define what
their absence means are intended to be associated with undefined their absence means are intended to be associated with undefined
properties. properties.
</t> </t>
</section><!-- XML schema --> </section>
<section title="&lt;mediaCaptures&gt;" anchor="sec-media-captures"> <section anchor="sec-media-captures" numbered="true" toc="default">
<t> <name>&lt;mediaCaptures&gt;</name>
<t>
&lt;mediaCaptures&gt; represents the list of one or more media &lt;mediaCaptures&gt; represents the list of one or more media
captures available at the Media Provider's side. captures available at the Media Provider's side.
Each media capture is represented by a &lt;mediaCapture&gt; Each media capture is represented by a &lt;mediaCapture&gt;
element (<xref target="sec-media-capture"/>). element (<xref target="sec-media-capture" format="default"/>).
</t> </t>
</section> </section>
<section anchor="sec-encoding-groups" numbered="true" toc="default">
<section title="&lt;encodingGroups&gt;" anchor="sec-encoding-groups"> <name>&lt;encodingGroups&gt;</name>
<t> <t>
&lt;encodingGroups&gt; represents the list of &lt;encodingGroups&gt; represents the list of
the encoding groups organized on the Media Provider's side. the encoding groups organized on the Media Provider's side.
Each encoding group is represented by an Each encoding group is represented by an
&lt;encodingGroup&gt; element &lt;encodingGroup&gt; element (<xref target="sec-encoding-group" format="default
(<xref target="sec-encoding-group"/>). "/>).
</t> </t>
</section> </section>
<section anchor="sec-capture-scenes" numbered="true" toc="default">
<section title="&lt;captureScenes&gt;" anchor="sec-capture-scenes"> <name>&lt;captureScenes&gt;</name>
<t> <t>
&lt;captureScenes&gt; represents the list of &lt;captureScenes&gt; represents the list of
the capture scenes organized on the Media Provider's side. the capture scenes organized on the Media Provider's side.
Each capture scene is represented by a Each capture scene is represented by a
&lt;captureScene&gt; element. &lt;captureScene&gt; element (<xref target="sec-capture-scene" format="default"/
(<xref target="sec-capture-scene"/>). >).
</t> </t>
</section> </section>
<section anchor="sec-simultaneous-sets" numbered="true" toc="default">
<section title="&lt;simultaneousSets&gt;" <name>&lt;simultaneousSets&gt;</name>
anchor="sec-simultaneous-sets"> <t>
<t>
&lt;simultaneousSets&gt; contains the simultaneous &lt;simultaneousSets&gt; contains the simultaneous
sets indicated by the Media Provider. sets indicated by the Media Provider.
Each simultaneous set is represented by a Each simultaneous set is represented by a
&lt;simultaneousSet&gt; element. &lt;simultaneousSet&gt; element (<xref target="sec-simultaneous-set" format="def
(<xref target="sec-simultaneous-set"/>). ault"/>).
</t> </t>
</section> </section>
<section anchor="sec-global-views" numbered="true" toc="default">
<section title="&lt;globalViews&gt;" anchor="sec-global-views"> <name>&lt;globalViews&gt;</name>
<t> <t>
&lt;globalViews&gt; contains a set of alternative representations of &lt;globalViews&gt; contains a set of alternative representations of
all the scenes that are offered by a Media Provider to a Media Consumer. all the scenes that are offered by a Media Provider to a Media Consumer.
Each alternative is named "global view" and it is represented by a Each alternative is named "global view", and it is represented by a
&lt;globalView&gt; element. &lt;globalView&gt; element (<xref target="sec-global-view" format="default"/>).
(<xref target="sec-global-view"/>).
</t> </t>
</section> </section>
<section anchor="sec-capture-encodings" numbered="true" toc="default">
<section title="&lt;captureEncodings&gt;" <name>&lt;captureEncodings&gt;</name>
anchor="sec-capture-encodings"> <t>
<t>
&lt;captureEncodings&gt; is a list of capture &lt;captureEncodings&gt; is a list of capture
encodings. encodings.
It can represent the list of the desired It can represent the list of the desired
capture encodings indicated by the Media Consumer capture encodings indicated by the Media Consumer
or the list of instantiated captures on the or the list of instantiated captures on the
provider's side. provider's side.
Each capture encoding is represented by a Each capture encoding is represented by a
&lt;captureEncoding&gt; element. &lt;captureEncoding&gt; element (<xref target="sec-capture-encoding" format="def
(<xref target="sec-capture-encoding"/>). ault"/>).
</t> </t>
</section> </section>
<section anchor="sec-media-capture" numbered="true" toc="default">
<section title="&lt;mediaCapture&gt;" anchor="sec-media-capture"> <name>&lt;mediaCapture&gt;</name>
<t> <t>
A Media Capture is the A Media Capture is the
fundamental representation of a media flow fundamental representation of a media flow
that is available on the provider's side. that is available on the provider's side.
Media captures are characterized (i) by a set of features Media captures are characterized by (i) a set of features
that are independent from the specific type of medium, that are independent from the specific type of medium
and (ii) by a set of features that are media-specific. and (ii) a set of features that are media specific.
The features that are common to all media types appear within The features that are common to all media types appear within
the media capture type, that has been designed as an abstract complex the media capture type, which has been designed as an abstract
type. complex type.
Media-specific captures, such as video captures, Media-specific captures, such as video captures,
audio captures and others, are specializations of that abstract audio captures, and others, are specializations of that abstract
media capture type, as in a typical generalization-specialization media capture type, as in a typical generalization-specialization
hierarchy. hierarchy.
</t> </t>
<t>The following is the XML Schema definition of the <t>The following is the XML Schema definition of the
media capture type: media capture type:
</t> </t>
<t> <sourcecode type="xml"><![CDATA[
<figure>
<artwork>
<![CDATA[
<!-- MEDIA CAPTURE TYPE --> <!-- MEDIA CAPTURE TYPE -->
<xs:complexType name="mediaCaptureType" abstract="true"> <xs:complexType name="mediaCaptureType" abstract="true">
<xs:sequence> <xs:sequence>
<!-- mandatory fields --> <!-- mandatory fields -->
<xs:element name="captureSceneIDREF" type="xs:IDREF"/> <xs:element name="captureSceneIDREF" type="xs:IDREF"/>
<xs:choice> <xs:choice>
<xs:sequence> <xs:sequence>
<xs:element name="spatialInformation" <xs:element name="spatialInformation"
type="tns:spatialInformationType"/> type="tns:spatialInformationType"/>
</xs:sequence> </xs:sequence>
<xs:element name="nonSpatiallyDefinable" type="xs:boolean" <xs:element name="nonSpatiallyDefinable" type="xs:boolean"
fixed="true"/> fixed="true"/>
</xs:choice> </xs:choice>
<!-- for handling multi-content captures: --> <!-- for handling multicontent captures: -->
<xs:choice> <xs:choice>
<xs:sequence> <xs:sequence>
<xs:element name="synchronizationID" type="xs:ID" <xs:element name="synchronizationID" type="xs:ID"
minOccurs="0"/> minOccurs="0"/>
<xs:element name="content" type="contentType" minOccurs="0"/> <xs:element name="content" type="contentType" minOccurs="0"/>
<xs:element name="policy" type="policyType" minOccurs="0"/> <xs:element name="policy" type="policyType" minOccurs="0"/>
<xs:element name="maxCaptures" type="maxCapturesType" <xs:element name="maxCaptures" type="maxCapturesType"
minOccurs="0"/> minOccurs="0"/>
<xs:element name="allowSubsetChoice" type="xs:boolean" <xs:element name="allowSubsetChoice" type="xs:boolean"
minOccurs="0"/> minOccurs="0"/>
</xs:sequence> </xs:sequence>
<xs:element name="individual" type="xs:boolean" fixed="true"/> <xs:element name="individual" type="xs:boolean" fixed="true"/>
</xs:choice> </xs:choice>
<!-- optional fields --> <!-- optional fields -->
<xs:element name="encGroupIDREF" type="xs:IDREF" minOccurs="0"/> <xs:element name="encGroupIDREF" type="xs:IDREF" minOccurs="0"/>
<xs:element ref="description" minOccurs="0" maxOccurs="unbounded"/> <xs:element ref="description" minOccurs="0"
maxOccurs="unbounded"/>
<xs:element name="priority" type="xs:unsignedInt" minOccurs="0"/> <xs:element name="priority" type="xs:unsignedInt" minOccurs="0"/>
<xs:element name="lang" type="xs:language" minOccurs="0" <xs:element name="lang" type="xs:language" minOccurs="0"
maxOccurs="unbounded"/> maxOccurs="unbounded"/>
<xs:element name="mobility" type="mobilityType" minOccurs="0" /> <xs:element name="mobility" type="mobilityType" minOccurs="0" />
<xs:element ref="presentation" minOccurs="0" /> <xs:element ref="presentation" minOccurs="0" />
<xs:element ref="embeddedText" minOccurs="0" /> <xs:element ref="embeddedText" minOccurs="0" />
<xs:element ref="view" minOccurs="0" /> <xs:element ref="view" minOccurs="0" />
<xs:element name="capturedPeople" type="capturedPeopleType" <xs:element name="capturedPeople" type="capturedPeopleType"
minOccurs="0"/> minOccurs="0"/>
<xs:element name="relatedTo" type="xs:IDREF" minOccurs="0"/> <xs:element name="relatedTo" type="xs:IDREF" minOccurs="0"/>
</xs:sequence> </xs:sequence>
<xs:attribute name="captureID" type="xs:ID" use="required"/> <xs:attribute name="captureID" type="xs:ID" use="required"/>
<xs:attribute name="mediaType" type="xs:string" use="required"/> <xs:attribute name="mediaType" type="xs:string" use="required"/>
</xs:complexType> </xs:complexType>
]]> ]]></sourcecode>
</artwork> <section anchor="sec-captureID" numbered="true" toc="default">
</figure> <name>captureID Attribute</name>
</t> <t>The "captureID" attribute is a mandatory field
<section title="captureID attribute" anchor="sec-captureID">
<t>The "captureID" attribute is a mandatory field
containing the identifier of the media capture. containing the identifier of the media capture.
Such an identifier serves as the way the capture is referenced from Such an identifier serves as the way the capture is referenced from
other data model elements (e.g., simultaneous sets, capture encodings, other data model elements (e.g., simultaneous sets, capture encodings,
and others via &lt;mediaCaptureIDREF&gt;). and others via &lt;mediaCaptureIDREF&gt;).
</t> </t>
</section> </section>
<section numbered="true" toc="default">
<section title="mediaType attribute"> <name>mediaType Attribute</name>
<t>The "mediaType" attribute is a mandatory attribute specifying <t>The "mediaType" attribute is a mandatory attribute specifying
the media type of the capture. the media type of the capture.
Common standard values are "audio", "video", "text", as defined in Common standard values are "audio", "video", and "text", as defined in
<xref target="RFC6838"/>. <xref target="RFC6838" format="default"/>.
Other values can be provided. It is assumed that implementations agree Other values can be provided. It is assumed that implementations agree
on the interpretation of those other values. on the interpretation of those other values.
The "mediaType" attribute is as generic as possible. Here is why: (i) The "mediaType" attribute is as generic as possible. Here is why: (i)
the basic media capture type is an abstract one; (ii) "concrete" the basic media capture type is an abstract one; (ii) "concrete"
definitions for the standard (<xref target="RFC6838"/>) audio, video definitions for the standard audio, video,
and text capture types have been specified; (iii) a generic and text capture types <xref target="RFC6838" format="default"/> have been speci
"otherCaptureType" type has been defined; (iv) the "mediaType" fied; (iii) a generic
"otherCaptureType" type has been defined; and (iv) the "mediaType"
attribute has been generically defined as a string, with no particular attribute has been generically defined as a string, with no particular
template. template.
From the considerations above, it is clear that if one chooses to rely From the considerations above, it is clear that if one chooses to rely
on a brand new media type and wants to interoperate with others, an on a brand new media type and wants to interoperate with others, an
application-level agreement is needed on how to interpret such application-level agreement is needed on how to interpret such
information. information.
</t> </t>
</section> </section>
<section numbered="true" toc="default">
<section title="&lt;captureSceneIDREF&gt;"> <name>&lt;captureSceneIDREF&gt;</name>
<t>&lt;captureSceneIDREF&gt; is a mandatory field <t>&lt;captureSceneIDREF&gt; is a mandatory field
containing the value of the identifier of the capture scene containing the value of the identifier of the capture scene
the media capture is defined in, i.e., the value of the the media capture is defined in, i.e., the value of the
<xref target="sec-sceneID">sceneID</xref> attribute sceneID attribute (<xref target="sec-sceneID" format="default"/>) of
of that capture scene. that capture scene.
Indeed, each media capture MUST be defined within Indeed, each media capture <bcp14>MUST</bcp14> be defined within
one and only one capture scene. one and only one capture scene.
When a media capture is spatially definable, some spatial When a media capture is spatially definable, some spatial
information is provided along with it in the form information is provided along with it in the form
of point coordinates (see <xref target="sec-spatial-info"/>). of point coordinates (see <xref target="sec-spatial-info" format="default"/>).
Such coordinates refer to the space of coordinates defined Such coordinates refer to the space of coordinates defined
for the capture scene containing the capture. for the capture scene containing the capture.
</t> </t>
</section> </section>
<section numbered="true" toc="default">
<section title="&lt;encGroupIDREF&gt;"> <name>&lt;encGroupIDREF&gt;</name>
<t>&lt;encGroupIDREF&gt; is an optional field <t>&lt;encGroupIDREF&gt; is an optional field
containing the identifier of the encoding group containing the identifier of the encoding group
the media capture is associated with, i.e., the value of the the media capture is associated with, i.e., the value of the
<xref target="sec-encodingGroupID">encodingGroupID</xref> encodingGroupID
attribute of that encoding group. attribute (<xref target="sec-encodingGroupID" format="default"/>) of that encodi
Media captures that are not associated with any encoding group can not ng group.
Media captures that are not associated with any encoding group cannot
be instantiated as media streams. be instantiated as media streams.
</t> </t>
</section> </section>
<section anchor="sec-spatial-info" numbered="true" toc="default">
<section title="&lt;spatialInformation&gt;" <name>&lt;spatialInformation&gt;</name>
anchor="sec-spatial-info"> <t>Media captures are divided into two categories:
<t>Media captures are divided into two categories:
(i) non spatially definable captures and (i) non spatially definable captures and
(ii) spatially definable captures. (ii) spatially definable captures.
</t> </t>
<t>Captures are spatially definable when at least (i) it is possible to <t>Captures are spatially definable when at least it is possible to
provide the coordinates of the device position within the telepresence provide (i) the coordinates of the device position within the telepresence
room of origin (capture point) together with its capturing direction room of origin (capture point) together with its capturing direction
specified by a second point (point on line of capture), specified by a second point (point on line of capture)
or (ii) it is possible to provide the represented area within or (ii) the represented area within
the telepresence room, by listing the coordinates of the four co-planar the telepresence room, by listing the coordinates of the four coplanar
points identifying the plane of interest (area of capture). points identifying the plane of interest (area of capture).
The coordinates of the above mentioned points MUST be expressed The coordinates of the above mentioned points <bcp14>MUST</bcp14> be expressed
according to the coordinate space of the capture scene the media according to the coordinate space of the capture scene the media
captures belongs to. captures belong to.
</t> </t>
<t>Non spatially definable captures cannot be characterized <t>Non spatially definable captures cannot be characterized
within the physical space of the telepresence room of origin. within the physical space of the telepresence room of origin.
Captures of this kind are for example Captures of this kind are, for example,
those related to recordings, text captures, those related to recordings, text captures,
DVDs, registered presentations, DVDs, registered presentations,
or external streams or external streams
that are played in the telepresence room that are played in the telepresence room
and transmitted to remote sites. and transmitted to remote sites.
</t> </t>
<t> <t>
Spatially definable captures represent a Spatially definable captures represent a
part of the telepresence room. part of the telepresence room.
The captured part of the telepresence room is described The captured part of the telepresence room is described
by means of the &lt;spatialInformation&gt; element. by means of the &lt;spatialInformation&gt; element.
By comparing the &lt;spatialInformation&gt; element By comparing the &lt;spatialInformation&gt; element
of different media captures within of different media captures within
the same capture scene, the same capture scene,
a consumer can better determine the spatial a consumer can better determine the spatial
relationships between them and render them correctly. relationships between them and render them correctly.
Non spatially definable captures do not embed such element Non spatially definable captures do not embed such elements
in their XML description: in their XML description:
they are instead characterized by having the they are instead characterized by having the
&lt;nonSpatiallyDefinable&gt; tag set to "true" (see &lt;nonSpatiallyDefinable&gt; tag set to "true" (see
<xref target="sub-sec-nonspatiallydef"/>). <xref target="sub-sec-nonspatiallydef" format="default"/>).
</t> </t>
<t>The definition of the spatial information <t>The definition of the spatial information
type is the following:</t> type is the following:</t>
<t>
<figure> <sourcecode type="xml"><![CDATA[
<artwork>
<![CDATA[
<!-- SPATIAL INFORMATION TYPE --> <!-- SPATIAL INFORMATION TYPE -->
<xs:complexType name="spatialInformationType"> <xs:complexType name="spatialInformationType">
<xs:sequence> <xs:sequence>
<xs:element name="captureOrigin" type="captureOriginType" <xs:element name="captureOrigin" type="captureOriginType"
minOccurs="0"/> minOccurs="0"/>
<xs:element name="captureArea" type="captureAreaType" minOccurs="0"/> <xs:element name="captureArea" type="captureAreaType"
minOccurs="0"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" <xs:any namespace="##other" processContents="lax" minOccurs="0"
maxOccurs="unbounded"/> maxOccurs="unbounded"/>
</xs:sequence> </xs:sequence>
<xs:anyAttribute namespace="##other" processContents="lax"/> <xs:anyAttribute namespace="##other" processContents="lax"/>
</xs:complexType> </xs:complexType>
]]> ]]></sourcecode>
</artwork> <t>The &lt;captureOrigin&gt; contains the coordinates
</figure>
</t>
<t>The &lt;captureOrigin&gt; contains the coordinates
of the capture device that is taking the capture (i.e., the capture of the capture device that is taking the capture (i.e., the capture
point), as well as, optionally, the pointing direction (i.e., the point point) as well as, optionally, the pointing direction (i.e., the point
on line of capture) (see <xref target="sec-capture-origin"/>). on line of capture); see <xref target="sec-capture-origin" format="default"/>.
</t> </t>
<t> <t>
The &lt;captureArea&gt; is an optional field The &lt;captureArea&gt; is an optional field
containing four points defining containing four points defining
the captured area covered by the capture the captured area covered by the capture
(see <xref target="sec-capture-area"/>). (see <xref target="sec-capture-area" format="default"/>).
</t> </t>
<t>The scale of the points coordinates is specified in <t>The scale of the points coordinates is specified in
the <xref target="sec-scale">scale</xref> attribute of the capture scene the scale attribute (<xref target="sec-scale" format="default"/>) of the capture
scene
the media capture belongs to. the media capture belongs to.
Indeed, all the spatially definable media captures referring to Indeed, all the spatially definable media captures referring to
the same capture scene share the same coordinate system and express the same capture scene share the same coordinate system and express
their spatial information according to the same scale.</t> their spatial information according to the same scale.</t>
<section title="&lt;captureOrigin&gt;" <section anchor="sec-capture-origin" numbered="true" toc="default">
anchor="sec-capture-origin"> <name>&lt;captureOrigin&gt;</name>
<t> <t>
The &lt;captureOrigin&gt; element The &lt;captureOrigin&gt; element
is used to represent the position and optionally the line of is used to represent the position and optionally the line of
capture of a capture device. capture of a capture device.
&lt;captureOrigin&gt; MUST be included in spatially definable audio &lt;captureOrigin&gt; <bcp14>MUST</bcp14> be included in spatially definable aud io
captures, while it is optional for spatially definable video captures. captures, while it is optional for spatially definable video captures.
</t><t> </t>
<t>
The XML Schema definition of the &lt;captureOrigin&gt; The XML Schema definition of the &lt;captureOrigin&gt;
element type is the following: element type is the following:
</t> </t>
<t> <sourcecode type="xml"><![CDATA[
<figure>
<artwork>
<![CDATA[
<!-- CAPTURE ORIGIN TYPE --> <!-- CAPTURE ORIGIN TYPE -->
<xs:complexType name="captureOriginType"> <xs:complexType name="captureOriginType">
<xs:sequence> <xs:sequence>
<xs:element name="capturePoint" type="pointType"/> <xs:element name="capturePoint" type="pointType"/>
<xs:element name="lineOfCapturePoint" type="pointType" <xs:element name="lineOfCapturePoint" type="pointType"
minOccurs="0"/> minOccurs="0"/>
</xs:sequence> </xs:sequence>
<xs:anyAttribute namespace="##any" processContents="lax"/> <xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType> </xs:complexType>
<!-- POINT TYPE --> <!-- POINT TYPE -->
<xs:complexType name="pointType"> <xs:complexType name="pointType">
<xs:sequence> <xs:sequence>
<xs:element name="x" type="xs:decimal"/> <xs:element name="x" type="xs:decimal"/>
<xs:element name="y" type="xs:decimal"/> <xs:element name="y" type="xs:decimal"/>
<xs:element name="z" type="xs:decimal"/> <xs:element name="z" type="xs:decimal"/>
</xs:sequence> </xs:sequence>
</xs:complexType> </xs:complexType>
]]> ]]></sourcecode>
</artwork> <t>
</figure>
</t>
<t>
The point type contains three spatial coordinates The point type contains three spatial coordinates
(x,y,z) representing a point (x,y,z) representing a point
in the space associated in the space associated
with a certain capture scene. with a certain capture scene.
</t> </t>
<t> <t>
The &lt;captureOrigin&gt; element includes a The &lt;captureOrigin&gt; element includes a
mandatory &lt;capturePoint&gt; element and an optional mandatory &lt;capturePoint&gt; element and an optional
&lt;lineOfCapturePoint&gt; element, &lt;lineOfCapturePoint&gt; element,
both of the type "pointType". both of the type "pointType".
&lt;capturePoint&gt; specifies &lt;capturePoint&gt; specifies
the three coordinates identifying the position of the the three coordinates identifying the position of the
capture device. capture device.
&lt;lineOfCapturePoint&gt; is another pointType element representing &lt;lineOfCapturePoint&gt; is another pointType element representing
the "point on line of capture", that gives the pointing direction the "point on line of capture", which gives the pointing direction
of the capture device. of the capture device.
</t> </t>
<t> <t>
The coordinates of the point on line of capture The coordinates of the point on line of capture
MUST NOT be identical to the capture point coordinates. <bcp14>MUST NOT</bcp14> be identical to the capture point coordinates.
For a spatially definable video capture, if the point on line of capture For a spatially definable video capture, if the point on line of capture
is provided, it MUST belong to the region between is provided, it <bcp14>MUST</bcp14> belong to the region between
the point of capture and the capture area. the point of capture and the capture area.
For a spatially definable audio capture, For a spatially definable audio capture,
if the point on line of capture is not provided, if the point on line of capture is not provided,
the sensitivity pattern should be considered omnidirectional. the sensitivity pattern should be considered omnidirectional.
</t> </t>
</section> </section>
<section title="&lt;captureArea&gt;" <section anchor="sec-capture-area" numbered="true" toc="default">
anchor="sec-capture-area"> <name>&lt;captureArea&gt;</name>
<t> <t>
&lt;captureArea&gt; is an optional element &lt;captureArea&gt; is an optional element
that can be contained within the spatial information that can be contained within the spatial information
associated with a media capture. associated with a media capture.
It represents the spatial area captured by It represents the spatial area captured by
the media capture. the media capture.
&lt;captureArea&gt; MUST be included in the spatial information of &lt;captureArea&gt; <bcp14>MUST</bcp14> be included in the spatial information o
spatially definable video captures, while it MUST NOT be associated f
spatially definable video captures, while it <bcp14>MUST NOT</bcp14> be associat
ed
with audio captures. with audio captures.
</t> </t>
<t> <t>
The XML representation of that area is provided The XML representation of that area is provided
through a set of four point-type elements, through a set of four point-type elements,
&lt;bottomLeft&gt;, &lt;bottomRight&gt;, &lt;topLeft&gt;, &lt;bottomLeft&gt;, &lt;bottomRight&gt;, &lt;topLeft&gt;,
and &lt;topRight&gt; that MUST be co-planar. and &lt;topRight&gt;, that <bcp14>MUST</bcp14> be coplanar.
The four coplanar points are identified from The four coplanar points are identified from
the perspective of the capture device. the perspective of the capture device.
The XML schema definition is the following: The XML schema definition is the following:
</t> </t>
<t> <sourcecode type="xml"><![CDATA[
<figure>
<artwork>
<![CDATA[
<!-- CAPTURE AREA TYPE --> <!-- CAPTURE AREA TYPE -->
<xs:complexType name="captureAreaType"> <xs:complexType name="captureAreaType">
<xs:sequence> <xs:sequence>
<xs:element name="bottomLeft" type="pointType"/> <xs:element name="bottomLeft" type="pointType"/>
<xs:element name="bottomRight" type="pointType"/> <xs:element name="bottomRight" type="pointType"/>
<xs:element name="topLeft" type="pointType"/> <xs:element name="topLeft" type="pointType"/>
<xs:element name="topRight" type="pointType"/> <xs:element name="topRight" type="pointType"/>
</xs:sequence> </xs:sequence>
</xs:complexType> </xs:complexType>
]]> ]]></sourcecode>
</artwork> </section>
</figure> </section>
</t>
<t>
</t>
</section> <section anchor="sub-sec-nonspatiallydef" numbered="true" toc="default">
</section> <!-- spatial info section --> <name>&lt;nonSpatiallyDefinable&gt;</name>
<section title="&lt;nonSpatiallyDefinable&gt;" <t>When media captures are non spatially definable,
anchor="sub-sec-nonspatiallydef"> they <bcp14>MUST</bcp14> be marked with the boolean
<t>When media captures are non spatially definable,
they MUST be marked with the boolean
&lt;nonSpatiallyDefinable&gt; &lt;nonSpatiallyDefinable&gt;
element set to "true" and no &lt;spatialInformation&gt; MUST be element set to "true", and no &lt;spatialInformation&gt; <bcp14>MUST</bcp14> be
provided. provided.
Indeed, &lt;nonSpatiallyDefinable&gt; and &lt;spatialInformation&gt; Indeed, &lt;nonSpatiallyDefinable&gt; and &lt;spatialInformation&gt;
are mutually are mutually
exclusive tags, according to the &lt;choice&gt; section within the XML exclusive tags, according to the &lt;choice&gt; section within the XML
Schema definition of the media capture type. Schema definition of the media capture type.
</t> </t>
</section> </section>
<section title="&lt;content&gt;" anchor="sub-sec-content"> <section anchor="sub-sec-content" numbered="true" toc="default">
<t> <name>&lt;content&gt;</name>
<t>
A media capture can be (i) an individual media capture or (ii) A media capture can be (i) an individual media capture or (ii)
a multiple content capture (MCC). an MCC.
A multiple content capture is made by different captures An MCC is made by different captures
that can be arranged spatially that can be arranged spatially
(by a composition operation), or temporally (by a switching operation), (by a composition operation), or temporally (by a switching operation),
or that can result from or that can result from
the orchestration of both the techniques. the orchestration of both the techniques.
If a media capture is an MCC, then it MAY show in its XML If a media capture is an MCC, then it <bcp14>MAY</bcp14> show in its XML
data model representation the data model representation the
&lt;content&gt; element. It is composed by a list of media &lt;content&gt; element. It is composed by a list of media
capture identifiers ("mediaCaptureIDREF") and capture scene view capture identifiers ("mediaCaptureIDREF") and capture scene view
identifiers ("sceneViewIDREF"), identifiers ("sceneViewIDREF"),
where the latter ones are where the latter ones are
used as shortcuts to refer to multiple capture identifiers. The used as shortcuts to refer to multiple capture identifiers. The
referenced captures are used to create the MCC according to a certain referenced captures are used to create the MCC according to a certain
strategy. If the &lt;content&gt; element does not appear in a MCC, strategy. If the &lt;content&gt; element does not appear in an MCC,
or it has no child elements, then the MCC is assumed to be made or it has no child elements, then the MCC is assumed to be made
of multiple sources but no information regarding those sources is of multiple sources, but no information regarding those sources is
provided. provided.
</t> </t>
<figure>
<artwork>
<![CDATA[
<!-- Note: FYI, updated the following per the author's email on 10/3/18:
Changed "xs:IDREF" to "xs:string" in two places (in the CONTENT TYPE
schmema below)
-->
<sourcecode type="xml"><![CDATA[
<!-- CONTENT TYPE --> <!-- CONTENT TYPE -->
<xs:complexType name="contentType"> <xs:complexType name="contentType">
<xs:sequence> <xs:sequence>
<xs:element name="mediaCaptureIDREF" type="xs:IDREF" <xs:element name="mediaCaptureIDREF" type="xs:string"
minOccurs="0" maxOccurs="unbounded"/> minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="sceneViewIDREF" type="xs:IDREF" <xs:element name="sceneViewIDREF" type="xs:string"
minOccurs="0" maxOccurs="unbounded"/> minOccurs="0" maxOccurs="unbounded"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" <xs:any namespace="##other" processContents="lax" minOccurs="0"
maxOccurs="unbounded"/> maxOccurs="unbounded"/>
</xs:sequence> </xs:sequence>
<xs:anyAttribute namespace="##other" processContents="lax"/> <xs:anyAttribute namespace="##other" processContents="lax"/>
</xs:complexType> </xs:complexType>
]]></sourcecode>
]]> </section>
</artwork> <section numbered="true" toc="default">
</figure> <name>&lt;synchronizationID&gt;</name>
</section> <t>&lt;synchronizationID&gt; is an optional element for multiple
<section title="&lt;synchronizationID&gt;">
<t>&lt;synchronizationID&gt; is an optional element for multiple
content captures that content captures that
contains a numeric identifier. contains a numeric identifier.
Multiple content captures marked with the same identifier in the Multiple content captures marked with the same identifier in the
&lt;synchronizationID&gt; &lt;synchronizationID&gt;
contain at all times captures coming from the same sources. It is contain at all times captures coming from the same sources. It is
the Media Provider that determines what the source for the captures the Media Provider that determines what the source is for the captures.
is.
In this way, the Media Provider can choose how to group together In this way, the Media Provider can choose how to group together
single captures for the purpose of keeping them synchronized single captures for the purpose of keeping them synchronized
according to the &lt;synchronizationID&gt; element. according to the &lt;synchronizationID&gt; element.
</t> </t>
</section> </section>
<section numbered="true" toc="default">
<section title="&lt;allowSubsetChoice&gt;"> <name>&lt;allowSubsetChoice&gt;</name>
<t>&lt;allowSubsetChoice&gt; is an optional boolean element for <t>&lt;allowSubsetChoice&gt; is an optional boolean element for
multiple content captures. multiple content captures.
It indicates whether or not the Provider allows the Consumer to It indicates whether or not the Provider allows the Consumer to
choose a specific subset of the captures referenced by the MCC. choose a specific subset of the captures referenced by the MCC.
If this attribute is true, and the MCC references other captures, If this attribute is true, and the MCC references other captures,
then the Consumer MAY specify in a CONFIGURE message a specific then the Consumer <bcp14>MAY</bcp14> specify in a CONFIGURE message a specifi c
subset of those captures to be included in the MCC, and the subset of those captures to be included in the MCC, and the
Provider MUST then include only that subset. If this attribute is Provider <bcp14>MUST</bcp14> then include only that subset. If this attribut e is
false, or the MCC does not reference other captures, then the false, or the MCC does not reference other captures, then the
Consumer MUST NOT select a subset. If &lt;allowSubsetChoice&gt; Consumer <bcp14>MUST NOT</bcp14> select a subset. If &lt;allowSubsetChoice&gt ;
is not shown in the XML description of the is not shown in the XML description of the
MCC, its value is to be considered "false". MCC, its value is to be considered "false".
</t> </t>
</section> </section>
<section numbered="true" toc="default">
<section title="&lt;policy&gt;"> <name>&lt;policy&gt;</name>
<t> <t>
&lt;policy&gt; is an optional element &lt;policy&gt; is an optional element
that can be used only for multiple content captures. that can be used only for multiple content captures.
It indicates the criteria applied to build the multiple content capture It indicates the criteria applied to build the multiple content capture
using the media captures referenced in the &lt;mediaCaptureIDREF&gt; using the media captures referenced in the &lt;mediaCaptureIDREF&gt;
list. list.
The &lt;policy&gt; value is in the form of a token that indicates the The &lt;policy&gt; value is in the form of a token that indicates the
policy and an index representing an instance of the policy, separated policy and an index representing an instance of the policy, separated
by a ":" (e.g., SoundLevel:2, RoundRobin:0, etc.). by a ":" (e.g., SoundLevel:2, RoundRobin:0, etc.).
The XML schema defining the type of the &lt;policy&gt; element The XML schema defining the type of the &lt;policy&gt; element
is the following: is the following:
</t> </t>
<figure> <sourcecode type="xml"><![CDATA[
<artwork>
<![CDATA[
<!-- POLICY TYPE --> <!-- POLICY TYPE -->
<xs:simpleType name="policyType"> <xs:simpleType name="policyType">
<xs:restriction base="xs:string"> <xs:restriction base="xs:string">
<xs:pattern value="([a-zA-Z0-9])+[:]([0-9])+"/> <xs:pattern value="([a-zA-Z0-9])+[:]([0-9])+"/>
</xs:restriction> </xs:restriction>
</xs:simpleType> </xs:simpleType>
]]> ]]></sourcecode>
</artwork>
</figure> <!--[rfced] Would you like to update this text to exactly
<t>At the time of writing, only two switching policies are defined in match RFC-to-be 8845? Also, may the lead-in sentence
<xref target="I-D.ietf-clue-framework"/>:</t> be updated to be more precise?
<list>
<t>SoundLevel: the content of the MCC is Current:
At the time of writing, only two switching policies are defined in
[RFC8845]:
SoundLevel: the content of the MCC is determined by a sound level
detection algorithm. The loudest (active) speaker (or a
previous speaker, depending on the index value) is contained in
the MCC. Index 0 represents the most current instance of the
policy, i.e., the currently active speaker, 1 represents the
previous instance, i.e., the previous active speaker, and so
on.
RoundRobin: the content of the MCC is determined by a time-based
algorithm.
Perhaps (to match 8845):
At the time of writing, only two switching policies are defined;
there are in [RFC8845] as follows:
SoundLevel: This indicates that the content of the MCC is determined
by a sound-level-detection algorithm. The loudest (active)
speaker (or a previous speaker, depending on the index value) is
contained in the MCC.
RoundRobin: This indicates that the content of the MCC is determined
by a time-based algorithm. For example, the Provider provides
content from a particular source for a period of time and then
provides content from another source, and so on.
-->
<t>At the time of writing, only two switching policies are defined in
<xref target="RFC8845" format="default"/>:</t>
<blockquote>
<dl newline="false" spacing="normal">
<dt>SoundLevel:</dt><dd>the content of the MCC is
determined by a sound level detection algorithm. The loudest determined by a sound level detection algorithm. The loudest
(active) speaker (or a previous speaker, depending on the index (active) speaker (or a previous speaker, depending on the index
value) is contained in the MCC. Index 0 represents the most current value) is contained in the MCC. Index 0 represents the most current
instance of the policy, i.e., the currently active speaker, instance of the policy, i.e., the currently active speaker,
1 represents the previous instance, i.e., the 1 represents the previous instance, i.e., the
previous active speaker, and so on. previous active speaker, and so on.
</t> </dd>
<t>RoundRobin: the content of the MCC is <dt>RoundRobin:</dt><dd>the content of the MCC is
determined by a time based algorithm.</t> determined by a time-based algorithm.</dd>
</list> </dl>
<t>Other values for the &lt;policy&gt; element can be used. </blockquote>
<t>Other values for the &lt;policy&gt; element can be used.
In this case, it is assumed that implementations agree on the In this case, it is assumed that implementations agree on the
meaning of those other values and/or those new switching policies meaning of those other values and/or those new switching policies
are defined in later documents.</t> are defined in later documents.</t>
</section> </section>
<section anchor="sub-sec-maxCaptures" numbered="true" toc="default">
<section title="&lt;maxCaptures&gt;" anchor="sub-sec-maxCaptures"> <name>&lt;maxCaptures&gt;</name>
<t> <t>
&lt;maxCaptures&gt; is an optional element &lt;maxCaptures&gt; is an optional element
that can be used only for multiple content captures (MCC). that can be used only for MCCs.
It provides information about the number of media captures It provides information about the number of media captures
that can be represented that can be represented
in the multiple content capture at a time. in the multiple content capture at a time.
If &lt;maxCaptures&gt; is not provided, all the media captures listed If &lt;maxCaptures&gt; is not provided, all the media captures listed
in the &lt;content&gt; element can appear at a time in the capture in the &lt;content&gt; element can appear at a time in the capture
encoding. The type definition is provided below. encoding. The type definition is provided below.
</t> </t>
<t> <sourcecode type="xml"><![CDATA[
<figure>
<artwork>
<![CDATA[
<!-- MAX CAPTURES TYPE --> <!-- MAX CAPTURES TYPE -->
<xs:simpleType name="positiveShort"> <xs:simpleType name="positiveShort">
<xs:restriction base="xs:unsignedShort"> <xs:restriction base="xs:unsignedShort">
<xs:minInclusive value="1"> <xs:minInclusive value="1">
</xs:minInclusive> </xs:minInclusive>
</xs:restriction> </xs:restriction>
</xs:simpleType> </xs:simpleType>
<xs:complexType name="maxCapturesType"> <xs:complexType name="maxCapturesType">
<xs:simpleContent> <xs:simpleContent>
<xs:extension base="positiveShort"> <xs:extension base="positiveShort">
<xs:attribute name="exactNumber" <xs:attribute name="exactNumber"
type="xs:boolean"/> type="xs:boolean"/>
</xs:extension> </xs:extension>
</xs:simpleContent> </xs:simpleContent>
</xs:complexType> </xs:complexType>
]]> ]]></sourcecode>
</artwork> <t>When the "exactNumber" attribute is set to "true", it means
</figure>
</t>
<t>When the "exactNumber" attribute is set to "true", it means
the &lt;maxCaptures&gt; element carries the exact number of the the &lt;maxCaptures&gt; element carries the exact number of the
media captures appearing at a time. media captures appearing at a time.
Otherwise, the number of the represented media captures MUST be Otherwise, the number of the represented media captures <bcp14>MUST</bcp14> be
considered "&lt;=" the &lt;maxCaptures&gt; value. considered "&lt;=" the &lt;maxCaptures&gt; value.
</t> </t>
<t> <t>
For instance, an audio MCC having the &lt;maxCaptures&gt; value set to 1 For instance, an audio MCC having the &lt;maxCaptures&gt; value set to 1
means that a media stream from the MCC will only contain means that a media stream from the MCC will only contain
audio from a single one of its constituent captures at a time. audio from a single one of its constituent captures at a time.
On the other hand, if the &lt;maxCaptures&gt; value is set to On the other hand, if the &lt;maxCaptures&gt; value is set to
4 and the exactNumber 4 and the exactNumber
attribute is set to "true", it would mean that the media stream attribute is set to "true", it would mean that the media stream
received from the MCC will always contain a mix of audio received from the MCC will always contain a mix of audio
from exactly four of its constituent captures. from exactly four of its constituent captures.
</t> </t>
</section> </section>
<section title="&lt;individual&gt;"> <section numbered="true" toc="default">
<t> <name>&lt;individual&gt;</name>
<t>
&lt;individual&gt; is a boolean element &lt;individual&gt; is a boolean element
that MUST be used for single-content captures. that <bcp14>MUST</bcp14> be used for single-content captures.
Its value is fixed and set to "true". Its value is fixed and set to "true".
Such element indicates the capture that is being described is not Such element indicates the capture that is being described is not
a multiple content capture. an MCC.
Indeed, &lt;individual&gt; and the aforementioned Indeed, &lt;individual&gt; and the aforementioned
tags related to MCC attributes tags related to MCC attributes
(from <xref target="sub-sec-content"/> to (from Sections <xref target="sub-sec-content" format="counter"/> to
<xref target="sub-sec-maxCaptures"/>) are mutually <xref target="sub-sec-maxCaptures" format="counter"/>) are mutually
exclusive, according to the &lt;choice&gt; section within the XML Schema exclusive, according to the &lt;choice&gt; section within the XML Schema
definition of the media capture type. definition of the media capture type.
</t> </t>
</section> </section>
<section title="&lt;description&gt;" <section anchor="sec-description" numbered="true" toc="default">
anchor="sec-description"> <name>&lt;description&gt;</name>
<t> <t>
<!--[rfced] Please clarify "to the aim of providing" in the
following. Could we perhaps replace it with "to provide"?
Original:
<description> is used to provide human-readable textual information.
This element is included in the XML definition of media captures,
capture scenes and capture scene views to the aim of providing human-
readable description of, respectively, media captures, capture scenes
and capture scene views.
Perhaps:
<description> is used to provide human-readable textual information.
This element is included in the XML definition of media captures,
capture scenes, and capture scene views to provide human-
readable descriptions of, respectively, media captures, capture scenes
and capture scene views.
-->
&lt;description&gt; is used to provide human-readable &lt;description&gt; is used to provide human-readable
textual information. textual information.
This element is included in the XML definition of media captures, This element is included in the XML definition of media captures,
capture scenes and capture scene views to the aim of providing capture scenes, and capture scene views to the aim of providing
human-readable description of, respectively, human-readable descriptions of, respectively,
media captures, capture scenes and capture scene views. media captures, capture scenes, and capture scene views.
According to the data model definition of a media capture According to the data model definition of a media capture
(<xref target="sec-media-capture"/>)), zero or more (<xref target="sec-media-capture" format="default"/>)), zero or more
&lt;description&gt; elements can be used, each &lt;description&gt; elements can be used, each
providing information in a different providing information in a different
language. language.
The &lt;description&gt; element definition is the following: The &lt;description&gt; element definition is the following:
</t> </t>
<t> <sourcecode type="xml"><![CDATA[
<figure>
<artwork>
<![CDATA[
<!-- DESCRIPTION element --> <!-- DESCRIPTION element -->
<xs:element name="description"> <xs:element name="description">
<xs:complexType> <xs:complexType>
<xs:simpleContent> <xs:simpleContent>
<xs:extension base="xs:string"> <xs:extension base="xs:string">
<xs:attribute name="lang" type="xs:language"/> <xs:attribute name="lang" type="xs:language"/>
</xs:extension> </xs:extension>
</xs:simpleContent> </xs:simpleContent>
</xs:complexType> </xs:complexType>
</xs:element> </xs:element>
]]> ]]></sourcecode>
</artwork> <t>As can be seen, &lt;description&gt; is a
</figure>
</t>
<t>As can be seen, &lt;description&gt; is a
string element with an attribute ("lang") indicating string element with an attribute ("lang") indicating
the language used in the textual description. Such an attribute is the language used in the textual description. Such an attribute is
compliant with the Language-Tag ABNF production compliant with the Language-Tag ABNF production
from <xref target="RFC5646"/>. from <xref target="RFC5646" format="default"/>.
</t> </t>
</section> </section>
<section title="&lt;priority&gt;"> <section numbered="true" toc="default">
<t> <name>&lt;priority&gt;</name>
<t>
&lt;priority&gt; &lt;priority&gt;
is an optional unsigned integer field is an optional unsigned integer field
indicating the importance of a media capture indicating the importance of a media capture
according to the Media Provider's perspective. according to the Media Provider's perspective.
It can be used on the receiver's side to It can be used on the receiver's side to
automatically identify automatically identify
the most relevant contribution from the most relevant contribution from
the Media Provider. the Media Provider.
The higher the importance, the lower the contained value. The higher the importance, the lower the contained value.
If no priority If no priority
is assigned, no assumptions regarding relative importance of the is assigned, no assumptions regarding relative importance of the
media capture can be assumed.</t> media capture can be assumed.</t>
</section> </section>
<section title="&lt;lang&gt;"> <section numbered="true" toc="default">
<t> <name>&lt;lang&gt;</name>
<t>
&lt;lang&gt; is an optional element &lt;lang&gt; is an optional element
containing the language used in the capture. containing the language used in the capture.
Zero or more &lt;lang&gt; elements can appear in the XML description of Zero or more &lt;lang&gt; elements can appear in the XML description of
a media capture. Each such element has to be compliant with the a media capture. Each such element has to be compliant with the
Language-Tag ABNF production from <xref target="RFC5646"/>. Language-Tag ABNF production from <xref target="RFC5646" format="default"/>.
</t> </t>
</section> </section>
<section numbered="true" toc="default">
<section title="&lt;mobility&gt;"> <name>&lt;mobility&gt;</name>
<t> <t>
&lt;mobility&gt; is an optional element &lt;mobility&gt; is an optional element
indicating whether or not the capture device originating indicating whether or not the capture device originating
the capture may move during the telepresence session. the capture may move during the telepresence session.
That optional element can assume one of the three following values: That optional element can assume one of the three following values:
<list style="hanging">
<t hangText="static">SHOULD NOT change for the
duration of the CLUE session, across multiple ADVERTISEMENT messages.
</t> </t>
<t hangText="dynamic"> <ul empty="true"><li>
MAY change in each new ADVERTISEMENT message. <dl newline="false" spacing="normal">
<dt>static:</dt>
<dd><bcp14>SHOULD NOT</bcp14> change for the
duration of the CLUE session, across multiple ADVERTISEMENT messages.</dd>
<dt>dynamic:</dt>
<dd>
<bcp14>MAY</bcp14> change in each new ADVERTISEMENT message.
Can be assumed to remain unchanged until there is a Can be assumed to remain unchanged until there is a
new ADVERTISEMENT message.</t> new ADVERTISEMENT message.</dd>
<t hangText="highly-dynamic"> <dt>highly-dynamic:</dt>
MAY change dynamically, even between consecutive ADVERTISEMENT messages. <dd>
<bcp14>MAY</bcp14> change dynamically, even between consecutive ADVERTISEMENT me
ssages.
The spatial information provided in an ADVERTISEMENT message is simply a The spatial information provided in an ADVERTISEMENT message is simply a
snapshot of the current values at the time when the message is sent.</t> snapshot of the current values at the time when the message is sent.</dd>
</list> </dl></li>
</t> </ul>
</section> </section>
<section numbered="true" toc="default">
<section title="&lt;relatedTo&gt;"> <name>&lt;relatedTo&gt;</name>
<t> <t>
The optional &lt;relatedTo&gt; element contains the The optional &lt;relatedTo&gt; element contains the
value of the <xref target="sec-captureID">captureID attribute</xref> value of the <xref target="sec-captureID" format="default">captureID attribute</ xref>
of the media capture to which the considered of the media capture to which the considered
media capture refers. media capture refers.
The media capture marked with a &lt;relatedTo&gt; The media capture marked with a &lt;relatedTo&gt;
element can be for example the translation of the referred element can be, for example, the translation of the referred
media capture in a different language. media capture in a different language.
</t> </t>
</section> </section>
<section anchor="sec-view" numbered="true" toc="default">
<section title="&lt;view&gt;" anchor="sec-view"> <name>&lt;view&gt;</name>
<t>The &lt;view&gt; element is an optional tag describing what is <t>The &lt;view&gt; element is an optional tag describing what is
represented in the spatial area covered by a media capture. represented in the spatial area covered by a media capture.
It has been specified as a simple string with an annotation pointing to It has been specified as a simple string with an annotation pointing to
an ad hoc defined IANA registry: an IANA registry that is defined ad hoc:
</t> </t>
<sourcecode type="xml"><![CDATA[
<figure>
<artwork>
<![CDATA[
<!-- VIEW ELEMENT --> <!-- VIEW ELEMENT -->
<xs:element name="view" type="xs:string"> <xs:element name="view" type="xs:string">
<xs:annotation> <xs:annotation>
<xs:documentation> <xs:documentation>
Acceptable values (enumerations) for this type are managed Acceptable values (enumerations) for this type are managed
by IANA in the "CLUE Schema <view> registry", by IANA in the "CLUE Schema <view> registry",
accessible at TBD-IANA. accessible at https://www.iana.org/assignments/clue.
</xs:documentation> </xs:documentation>
</xs:annotation> </xs:annotation>
</xs:element> </xs:element>
]]> ]]></sourcecode>
</artwork> <t>
</figure>
<t>
The current possible values, as per the CLUE framework document The current possible values, as per the CLUE framework document
<xref target="I-D.ietf-clue-framework"/>, are: "room", "table", <xref target="RFC8845" format="default"/>, are: "room", "table",
"lectern", "individual", and "audience". "lectern", "individual", and "audience".
</t> </t>
</section>
</section> <section anchor="sec-presentation" numbered="true" toc="default">
<name>&lt;presentation&gt;</name>
<section title="&lt;presentation&gt;" anchor="sec-presentation"> <t>The &lt;presentation&gt; element is an optional tag used for media
<t>The &lt;presentation&gt; element is an optional tag used for media
captures conveying information about presentations within the captures conveying information about presentations within the
telepresence session. It has been specified as a simple string with an telepresence session. It has been specified as a simple string with an
annotation pointing to an ad hoc defined IANA registry: annotation pointing to an IANA registry that is defined ad hoc:
</t> </t>
<sourcecode type="xml"><![CDATA[
<figure>
<artwork>
<![CDATA[
<!-- PRESENTATION ELEMENT --> <!-- PRESENTATION ELEMENT -->
<xs:element name="presentation" type="xs:string"> <xs:element name="presentation" type="xs:string">
<xs:annotation> <xs:annotation>
<xs:documentation> <xs:documentation>
Acceptable values (enumerations) for this type are managed Acceptable values (enumerations) for this type are managed
by IANA in the "CLUE Schema <presentation> registry", by IANA in the "CLUE Schema <presentation> registry",
accessible at TBD-IANA. accessible at https://www.iana.org/assignments/clue.
</xs:documentation> </xs:documentation>
</xs:annotation> </xs:annotation>
</xs:element> </xs:element>
]]> ]]></sourcecode>
</artwork> <t>
</figure>
<t>
The current possible values, as per the CLUE framework document The current possible values, as per the CLUE framework document
<xref target="I-D.ietf-clue-framework"/>, are "slides" and "images". <xref target="RFC8845" format="default"/>, are "slides" and "images".
</t> </t>
</section> </section>
<section anchor="sec-embedded-text" numbered="true" toc="default">
<section title="&lt;embeddedText&gt;" <name>&lt;embeddedText&gt;</name>
anchor="sec-embedded-text"> <t>
<t>
The &lt;embeddedText&gt; element is a boolean The &lt;embeddedText&gt; element is a boolean
element indicating that there is text embedded element indicating that there is text embedded
in the media capture (e.g., in a video capture). in the media capture (e.g., in a video capture).
The language used in such embedded textual description The language used in such an embedded textual description
is reported in &lt;embeddedText&gt; "lang" attribute. is reported in the &lt;embeddedText&gt; "lang" attribute.
</t> </t>
<t> <t>
The XML Schema definition of the &lt;embeddedText&gt; The XML Schema definition of the &lt;embeddedText&gt;
element is: element is:
</t> </t>
<t> <sourcecode type="xml"><![CDATA[
<figure>
<artwork>
<![CDATA[
<!-- EMBEDDED TEXT ELEMENT --> <!-- EMBEDDED TEXT ELEMENT -->
<xs:element name="embeddedText"> <xs:element name="embeddedText">
<xs:complexType> <xs:complexType>
<xs:simpleContent> <xs:simpleContent>
<xs:extension base="xs:boolean"> <xs:extension base="xs:boolean">
<xs:attribute name="lang" type="xs:language"/> <xs:attribute name="lang" type="xs:language"/>
</xs:extension> </xs:extension>
</xs:simpleContent> </xs:simpleContent>
</xs:complexType> </xs:complexType>
</xs:element> </xs:element>
]]> ]]></sourcecode>
</artwork> </section>
</figure> <section anchor="sec-participantIDs" numbered="true" toc="default">
</t> <name>&lt;capturedPeople&gt;</name>
<t>This optional element is used to indicate which
</section>
<section title="&lt;capturedPeople&gt;" anchor="sec-participantIDs">
<t>This optional element is used to indicate which
telepresence session participants telepresence session participants
are represented within the media captures. For each participant, a are represented in within the media captures. For each participant, a
&lt;personIDREF&gt; element is provided.</t> &lt;personIDREF&gt; element is provided.</t>
<section numbered="true" toc="default">
<section title="&lt;personIDREF&gt;"> <name>&lt;personIDREF&gt;</name>
<t> <t>
&lt;personIDREF&gt; contains the identifier of the represented person, &lt;personIDREF&gt; contains the identifier of the represented person,
i.e., the value of the related <xref target="sub-sec-participantID"> i.e., the value of the related <xref target="sub-sec-participantID" format="defa ult">
personID attribute</xref>. personID attribute</xref>.
Metadata about the represented participant can be retrieved by accessing Metadata about the represented participant can be retrieved by accessing
the &lt;people&gt; list (<xref target="sec-participants"/>). the &lt;people&gt; list (<xref target="sec-participants" format="default"/>).
</t> </t>
</section> </section>
</section> </section>
</section>
</section><!-- media capture section -->
<section title="Audio captures"> <section numbered="true" toc="default">
<t>Audio captures inherit all the features of a generic <name>Audio Captures</name>
<t>Audio captures inherit all the features of a generic
media capture and present further audio-specific media capture and present further audio-specific
characteristics. characteristics.
The XML Schema definition of the audio The XML Schema definition of the audio
capture type is reported below: capture type is reported below:
</t> </t>
<t> <sourcecode type="xml"><![CDATA[
<figure>
<artwork>
<![CDATA[
<!-- AUDIO CAPTURE TYPE --> <!-- AUDIO CAPTURE TYPE -->
<xs:complexType name="audioCaptureType"> <xs:complexType name="audioCaptureType">
<xs:complexContent> <xs:complexContent>
<xs:extension base="tns:mediaCaptureType"> <xs:extension base="tns:mediaCaptureType">
<xs:sequence> <xs:sequence>
<xs:element ref="sensitivityPattern" minOccurs="0" /> <xs:element ref="sensitivityPattern" minOccurs="0" />
<xs:any namespace="##other" processContents="lax" minOccurs="0" <xs:any namespace="##other" processContents="lax" minOccurs="0"
maxOccurs="unbounded"/> maxOccurs="unbounded"/>
</xs:sequence> </xs:sequence>
<xs:anyAttribute namespace="##other" processContents="lax"/> <xs:anyAttribute namespace="##other" processContents="lax"/>
</xs:extension> </xs:extension>
</xs:complexContent> </xs:complexContent>
</xs:complexType> </xs:complexType>
]]></sourcecode>
]]> <t>
</artwork>
</figure>
</t>
<t>
An example of audio-specific information An example of audio-specific information
that can be included is represented by the &lt;sensitivityPattern&gt; that can be included is represented by the &lt;sensitivityPattern&gt;
element. (<xref target="sec-sensitivity-pattern"/>). element (<xref target="sec-sensitivity-pattern" format="default"/>).
</t> </t>
<section anchor="sec-sensitivity-pattern" numbered="true" toc="default">
<section title="&lt;sensitivityPattern&gt;" <name>&lt;sensitivityPattern&gt;</name>
anchor="sec-sensitivity-pattern"> <t>
<t>
The &lt;sensitivityPattern&gt; element is an optional field The &lt;sensitivityPattern&gt; element is an optional field
describing the characteristics of the nominal sensitivity pattern of the describing the characteristics of the nominal sensitivity pattern of the
microphone capturing the audio signal. It has been specified as a simple microphone capturing the audio signal. It has been specified as a simple
string with an annotation pointing to an ad hoc defined IANA registry: string with an annotation pointing to an IANA registry that is defined ad hoc:
</t> </t>
<sourcecode type="xml"><![CDATA[
<t>
<figure>
<artwork>
<![CDATA[
<!-- SENSITIVITY PATTERN ELEMENT --> <!-- SENSITIVITY PATTERN ELEMENT -->
<xs:element name="sensitivityPattern" type="xs:string"> <xs:element name="sensitivityPattern" type="xs:string">
<xs:annotation> <xs:annotation>
<xs:documentation> <xs:documentation>
Acceptable values (enumerations) for this type are managed by IANA Acceptable values (enumerations) for this type are managed by IANA
in the "CLUE Schema <sensitivityPattern> registry", accessible in the "CLUE Schema <sensitivityPattern> registry", accessible
at TBD-IANA. at https://www.iana.org/assignments/clue.
</xs:documentation> </xs:documentation>
</xs:annotation> </xs:annotation>
</xs:element> </xs:element>
]]> ]]></sourcecode>
</artwork> <t>
</figure>
</t>
<t>
The current possible values, as per the CLUE framework document The current possible values, as per the CLUE framework document
<xref target="I-D.ietf-clue-framework"/>, are "uni", "shotgun", "omni", <xref target="RFC8845" format="default"/>, are "uni", "shotgun", "omni",
"figure8", "cardioid" and "hyper-cardioid". "figure8", "cardioid", and "hyper-cardioid".
</t> </t>
</section> </section>
</section><!-- audio capture --> </section>
<section title="Video captures"> <section numbered="true" toc="default">
<t>Video captures, similarly to audio captures, <name>Video Captures</name>
<t>Video captures, similarly to audio captures,
extend the information of a generic media capture extend the information of a generic media capture
with video-specific features.</t> with video-specific features.</t>
<t> <t>
The XML Schema representation of the The XML Schema representation of the
video capture type is provided in the following: video capture type is provided in the following:
</t> </t>
<t> <sourcecode type="xml"><![CDATA[
<figure>
<artwork>
<![CDATA[
<!-- VIDEO CAPTURE TYPE --> <!-- VIDEO CAPTURE TYPE -->
<xs:complexType name="videoCaptureType"> <xs:complexType name="videoCaptureType">
<xs:complexContent> <xs:complexContent>
<xs:extension base="tns:mediaCaptureType"> <xs:extension base="tns:mediaCaptureType">
<xs:sequence> <xs:sequence>
<xs:any namespace="##other" processContents="lax" minOccurs="0" <xs:any namespace="##other" processContents="lax" minOccurs="0"
maxOccurs="unbounded"/> maxOccurs="unbounded"/>
</xs:sequence> </xs:sequence>
<xs:anyAttribute namespace="##other" processContents="lax"/> <xs:anyAttribute namespace="##other" processContents="lax"/>
</xs:extension> </xs:extension>
</xs:complexContent> </xs:complexContent>
</xs:complexType> </xs:complexType>
]]> ]]></sourcecode>
</artwork> </section>
</figure>
</t>
</section><!-- video capture -->
<section title="Text captures"> <section numbered="true" toc="default">
<t>Also text captures can be described <name>Text Captures</name>
by extending the generic media capture information,
similarly to audio captures and video captures.</t> <t>Similar to audio captures and video captures, text captures can be desc
<t>There are no known properties of a text-based media which aren't ribed
by extending the generic media capture information.</t>
<t>There are no known properties of a text-based media that aren't
already covered by the generic mediaCaptureType. Text captures are hence already covered by the generic mediaCaptureType. Text captures are hence
defined as follows:</t> defined as follows:</t>
<t> <sourcecode type="xml"><![CDATA[
<figure>
<artwork>
<![CDATA[
<!-- TEXT CAPTURE TYPE --> <!-- TEXT CAPTURE TYPE -->
<xs:complexType name="textCaptureType"> <xs:complexType name="textCaptureType">
<xs:complexContent> <xs:complexContent>
<xs:extension base="tns:mediaCaptureType"> <xs:extension base="tns:mediaCaptureType">
<xs:sequence> <xs:sequence>
<xs:any namespace="##other" processContents="lax" minOccurs="0" <xs:any namespace="##other" processContents="lax" minOccurs="0"
maxOccurs="unbounded"/> maxOccurs="unbounded"/>
</xs:sequence> </xs:sequence>
<xs:anyAttribute namespace="##other" processContents="lax"/> <xs:anyAttribute namespace="##other" processContents="lax"/>
</xs:extension> </xs:extension>
</xs:complexContent> </xs:complexContent>
</xs:complexType> </xs:complexType>
]]></sourcecode>
]]> <t>Text captures <bcp14>MUST</bcp14> be marked as non spatially definable
</artwork> (i.e., they
</figure> <bcp14>MUST</bcp14> present in their XML description the
</t> <xref target="sub-sec-nonspatiallydef" format="default">
<t>Text captures MUST be marked as non spatially definable (i.e., they
MUST present in their XML description the
<xref target="sub-sec-nonspatiallydef">
&lt;nonSpatiallyDefinable&gt;</xref> element set to "true"). &lt;nonSpatiallyDefinable&gt;</xref> element set to "true").
</t> </t>
</section> </section>
<section numbered="true" toc="default">
<section title="Other capture types"> <name>Other Capture Types</name>
<t> <t>
Other media capture types can be described by using the CLUE data model. Other media capture types can be described by using the CLUE data model.
They can be represented by exploiting the "otherCaptureType" They can be represented by exploiting the "otherCaptureType"
type. type.
This media capture type is conceived to be This media capture type is conceived to be
filled in with elements defined within extensions of the current schema, filled in with elements defined within extensions of the current schema,
i.e., with i.e., with
elements defined in other XML schemas elements defined in other XML schemas
(see <xref target="sec-extension"/> for an example). (see <xref target="sec-extension" format="default"/> for an example).
The otherCaptureType inherits all the features envisioned for The otherCaptureType inherits all the features envisioned for
the abstract mediaCaptureType. the abstract mediaCaptureType.
</t> </t>
<t>The XML Schema representation of the <t>The XML Schema representation of the
otherCaptureType is the following:</t> otherCaptureType is the following:</t>
<t> <sourcecode type="xml"><![CDATA[
<figure>
<artwork>
<![CDATA[
<!-- OTHER CAPTURE TYPE --> <!-- OTHER CAPTURE TYPE -->
<xs:complexType name="otherCaptureType"> <xs:complexType name="otherCaptureType">
<xs:complexContent> <xs:complexContent>
<xs:extension base="tns:mediaCaptureType"> <xs:extension base="tns:mediaCaptureType">
<xs:sequence> <xs:sequence>
<xs:any namespace="##other" processContents="lax" minOccurs="0" <xs:any namespace="##other" processContents="lax" minOccurs="0"
maxOccurs="unbounded"/> maxOccurs="unbounded"/>
</xs:sequence> </xs:sequence>
<xs:anyAttribute namespace="##other" processContents="lax"/> <xs:anyAttribute namespace="##other" processContents="lax"/>
</xs:extension> </xs:extension>
</xs:complexContent> </xs:complexContent>
</xs:complexType> </xs:complexType>
]]></sourcecode>
]]> <t>When defining new media capture types that are going to be described
</artwork>
</figure>
</t>
<t>When defining new media capture types that are going to be described
by means of the &lt;otherMediaCapture&gt; element, by means of the &lt;otherMediaCapture&gt; element,
spatial properties of such new media capture types SHOULD be defined spatial properties of such new media capture types <bcp14>SHOULD</bcp14> be defi
(e.g., whether or not they are spatially definable, whether or not they ned
should be associated with an area of capture, or other properties (e.g., whether or not they are spatially definable and whether or not they
should be associated with an area of capture or other properties
that may be defined).</t> that may be defined).</t>
</section> </section>
<section anchor="sec-capture-scene" numbered="true" toc="default">
<section title="&lt;captureScene&gt;" anchor="sec-capture-scene"> <name>&lt;captureScene&gt;</name>
<t>A Media Provider organizes the available captures <t>A Media Provider organizes the available captures
in capture scenes in order to help the receiver both in capture scenes in order to help the receiver
in the rendering and in the selection of the group in both the rendering and the selection of the group
of captures. Capture scenes are made of media captures and of captures. Capture scenes are made of media captures and
capture scene views, that are sets of capture scene views, which are sets of
media captures of the same media type. media captures of the same media type.
Each capture scene view is an alternative Each capture scene view is an alternative
to represent completely a capture scene for a fixed to completely represent a capture scene for a fixed
media type.</t> media type.</t>
<t>The XML Schema representation of a &lt;captureScene&gt; element <t>The XML Schema representation of a &lt;captureScene&gt; element
is the following: is the following:
</t> </t>
<t> <sourcecode type="xml"><![CDATA[
<figure>
<artwork>
<![CDATA[
<!-- CAPTURE SCENE TYPE --> <!-- CAPTURE SCENE TYPE -->
<xs:complexType name="captureSceneType"> <xs:complexType name="captureSceneType">
<xs:sequence> <xs:sequence>
<xs:element ref="description" minOccurs="0" maxOccurs="unbounded"/> <xs:element ref="description" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="sceneInformation" type="xcard:vcardType" <xs:element name="sceneInformation" type="xcard:vcardType"
minOccurs="0"/> minOccurs="0"/>
<xs:element name="sceneViews" type="sceneViewsType" minOccurs="0"/> <xs:element name="sceneViews" type="sceneViewsType" minOccurs="0"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" <xs:any namespace="##other" processContents="lax" minOccurs="0"
maxOccurs="unbounded"/> maxOccurs="unbounded"/>
</xs:sequence> </xs:sequence>
<xs:attribute name="sceneID" type="xs:ID" use="required"/> <xs:attribute name="sceneID" type="xs:ID" use="required"/>
<xs:attribute name="scale" type="scaleType" use="required"/> <xs:attribute name="scale" type="scaleType" use="required"/>
<xs:anyAttribute namespace="##other" processContents="lax"/> <xs:anyAttribute namespace="##other" processContents="lax"/>
</xs:complexType> </xs:complexType>
]]> ]]></sourcecode>
</artwork> <t>
</figure>
</t>
<t>
Each capture scene is identified by a "sceneID" attribute. Each capture scene is identified by a "sceneID" attribute.
The &lt;captureScene&gt; element can contain zero or more The &lt;captureScene&gt; element can contain zero or more
textual &lt;description&gt; elements, defined as in textual &lt;description&gt; elements, as defined in
<xref target="sec-description"/>. <xref target="sec-description" format="default"/>.
Besides &lt;description&gt;, there is the optional Besides &lt;description&gt;, there is the optional
&lt;sceneInformation&gt; &lt;sceneInformation&gt;
element element
(<xref target="sec-scene-info" />), (<xref target="sec-scene-info" format="default"/>),
which contains structured which contains structured
information about the scene in the vcard format, and the optional information about the scene in the vCard format, and the optional
&lt;sceneViews&gt; element &lt;sceneViews&gt; element
(<xref target="sec-scene-views"/>), which is the list of (<xref target="sec-scene-views" format="default"/>), which is the list of
the capture scene the capture scene
views. views.
When no &lt;sceneViews&gt; is provided, the capture scene is assumed to When no &lt;sceneViews&gt; is provided, the capture scene is assumed to
be made of all the media captures which contain the value of its sceneID be made of all the media captures that contain the value of its sceneID
attribute in their mandatory captureSceneIDREF attribute. attribute in their mandatory captureSceneIDREF attribute.
</t> </t>
<section anchor="sec-scene-info" numbered="true" toc="default">
<section title="&lt;sceneInformation&gt;" anchor="sec-scene-info"> <name>&lt;sceneInformation&gt;</name>
<t> <t>
The &lt;sceneInformation&gt; element contains optional information about The &lt;sceneInformation&gt; element contains optional information about
the the
capture scene according to the vcard format, as specified in the Xcard capture scene according to the vCard format, as specified in the xCard
RFC <xref target="RFC6351"/>. specification <xref target="RFC6351" format="default"/>.
</t> </t>
</section> </section>
<section anchor="sec-scene-views" numbered="true" toc="default">
<section title="&lt;sceneViews&gt;" <name>&lt;sceneViews&gt;</name>
anchor="sec-scene-views"> <t>
<t>
The &lt;sceneViews&gt; element is a mandatory The &lt;sceneViews&gt; element is a mandatory
field of a capture scene containing the list field of a capture scene containing the list
of scene views. of scene views.
Each scene view is represented by a &lt;sceneView&gt; Each scene view is represented by a &lt;sceneView&gt;
element (<xref target="sec-scene-view"/>). element (<xref target="sec-scene-view" format="default"/>).
</t> </t>
<t> <sourcecode type="xml"><![CDATA[
<figure>
<artwork>
<![CDATA[
<!-- SCENE VIEWS TYPE --> <!-- SCENE VIEWS TYPE -->
<!-- envelope of scene views of a capture scene --> <!-- envelope of scene views of a capture scene -->
<xs:complexType name="sceneViewsType"> <xs:complexType name="sceneViewsType">
<xs:sequence> <xs:sequence>
<xs:element name="sceneView" type="sceneViewType" <xs:element name="sceneView" type="sceneViewType"
maxOccurs="unbounded"/> maxOccurs="unbounded"/>
</xs:sequence> </xs:sequence>
</xs:complexType> </xs:complexType>
]]> ]]></sourcecode>
</artwork> </section>
</figure> <section anchor="sec-sceneID" numbered="true" toc="default">
</t> <name>sceneID Attribute</name>
</section> <t>The sceneID attribute is a mandatory attribute
<section title="sceneID attribute" anchor="sec-sceneID">
<t>The sceneID attribute is a mandatory attribute
containing the identifier of the capture scene. containing the identifier of the capture scene.
</t> </t>
</section> </section>
<section title="scale attribute" anchor="sec-scale"> <section anchor="sec-scale" numbered="true" toc="default">
<t> <name>scale Attribute</name>
<t>
The scale attribute is a mandatory attribute The scale attribute is a mandatory attribute
that specifies the scale of the coordinates that specifies the scale of the coordinates
provided in the spatial provided in the spatial
information of the media capture belonging to information of the media capture belonging to
the considered capture scene. the considered capture scene.
The scale attribute can assume three different values: The scale attribute can assume three different values:
</t> </t>
<t> <ul empty="true" spacing="normal"><li>
<list style="empty"> <dl newline="false" spacing="normal">
<t>"mm" - the scale is in millimeters. <dt>"mm":</dt><dd>the scale is in millimeters.
Systems which Systems that
know their physical dimensions know their physical dimensions
(for example professionally (for example, professionally
installed telepresence room systems) installed telepresence room systems)
should always provide such should always provide such
real-world measurements. real-world measurements.</dd>
</t> <dt>"unknown":</dt><dd>the scale is the same for every media capture
<t>"unknown" - the scale is the same for every media capture in the capture scene, but the unity of measure is undefined.
in the capture scene but the unity of measure is undefined. Systems that are not aware of specific
Systems which are not aware of specific
physical dimensions yet still know physical dimensions yet still know
relative distances should select relative distances should select
"unknown" in the scale attribute of the "unknown" in the scale attribute of the
capture scene to be described. capture scene to be described.</dd>
</t> <dt>"noscale":</dt><dd>there is no common physical scale
<t>"noscale" - there is no common physical scale
among the media captures of the capture scene. among the media captures of the capture scene.
That means the scale could be different for each That means the scale could be different for each
media capture. </t> media capture.</dd></dl></li>
</list> </ul>
</t> <sourcecode type="xml"><![CDATA[
<t>
<figure>
<artwork>
<![CDATA[
<!-- SCALE TYPE --> <!-- SCALE TYPE -->
<xs:simpleType name="scaleType"> <xs:simpleType name="scaleType">
<xs:restriction base="xs:string"> <xs:restriction base="xs:string">
<xs:enumeration value="mm"/> <xs:enumeration value="mm"/>
<xs:enumeration value="unknown"/> <xs:enumeration value="unknown"/>
<xs:enumeration value="noscale"/> <xs:enumeration value="noscale"/>
</xs:restriction> </xs:restriction>
</xs:simpleType> </xs:simpleType>
]]> ]]></sourcecode>
</artwork> </section>
</figure> </section>
</t>
</section>
</section><!-- capture scene section -->
<section title="&lt;sceneView&gt;" <section anchor="sec-scene-view" numbered="true" toc="default">
anchor="sec-scene-view"> <name>&lt;sceneView&gt;</name>
<t> <t>
A &lt;sceneView&gt; element represents a A &lt;sceneView&gt; element represents a
capture scene view, which contains a set of media capture scene view, which contains a set of media
captures of the same media type describing captures of the same media type describing
a capture scene. a capture scene.
</t> </t>
<t>A &lt;sceneView&gt; element is characterized as follows. <t>A &lt;sceneView&gt; element is characterized as follows.
</t> </t>
<t> <sourcecode type="xml"><![CDATA[
<figure>
<artwork>
<![CDATA[
<!-- SCENE VIEW TYPE --> <!-- SCENE VIEW TYPE -->
<xs:complexType name="sceneViewType"> <xs:complexType name="sceneViewType">
<xs:sequence> <xs:sequence>
<xs:element ref="description" minOccurs="0" maxOccurs="unbounded"/> <xs:element ref="description" minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="mediaCaptureIDs" type="captureIDListType"/> <xs:element name="mediaCaptureIDs" type="captureIDListType"/>
</xs:sequence> </xs:sequence>
<xs:attribute name="sceneViewID" type="xs:ID" use="required"/> <xs:attribute name="sceneViewID" type="xs:ID" use="required"/>
</xs:complexType> </xs:complexType>
]]></sourcecode>
]]> <t>
</artwork>
</figure>
</t>
<t>
One or more optional &lt;description&gt; elements One or more optional &lt;description&gt; elements
provide human-readable information about what the scene provide human-readable information about what the scene
view contains. &lt;description&gt; is defined as already view contains. &lt;description&gt; is defined in <xref target="sec-description"
seen in <xref target="sec-description"/>. format="default"/>.
</t> </t>
<t>The remaining child elements are described in the <t>The remaining child elements are described in the
following subsections.</t> following subsections.</t>
<section numbered="true" toc="default">
<section title="&lt;mediaCaptureIDs&gt;"> <name>&lt;mediaCaptureIDs&gt;</name>
<t> <t>
The &lt;mediaCaptureIDs&gt; is the list of the &lt;mediaCaptureIDs&gt; is the list of the
identifiers of the media captures included in the identifiers of the media captures included in the
scene view. scene view.
It is an element of the captureIDListType type, which is It is an element of the captureIDListType type, which is
defined as a sequence of &lt;mediaCaptureIDREF&gt;, each defined as a sequence of &lt;mediaCaptureIDREF&gt;, each
containing the identifier of a media capture containing the identifier of a media capture
listed within the &lt;mediaCaptures&gt; element: listed within the &lt;mediaCaptures&gt; element:
</t> </t>
<t> <sourcecode type="xml"><![CDATA[
<figure>
<artwork>
<![CDATA[
<!-- CAPTURE ID LIST TYPE --> <!-- CAPTURE ID LIST TYPE -->
<xs:complexType name="captureIDListType"> <xs:complexType name="captureIDListType">
<xs:sequence> <xs:sequence>
<xs:element name="mediaCaptureIDREF" type="xs:IDREF" <xs:element name="mediaCaptureIDREF" type="xs:IDREF"
maxOccurs="unbounded"/> maxOccurs="unbounded"/>
</xs:sequence> </xs:sequence>
</xs:complexType> </xs:complexType>
]]> ]]></sourcecode>
</artwork> </section>
</figure> <section numbered="true" toc="default">
</t> <name>sceneViewID Attribute</name>
</section> <t>The sceneViewID attribute is a mandatory attribute
<section title="sceneViewID attribute">
<t>The sceneViewID attribute is a mandatory attribute
containing the identifier of the capture scene view containing the identifier of the capture scene view
represented by the &lt;sceneView&gt; element.</t> represented by the &lt;sceneView&gt; element.</t>
</section> </section>
</section><!-- scene view section --> </section>
<section anchor="sec-encoding-group" numbered="true" toc="default">
<section title="&lt;encodingGroup&gt;" <name>&lt;encodingGroup&gt;</name>
anchor="sec-encoding-group"> <t>
<t>
The &lt;encodingGroup&gt; element represents The &lt;encodingGroup&gt; element represents
an encoding group, which is made by a an encoding group, which is made by a
set of one or more individual set of one or more individual
encodings and some parameters that apply encodings and some parameters that apply
to the group as a whole. to the group as a whole.
Encoding groups contain references to individual encodings Encoding groups contain references to individual encodings
that can be applied to media captures. that can be applied to media captures.
The definition of the &lt;encodingGroup&gt; element The definition of the &lt;encodingGroup&gt; element
is the following: is the following:
</t> </t>
<t> <sourcecode type="xml"><![CDATA[
<figure>
<artwork>
<![CDATA[
<!-- ENCODING GROUP TYPE --> <!-- ENCODING GROUP TYPE -->
<xs:complexType name="encodingGroupType"> <xs:complexType name="encodingGroupType">
<xs:sequence> <xs:sequence>
<xs:element name="maxGroupBandwidth" type="xs:unsignedLong"/> <xs:element name="maxGroupBandwidth" type="xs:unsignedLong"/>
<xs:element name="encodingIDList" type="encodingIDListType"/> <xs:element name="encodingIDList" type="encodingIDListType"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" <xs:any namespace="##other" processContents="lax" minOccurs="0"
maxOccurs="unbounded"/> maxOccurs="unbounded"/>
</xs:sequence> </xs:sequence>
<xs:attribute name="encodingGroupID" type="xs:ID" use="required"/> <xs:attribute name="encodingGroupID" type="xs:ID" use="required"/>
<xs:anyAttribute namespace="##any" processContents="lax"/> <xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType> </xs:complexType>
]]> ]]></sourcecode>
</artwork> <t>
</figure> In the following subsections, the contained elements are further described.
</t>
<t>
In the following, the contained elements are further described.
</t> </t>
<section title="&lt;maxGroupBandwidth&gt;"> <section numbered="true" toc="default">
<t>&lt;maxGroupBandwidth&gt; is an optional field <name>&lt;maxGroupBandwidth&gt;</name>
<t>&lt;maxGroupBandwidth&gt; is an optional field
containing the maximum bitrate expressed in bits per second that can be containing the maximum bitrate expressed in bits per second that can be
shared by the individual encodings included in the encoding group. shared by the individual encodings included in the encoding group.
</t> </t>
</section> </section>
<section anchor="sec-encodingIDList" numbered="true" toc="default">
<section title="&lt;encodingIDList&gt;" anchor="sec-encodingIDList"> <name>&lt;encodingIDList&gt;</name>
<t>&lt;encodingIDList&gt; is the list <t>&lt;encodingIDList&gt; is the list
of the individual encodings grouped together in the encoding group. of the individual encodings grouped together in the encoding group.
Each individual encoding is represented Each individual encoding is represented
through its identifier contained within through its identifier contained within
an &lt;encodingID&gt; element. an &lt;encodingID&gt; element.
</t> </t>
<t> <sourcecode type="xml"><![CDATA[
<figure>
<artwork>
<![CDATA[
<!-- ENCODING ID LIST TYPE --> <!-- ENCODING ID LIST TYPE -->
<xs:complexType name="encodingIDListType"> <xs:complexType name="encodingIDListType">
<xs:sequence> <xs:sequence>
<xs:element name="encodingID" type="xs:string" maxOccurs="unbounded"/> <xs:element name="encodingID" type="xs:string"
maxOccurs="unbounded"/>
</xs:sequence> </xs:sequence>
</xs:complexType> </xs:complexType>
]]> ]]></sourcecode>
</artwork> </section>
</figure> <section anchor="sec-encodingGroupID" numbered="true" toc="default">
</t> <name>encodingGroupID Attribute</name>
</section> <t>The encodingGroupID attribute contains the
<section title="encodingGroupID attribute" anchor="sec-encodingGroupID">
<t>The encodingGroupID attribute contains the
identifier of the encoding group.</t> identifier of the encoding group.</t>
</section> </section>
</section><!-- encoding group --> </section>
<section title="&lt;simultaneousSet&gt;" anchor="sec-simultaneous-set"> <section anchor="sec-simultaneous-set" numbered="true" toc="default">
<t>&lt;simultaneousSet&gt; represents a simultaneous <name>&lt;simultaneousSet&gt;</name>
<t>&lt;simultaneousSet&gt; represents a simultaneous
transmission set, i.e., a list of captures of the same media type transmission set, i.e., a list of captures of the same media type
that can be transmitted at the same time that can be transmitted at the same time
by a Media Provider. by a Media Provider.
There are different simultaneous transmission sets There are different simultaneous transmission sets
for each media type. for each media type.
</t> </t>
<t> <sourcecode type="xml"><![CDATA[
<figure>
<artwork>
<![CDATA[
<!-- SIMULTANEOUS SET TYPE --> <!-- SIMULTANEOUS SET TYPE -->
<xs:complexType name="simultaneousSetType"> <xs:complexType name="simultaneousSetType">
<xs:sequence> <xs:sequence>
<xs:element name="mediaCaptureIDREF" type="xs:IDREF" <xs:element name="mediaCaptureIDREF" type="xs:IDREF"
minOccurs="0" maxOccurs="unbounded"/> minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="sceneViewIDREF" type="xs:IDREF" <xs:element name="sceneViewIDREF" type="xs:IDREF"
minOccurs="0" maxOccurs="unbounded"/> minOccurs="0" maxOccurs="unbounded"/>
<xs:element name="captureSceneIDREF" type="xs:IDREF" <xs:element name="captureSceneIDREF" type="xs:IDREF"
minOccurs="0" maxOccurs="unbounded"/> minOccurs="0" maxOccurs="unbounded"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" <xs:any namespace="##other" processContents="lax" minOccurs="0"
maxOccurs="unbounded"/> maxOccurs="unbounded"/>
</xs:sequence> </xs:sequence>
<xs:attribute name="setID" type="xs:ID" use="required"/> <xs:attribute name="setID" type="xs:ID" use="required"/>
<xs:attribute name="mediaType" type="xs:string"/> <xs:attribute name="mediaType" type="xs:string"/>
<xs:anyAttribute namespace="##any" processContents="lax"/> <xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType> </xs:complexType>
]]> ]]></sourcecode>
</artwork> <t>
</figure>
</t>
<t>
Besides the identifiers of the captures (&lt;mediaCaptureIDREF&gt; Besides the identifiers of the captures (&lt;mediaCaptureIDREF&gt;
elements), also the identifiers of capture scene views and of capture elements), the identifiers of capture scene views and capture
scene can be exploited as shortcuts scenes can also be exploited as shortcuts
(&lt;sceneViewIDREF&gt; and &lt;captureSceneIDREF&gt; elements). (&lt;sceneViewIDREF&gt; and &lt;captureSceneIDREF&gt; elements).
As an example, let's consider the situation where there are two capture As an example, let's consider the situation where there are two capture
scene views (S1 and S7). scene views (S1 and S7).
S1 contains captures AC11, AC12, AC13. S7 contains captures AC71, AC72. S1 contains captures AC11, AC12, and AC13. S7 contains captures AC71 and AC72.
Provided that AC11, AC12, AC13, AC71, AC72 can be simultaneously sent to Provided that AC11, AC12, AC13, AC71, and AC72 can be simultaneously sent to
the media consumer, instead of having 5 &lt;mediaCaptureIDREF&gt; the media consumer, instead of having 5 &lt;mediaCaptureIDREF&gt;
elements listed in the simultaneous set (i.e., one elements listed in the simultaneous set (i.e., one
&lt;mediaCaptureIDREF&gt; for AC11, one for AC12, and so on), there can &lt;mediaCaptureIDREF&gt; for AC11, one for AC12, and so on), there can
be just two &lt;sceneViewIDREF&gt; elements (one for S1 and one for S7). be just two &lt;sceneViewIDREF&gt; elements (one for S1 and one for S7).
</t> </t>
<section title="setID attribute"> <section numbered="true" toc="default">
<t> <name>setID Attribute</name>
<t>
The "setID" attribute is a mandatory field containing the identifier of The "setID" attribute is a mandatory field containing the identifier of
the simultaneous set. the simultaneous set.
</t> </t>
</section>
</section> <section numbered="true" toc="default">
<section title="mediaType attribute"> <name>mediaType Attribute</name>
<t> <t>
The "mediaType" attribute is an optional attribute containing the media The "mediaType" attribute is an optional attribute containing the media
type of the type of the
captures referenced by the simultaneous set. captures referenced by the simultaneous set.
</t> </t>
<t>When only capture scene identifiers are listed within a simultaneous <t>When only capture scene identifiers are listed within a simultaneous
set, the media type attribute MUST appear in the XML description in set, the media type attribute <bcp14>MUST</bcp14> appear in the XML description
in
order to determine which media captures can be simultaneously sent order to determine which media captures can be simultaneously sent
together. together.
</t> </t>
</section> </section>
<section numbered="true" toc="default">
<section title="&lt;mediaCaptureIDREF&gt;"> <name>&lt;mediaCaptureIDREF&gt;</name>
<t>&lt;mediaCaptureIDREF&gt; contains the identifier of the media <t>&lt;mediaCaptureIDREF&gt; contains the identifier of the media
capture that belongs to the simultaneous set. capture that belongs to the simultaneous set.
</t> </t>
</section> </section>
<section title="&lt;sceneViewIDREF&gt;"> <section numbered="true" toc="default">
<t>&lt;sceneViewIDREF&gt; contains the identifier of the scene <name>&lt;sceneViewIDREF&gt;</name>
<t>&lt;sceneViewIDREF&gt; contains the identifier of the scene
view containing a group of captures view containing a group of captures
that are able to be sent simultaneously with the other that are able to be sent simultaneously with the other
captures of the simultaneous set. captures of the simultaneous set.
</t> </t>
</section> </section>
<section numbered="true" toc="default">
<section title="&lt;captureSceneIDREF&gt;"> <name>&lt;captureSceneIDREF&gt;</name>
<t>&lt;captureSceneIDREF&gt; contains the identifier of the capture <t>&lt;captureSceneIDREF&gt; contains the identifier of the capture
scene where all the included captures of a certain media type scene where all the included captures of a certain media type
are able to be sent together with the other captures of the simultaneous are able to be sent together with the other captures of the simultaneous
set. set.
</t> </t>
</section> </section>
</section><!-- simultaneous set section --> </section>
<section title="&lt;globalView&gt;" anchor="sec-global-view"> <section anchor="sec-global-view" numbered="true" toc="default">
<t>&lt;globalView&gt; is a set of captures of the same media type <name>&lt;globalView&gt;</name>
<t>&lt;globalView&gt; is a set of captures of the same media type
representing a summary of the complete Media Provider's offer. representing a summary of the complete Media Provider's offer.
The content of a global view is expressed The content of a global view is expressed
by leveraging only scene view identifiers, put within by leveraging only scene view identifiers, put within
&lt;sceneViewIDREF&gt; elements. &lt;sceneViewIDREF&gt; elements.
Each global view is identified by a unique identifier within the Each global view is identified by a unique identifier within the
"globalViewID" attribute. "globalViewID" attribute.
</t> </t>
<t> <sourcecode type="xml"><![CDATA[
<figure>
<artwork>
<![CDATA[
<!-- GLOBAL VIEW TYPE --> <!-- GLOBAL VIEW TYPE -->
<xs:complexType name="globalViewType"> <xs:complexType name="globalViewType">
<xs:sequence> <xs:sequence>
<xs:element name="sceneViewIDREF" type="xs:IDREF" <xs:element name="sceneViewIDREF" type="xs:IDREF"
maxOccurs="unbounded"/> maxOccurs="unbounded"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" <xs:any namespace="##other" processContents="lax" minOccurs="0"
maxOccurs="unbounded"/> maxOccurs="unbounded"/>
</xs:sequence> </xs:sequence>
<xs:attribute name="globalViewID" type="xs:ID"/> <xs:attribute name="globalViewID" type="xs:ID"/>
<xs:anyAttribute namespace="##any" processContents="lax"/> <xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType> </xs:complexType>
]]> ]]></sourcecode>
</artwork> </section>
</figure> <section anchor="sec-participants" numbered="true" toc="default">
</t> <name>&lt;people&gt;</name>
</section> <t>
<section title="&lt;people&gt;" anchor="sec-participants">
<t>
Information about the participants that are represented in the media Information about the participants that are represented in the media
captures is conveyed via the &lt;people&gt; element. captures is conveyed via the &lt;people&gt; element.
As it can be seen from the XML Schema depicted below, for each As it can be seen from the XML Schema depicted below, for each
participant, a &lt;person&gt; element is provided. participant, a &lt;person&gt; element is provided.
</t> </t>
<figure> <sourcecode type="xml"><![CDATA[
<artwork>
<![CDATA[
<!-- PEOPLE TYPE --> <!-- PEOPLE TYPE -->
<xs:complexType name="peopleType"> <xs:complexType name="peopleType">
<xs:sequence> <xs:sequence>
<xs:element name="person" type="personType" maxOccurs="unbounded"/> <xs:element name="person" type="personType" maxOccurs="unbounded"/>
</xs:sequence> </xs:sequence>
</xs:complexType> </xs:complexType>
]]></sourcecode>
]]> <section anchor="sub-sec-participantInfo" numbered="true" toc="default">
</artwork> <name>&lt;person&gt;</name>
</figure> <t>&lt;person&gt; includes all the metadata related to a person
<section title="&lt;person&gt;" anchor="sub-sec-participantInfo">
<t>&lt;person&gt; includes all the metadata related to a person
represented within one or more media captures. represented within one or more media captures.
Such element provides the vcard of the subject (via the Such element provides the vCard of the subject (via the
&lt;personInfo&gt; element, see <xref target="sub-sec-vcard"/>) &lt;personInfo&gt; element; see <xref target="sub-sec-vcard" format="default"/>)
and his conference role(s) (via one or more &lt;personType&gt; elements, and its conference role(s) (via one or more &lt;personType&gt; elements;
see <xref target="sub-sec-participantType"/>). see <xref target="sub-sec-participantType" format="default"/>).
Furthermore, it has a mandatory "personID" attribute Furthermore, it has a mandatory "personID" attribute
(<xref target="sub-sec-participantID"/>). (<xref target="sub-sec-participantID" format="default"/>).
</t> </t>
<figure> <sourcecode type="xml"><![CDATA[
<artwork>
<![CDATA[
<!-- PERSON TYPE --> <!-- PERSON TYPE -->
<xs:complexType name="personType"> <xs:complexType name="personType">
<xs:sequence> <xs:sequence>
<xs:element name="personInfo" type="xcard:vcardType" maxOccurs="1" <xs:element name="personInfo" type="xcard:vcardType" maxOccurs="1"
minOccurs="0"/> minOccurs="0"/>
<xs:element ref="personType" minOccurs="0" maxOccurs="unbounded" /> <xs:element ref="personType" minOccurs="0" maxOccurs="unbounded" />
<xs:any namespace="##other" processContents="lax" minOccurs="0" <xs:any namespace="##other" processContents="lax" minOccurs="0"
maxOccurs="unbounded"/> maxOccurs="unbounded"/>
</xs:sequence> </xs:sequence>
<xs:attribute name="personID" type="xs:ID" use="required"/> <xs:attribute name="personID" type="xs:ID" use="required"/>
<xs:anyAttribute namespace="##other" processContents="lax"/> <xs:anyAttribute namespace="##other" processContents="lax"/>
</xs:complexType> </xs:complexType>
]]> ]]></sourcecode>
</artwork> <section anchor="sub-sec-participantID" numbered="true" toc="default">
</figure> <name>personID Attribute</name>
<section title="personID attribute" anchor="sub-sec-participantID"> <t>
<t>
The "personID" attribute carries the identifier of a represented person. The "personID" attribute carries the identifier of a represented person.
Such an identifier can be used to refer to the participant, Such an identifier can be used to refer to the participant,
as in the &lt;capturedPeople&gt; element in the media captures as in the &lt;capturedPeople&gt; element in the media captures
representation (<xref target="sec-participantIDs"/>). representation (<xref target="sec-participantIDs" format="default"/>).
</t> </t>
</section> </section>
<section title="&lt;personInfo&gt;" anchor="sub-sec-vcard"> <section anchor="sub-sec-vcard" numbered="true" toc="default">
<t>The &lt;personInfo&gt; element is the XML representation of all the <name>&lt;personInfo&gt;</name>
fields composing a vcard as specified in the Xcard RFC <t>The &lt;personInfo&gt; element is the XML representation of all th
<xref target="RFC6351"/>. e
The vcardType is imported by the Xcard XML Schema provided in Appendix fields composing a vCard as specified in the xCard document
A of <xref target="I-D.ietf-ecrit-additional-data"/>. <xref target="RFC6351" format="default"/>.
The vcardType is imported by the xCard XML Schema provided in <xref target="RFC7
852" sectionFormat="of" section="A" format="default" derivedLink="https://rfc-ed
itor.org/rfc/rfc7852#appendix-A" derivedContent="RFC7852"/>.
As such schema specifies, the &lt;fn&gt; element within &lt;vcard&gt; As such schema specifies, the &lt;fn&gt; element within &lt;vcard&gt;
is mandatory. is mandatory.
</t> </t>
</section> </section>
<section anchor="sub-sec-participantType" numbered="true" toc="default">
<section title="&lt;personType&gt;" anchor="sub-sec-participantType"> <name>&lt;personType&gt;</name>
<t>The value of the &lt;personType&gt; element determines the role of
<t>The value of the &lt;personType&gt; element determines the role of
the represented participant within the telepresence session the represented participant within the telepresence session
organization. It has been specified as a simple string with an organization. It has been specified as a simple string with an
annotation pointing to an ad hoc defined IANA registry: annotation pointing to an IANA registry that is defined ad hoc:
</t> </t>
<figure> <sourcecode type="xml"><![CDATA[
<artwork>
<![CDATA[
<!-- PERSON TYPE ELEMENT --> <!-- PERSON TYPE ELEMENT -->
<xs:element name="personType" type="xs:string"> <xs:element name="personType" type="xs:string">
<xs:annotation> <xs:annotation>
<xs:documentation> <xs:documentation>
Acceptable values (enumerations) for this type are managed Acceptable values (enumerations) for this type are managed
by IANA in the "CLUE Schema <personType> registry", by IANA in the "CLUE Schema <personType> registry",
accessible at TBD-IANA. accessible at https://www.iana.org/assignments/clue.
</xs:documentation> </xs:documentation>
</xs:annotation> </xs:annotation>
</xs:element> </xs:element>
]]></sourcecode>
]]> <t>
</artwork>
</figure>
<t>
The current possible values, as per the CLUE framework document The current possible values, as per the CLUE framework document
<xref target="I-D.ietf-clue-framework"/>, are: "presenter", <xref target="RFC8845" format="default"/>, are: "presenter",
"timekeeper", "attendee", "minute taker", "translator", "chairman", "timekeeper", "attendee", "minute taker", "translator", "chairman",
"vice-chairman", "observer".</t> "vice-chairman", and "observer".</t>
<t>
<t>
A participant can play more than one conference role. In that case, more A participant can play more than one conference role. In that case, more
than one &lt;personType&gt; element will appear in his description. than one &lt;personType&gt; element will appear in its description.
</t> </t>
</section>
</section>
</section>
</section> <section anchor="sec-capture-encoding" numbered="true" toc="default">
</section> <name>&lt;captureEncoding&gt;</name>
</section> <t>A capture encoding is given from
<!-- </section> -->
<section title="&lt;captureEncoding&gt;" anchor="sec-capture-encoding">
<t>A capture encoding is given from
the association of a media capture the association of a media capture
with an individual encoding, to form a capture stream as defined in with an individual encoding, to form a capture stream as defined in
<xref target="I-D.ietf-clue-framework"/>. <xref target="RFC8845" format="default"/>.
Capture encodings are used within CONFIGURE messages from a Media Capture encodings are used within CONFIGURE messages from a Media
Consumer to a Media Provider for representing the streams desired by the Consumer to a Media Provider for representing the streams desired by the
Media Consumer. Media Consumer.
For each desired stream, the Media Consumer needs to be allowed to For each desired stream, the Media Consumer needs to be allowed to
specify: (i) the capture identifier of the desired capture that has been specify: (i) the capture identifier of the desired capture that has been
advertised by the Media Provider; (ii) the encoding identifier of the advertised by the Media Provider; (ii) the encoding identifier of the
encoding to use, among those advertised by the Media Provider; encoding to use, among those advertised by the Media Provider;
(iii) optionally, in case of multi-content captures, the list of the and (iii) optionally, in case of multicontent captures, the list of the
capture identifiers of the desired captures. capture identifiers of the desired captures.
All the mentioned identifiers are intended to be included in the All the mentioned identifiers are intended to be included in the
ADVERTISEMENT message that the CONFIGURE message refers to. ADVERTISEMENT message that the CONFIGURE message refers to.
The XML model of &lt;captureEncoding&gt; is provided in the following. The XML model of &lt;captureEncoding&gt; is provided in the following.
</t> </t>
<t> <sourcecode type="xml"><![CDATA[
<figure>
<artwork>
<![CDATA[
<!-- CAPTURE ENCODING TYPE --> <!-- CAPTURE ENCODING TYPE -->
<xs:complexType name="captureEncodingType"> <xs:complexType name="captureEncodingType">
<xs:sequence> <xs:sequence>
<xs:element name="captureID" type="xs:string"/> <xs:element name="captureID" type="xs:string"/>
<xs:element name="encodingID" type="xs:string"/> <xs:element name="encodingID" type="xs:string"/>
<xs:element name="configuredContent" type="contentType" <xs:element name="configuredContent" type="contentType"
minOccurs="0"/> minOccurs="0"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" <xs:any namespace="##other" processContents="lax" minOccurs="0"
maxOccurs="unbounded"/> maxOccurs="unbounded"/>
</xs:sequence> </xs:sequence>
<xs:attribute name="ID" type="xs:ID" use="required"/> <xs:attribute name="ID" type="xs:ID" use="required"/>
<xs:anyAttribute namespace="##any" processContents="lax"/> <xs:anyAttribute namespace="##any" processContents="lax"/>
</xs:complexType> </xs:complexType>
]]></sourcecode>
]]> <section numbered="true" toc="default">
</artwork> <name>&lt;captureID&gt;</name>
</figure> <t>&lt;captureID&gt; is the mandatory element containing the identifier
</t>
<section title="&lt;captureID&gt;">
<t>&lt;captureID&gt; is the mandatory element containing the identifier
of the media capture that has been encoded to of the media capture that has been encoded to
form the capture encoding.</t> form the capture encoding.</t>
</section> </section>
<section title="&lt;encodingID&gt;"> <section numbered="true" toc="default">
<t>&lt;encodingID&gt; is the mandatory element containing the identifier <name>&lt;encodingID&gt;</name>
<t>&lt;encodingID&gt; is the mandatory element containing the identifier
of the applied individual encoding. of the applied individual encoding.
</t> </t>
</section> </section>
<section title="&lt;configuredContent&gt;"> <section numbered="true" toc="default">
<t>&lt;configuredContent&gt; is an optional element to be used in case <name>&lt;configuredContent&gt;</name>
of configuration of MCC. <t>&lt;configuredContent&gt; is an optional element to be used in case
of the configuration of MCC.
It contains the list of capture identifiers and capture scene view It contains the list of capture identifiers and capture scene view
identifiers the Media Consumer wants within the MCC. identifiers the Media Consumer wants within the MCC.
That element is structured as the &lt;content&gt; element used to That element is structured as the &lt;content&gt; element used to
describe the content of an MCC. describe the content of an MCC.
The total number of media captures listed in the The total number of media captures listed in the
&lt;configuredContent&gt; MUST be lower than or equal to the value &lt;configuredContent&gt; <bcp14>MUST</bcp14> be lower than or equal to the valu e
carried within the &lt;maxCaptures&gt; attribute of the MCC. carried within the &lt;maxCaptures&gt; attribute of the MCC.
</t> </t>
</section> </section>
</section><!-- capture encoding section --> </section>
<section title="&lt;clueInfo&gt;"> <section numbered="true" toc="default">
<t>The &lt;clueInfo&gt; element includes all the <name>&lt;clueInfo&gt;</name>
<t>The &lt;clueInfo&gt; element includes all the
information needed to represent the Media Provider's description of information needed to represent the Media Provider's description of
its telepresence capabilities according to the its telepresence capabilities according to the
CLUE framework. CLUE framework.
Indeed, it is made by:</t> Indeed, it is made by:</t>
<list> <ul empty="false" spacing="normal">
<t>the list of the available media captures <li>the list of the available media captures
(<xref target="sec-media-captures">&lt;mediaCaptures&gt;</xref>)</t> (see "&lt;mediaCaptures&gt;", <xref target="sec-media-captures" format="default
<t>the list of encoding groups "/>)</li>
(<xref target="sec-encoding-groups">&lt;encodingGroups&gt;</xref>)</t> <li>the list of encoding groups
<t>the list of capture scenes (see "&lt;encodingGroups&gt;", <xref target="sec-encoding-groups" format="defa
(<xref target="sec-capture-scenes">&lt;captureScenes&gt;</xref>)</t> ult"/>)</li>
<t>the list of simultaneous transmission sets <li>the list of capture scenes
(<xref target="sec-simultaneous-sets">&lt;simultaneousSets&gt;</xref>) (see "&lt;captureScenes&gt;", <xref target="sec-capture-scenes" format="defaul
</t> t"/>)</li>
<t>the list of global views sets <li>the list of simultaneous transmission sets
(<xref target="sec-global-views">&lt;globalViews&gt;</xref>)</t> (see "&lt;simultaneousSets&gt;", <xref target="sec-simultaneous-sets" format="
<t>meta data about the participants represented in the telepresence default"/>)</li>
session (<xref target="sec-participants">&lt;people&gt; </xref>)</t> <li>the list of global views sets
</list> (see "&lt;globalViews&gt;", <xref target="sec-global-views" format="default"/>
<t> )</li>
It has been conceived only for data model testing purposes and, though <li>metadata about the participants represented in the telepresence
session (see "&lt;people&gt;", <xref target="sec-participants" format="default
"/>)</li>
</ul>
<t>
It has been conceived only for data model testing purposes, and though
it resembles the body of an ADVERTISEMENT message, it is not actually it resembles the body of an ADVERTISEMENT message, it is not actually
used in the CLUE protocol message definitions. used in the CLUE protocol message definitions.
The telepresence capabilities descriptions compliant to The telepresence capabilities descriptions compliant to
this data model specification that can be found in this data model specification that can be found in Sections
<xref target="sec-XML-sample"/> and <xref target="sec-MCC-sample"/> <xref target="sec-XML-sample" format="counter"/> and <xref target="sec-MCC-sampl
e" format="counter"/>
are provided by using the &lt;clueInfo&gt; element. are provided by using the &lt;clueInfo&gt; element.
</t> </t>
<t> <sourcecode type="xml"><![CDATA[
<figure>
<artwork>
<![CDATA[
<!-- CLUE INFO TYPE --> <!-- CLUE INFO TYPE -->
<xs:complexType name="clueInfoType"> <xs:complexType name="clueInfoType">
<xs:sequence> <xs:sequence>
<xs:element ref="mediaCaptures"/> <xs:element ref="mediaCaptures"/>
<xs:element ref="encodingGroups"/> <xs:element ref="encodingGroups"/>
<xs:element ref="captureScenes"/> <xs:element ref="captureScenes"/>
<xs:element ref="simultaneousSets" minOccurs="0"/> <xs:element ref="simultaneousSets" minOccurs="0"/>
<xs:element ref="globalViews" minOccurs="0"/> <xs:element ref="globalViews" minOccurs="0"/>
<xs:element ref="people" minOccurs="0"/> <xs:element ref="people" minOccurs="0"/>
<xs:any namespace="##other" processContents="lax" minOccurs="0" <xs:any namespace="##other" processContents="lax" minOccurs="0"
maxOccurs="unbounded"/> maxOccurs="unbounded"/>
</xs:sequence> </xs:sequence>
<xs:attribute name="clueInfoID" type="xs:ID" use="required"/> <xs:attribute name="clueInfoID" type="xs:ID" use="required"/>
<xs:anyAttribute namespace="##other" processContents="lax"/> <xs:anyAttribute namespace="##other" processContents="lax"/>
</xs:complexType> </xs:complexType>
]]></sourcecode>
]]> </section>
</artwork> <section anchor="sec-extension" numbered="true" toc="default">
</figure> <name>XML Schema Extensibility</name>
</t> <t>
</section>
<section title="XML Schema extensibility" anchor="sec-extension">
<t>
The telepresence data model defined in this document is The telepresence data model defined in this document is
meant to be extensible. Extensions are accomplished by defining meant to be extensible. Extensions are accomplished by defining
elements or attributes qualified by namespaces other than elements or attributes qualified by namespaces other than
"urn:ietf:params:xml:ns:clue-info" and "urn:ietf:params:xml:ns:clue-info" and
"urn:ietf:params:xml:ns:vcard-4.0" for use wherever the "urn:ietf:params:xml:ns:vcard-4.0" for use wherever the
schema allows such extensions (i.e., where the XML Schema definition schema allows such extensions (i.e., where the XML Schema definition
specifies "anyAttribute" or "anyElement"). specifies "anyAttribute" or "anyElement").
Elements or attributes from unknown namespaces MUST be ignored. Elements or attributes from unknown namespaces <bcp14>MUST</bcp14> be ignored .
Extensibility was purposefully favored as much as possible based on Extensibility was purposefully favored as much as possible based on
expectations about custom implementations. Hence, the schema offers expectations about custom implementations. Hence, the schema offers
people enough flexibility as to define custom extensions, without people enough flexibility as to define custom extensions, without
losing compliance with the standard. This is achieved by leveraging losing compliance with the standard. This is achieved by leveraging
&lt;xs:any&gt; elements and &lt;xs:anyAttribute&gt; attributes, which &lt;xs:any&gt; elements and &lt;xs:anyAttribute&gt; attributes, which
is a common approach with schemas, still matching the UPA is a common approach with schemas, while still matching the
(Unique Particle Attribution) constraint. Unique Particle Attribution (UPA) constraint.
</t> </t>
<section title="Example of extension"> <section numbered="true" toc="default">
<t>When extending the CLUE data model, a new schema <name>Example of Extension</name>
<t>When extending the CLUE data model, a new schema
with a new namespace associated with it with a new namespace associated with it
needs to be specified. needs to be specified.
</t> </t>
<t> <t>
In the following, an example of extension is provided. The extension In the following, an example of extension is provided. The extension
defines a new audio capture attribute ("newAudioFeature") and defines a new audio capture attribute ("newAudioFeature") and
an attribute for characterizing the captures belonging to an an attribute for characterizing the captures belonging to an
"otherCaptureType" defined by the user. "otherCaptureType" defined by the user.
An XML document compliant with the extension is also included. An XML document compliant with the extension is also included.
The XML file results validated against the current CLUE data model The XML file results are validated against the current CLUE data model
schema. schema.
</t> </t>
<t> <sourcecode type="xml"><![CDATA[
<figure>
<artwork>
<![CDATA[
<?xml version="1.0" encoding="UTF-8" ?> <?xml version="1.0" encoding="UTF-8" ?>
<xs:schema <xs:schema
targetNamespace="urn:ietf:params:xml:ns:clue-info-ext" targetNamespace="urn:ietf:params:xml:ns:clue-info-ext"
xmlns:tns="urn:ietf:params:xml:ns:clue-info-ext" xmlns:tns="urn:ietf:params:xml:ns:clue-info-ext"
xmlns:clue-ext="urn:ietf:params:xml:ns:clue-info-ext" xmlns:clue-ext="urn:ietf:params:xml:ns:clue-info-ext"
xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns="urn:ietf:params:xml:ns:clue-info-ext" xmlns="urn:ietf:params:xml:ns:clue-info-ext"
xmlns:xcard="urn:ietf:params:xml:ns:vcard-4.0" xmlns:xcard="urn:ietf:params:xml:ns:vcard-4.0"
xmlns:info="urn:ietf:params:xml:ns:clue-info" xmlns:info="urn:ietf:params:xml:ns:clue-info"
elementFormDefault="qualified" elementFormDefault="qualified"
attributeFormDefault="unqualified"> attributeFormDefault="unqualified">
<!-- Import xcard XML schema --> <!-- Import xCard XML schema -->
<xs:import namespace="urn:ietf:params:xml:ns:vcard-4.0" <xs:import namespace="urn:ietf:params:xml:ns:vcard-4.0"
schemaLocation= schemaLocation=
"http://www.iana.org/assignments/xml-registry/schema/vcard-4.0.xsd"/> "https://www.iana.org/assignments/xml-registry/schema/
vcard-4.0.xsd"/>
<!-- Import CLUE XML schema --> <!-- Import CLUE XML schema -->
<xs:import namespace="urn:ietf:params:xml:ns:clue-info" <xs:import namespace="urn:ietf:params:xml:ns:clue-info"
schemaLocation="clue-data-model-schema.xsd"/> schemaLocation="clue-data-model-schema.xsd"/>
<!-- ELEMENT DEFINITIONS --> <!-- ELEMENT DEFINITIONS -->
<xs:element name="newAudioFeature" type="xs:string"/> <xs:element name="newAudioFeature" type="xs:string"/>
<xs:element name="otherMediaCaptureTypeFeature" type="xs:string"/> <xs:element name="otherMediaCaptureTypeFeature" type="xs:string"/>
</xs:schema> </xs:schema>
]]> ]]></sourcecode>
</artwork>
</figure> <sourcecode type="xml"><![CDATA[
</t>
<t>
<figure>
<artwork>
<![CDATA[
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<clueInfo xmlns="urn:ietf:params:xml:ns:clue-info" <clueInfo xmlns="urn:ietf:params:xml:ns:clue-info"
xmlns:ns2="urn:ietf:params:xml:ns:vcard-4.0" xmlns:ns2="urn:ietf:params:xml:ns:vcard-4.0"
xmlns:ns3="urn:ietf:params:xml:ns:clue-info-ext" xmlns:ns3="urn:ietf:params:xml:ns:clue-info-ext"
clueInfoID="NapoliRoom"> clueInfoID="NapoliRoom">
<mediaCaptures> <mediaCaptures>
<mediaCapture <mediaCapture
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:type="audioCaptureType" xsi:type="audioCaptureType"
captureID="AC0" captureID="AC0"
skipping to change at line 2538 skipping to change at line 2530
<encodingIDList> <encodingIDList>
<encodingID>ENC4</encodingID> <encodingID>ENC4</encodingID>
<encodingID>ENC5</encodingID> <encodingID>ENC5</encodingID>
</encodingIDList> </encodingIDList>
</encodingGroup> </encodingGroup>
</encodingGroups> </encodingGroups>
<captureScenes> <captureScenes>
<captureScene scale="unknown" sceneID="CS1"/> <captureScene scale="unknown" sceneID="CS1"/>
</captureScenes> </captureScenes>
</clueInfo> </clueInfo>
]]> ]]></sourcecode>
</artwork> </section>
</figure> </section>
</t> <section anchor="sec_security" numbered="true" toc="default">
</section> <name>Security Considerations</name>
</section> <t>
<section title="Security considerations" anchor="sec:security">
<t>
This document defines an XML Schema data model for telepresence This document defines an XML Schema data model for telepresence
scenarios. scenarios.
The modeled information is identified in the CLUE framework The modeled information is identified in the CLUE framework
as necessary in order to enable a full-fledged as necessary in order to enable a full-fledged
media stream negotiation and rendering. media stream negotiation and rendering.
Indeed, the XML elements herein defined are used within Indeed, the XML elements herein defined are used within
CLUE protocol messages to describe CLUE protocol messages to describe
both the media streams representing the Media Provider's telepresence both the media streams representing the Media Provider's telepresence
offer and the desired selection requested by the Media Consumer. offer and the desired selection requested by the Media Consumer.
Security concerns described in Security concerns described in
<xref target="I-D.ietf-clue-framework"/>, Section 15, apply to this <xref target="RFC8845" sectionFormat="comma" section="15"/> apply to this
document. document.
</t> </t>
<t> <t>
Data model information carried within CLUE messages SHOULD Data model information carried within CLUE messages <bcp14>SHOULD</bcp14>
be accessed only by authenticated endpoints. be accessed only by authenticated endpoints.
Indeed, authenticated access is strongly advisable, especially if you Indeed, authenticated access is strongly advisable, especially if you
convey information about individuals (&lt;personalInfo&gt;) and/or convey information about individuals (&lt;personalInfo&gt;) and/or
scenes (&lt;sceneInformation&gt;). scenes (&lt;sceneInformation&gt;).
There might be more exceptions, depending on the level of criticality There might be more exceptions, depending on the level of criticality
that is associated with the setup and configuration of a specific that is associated with the setup and configuration of a specific
session. In principle, one might even decide that no protection at all session. In principle, one might even decide that no protection at all
is needed for a particular session; here is why authentication is needed for a particular session; here is why authentication
has not been identified as a mandatory requirement. has not been identified as a mandatory requirement.
</t> </t>
<t>
<t>
Going deeper into details, some information published by the Media Going deeper into details, some information published by the Media
Provider might reveal sensitive data about who and what is represented Provider might reveal sensitive data about who and what is represented
in the transmitted streams. in the transmitted streams.
The vCard included in the &lt;personInfo&gt; The vCard included in the &lt;personInfo&gt;
elements (<xref target="sub-sec-participantInfo"/>) elements (<xref target="sub-sec-participantInfo" format="default"/>)
mandatorily contains the identity of the represented person. mandatorily contains the identity of the represented person.
Optionally vCards can also carry the person's contact addresses, Optionally, vCards can also carry the person's contact addresses,
together with his/her photo and other personal data. Similar together with their photo and other personal data. Similar
privacy-critical information can be conveyed by means of privacy-critical information can be conveyed by means of
&lt;sceneInformation&gt; elements (<xref target="sec-scene-info"/>) &lt;sceneInformation&gt; elements (<xref target="sec-scene-info" format="default "/>)
describing the capture scenes. describing the capture scenes.
The &lt;description&gt; elements (<xref target="sec-description"/>) also The &lt;description&gt; elements (<xref target="sec-description" format="default
can specify details about the content of media captures, capture scenes "/>) also
can specify details about the content of media captures, capture scenes,
and scene views that should be protected. and scene views that should be protected.
</t> </t>
<t>
<t>
Integrity attacks to the data model information encapsulated Integrity attacks to the data model information encapsulated
in CLUE messages can invalidate the success of the telepresence in CLUE messages can invalidate the success of the telepresence
session's setup by misleading the Media Consumer's and Media Provider's session's setup by misleading the Media Consumer's and Media Provider's
interpretation of the offered and desired media streams. interpretation of the offered and desired media streams.
</t><t> </t>
<t>
The assurance of the authenticated access and of the integrity of the The assurance of the authenticated access and of the integrity of the
data model information is up to the involved transport mechanisms, data model information is up to the involved transport mechanisms,
namely the CLUE protocol namely the CLUE protocol
<xref target="I-D.ietf-clue-protocol"/> <xref target="RFC8847" format="default"/>
and the CLUE data channel <xref target="I-D.ietf-clue-datachannel"/>. and the CLUE data channel <xref target="RFC8850" format="default"/>.
</t> </t>
<t>
<t>
XML parsers need to be robust with respect to malformed documents. XML parsers need to be robust with respect to malformed documents.
Reading malformed documents from unknown or untrusted sources could Reading malformed documents from unknown or untrusted sources could
result in an attacker gaining privileges of the user running the XML result in an attacker gaining privileges of the user running the XML
parser. In an extreme situation, the entire machine could be parser. In an extreme situation, the entire machine could be
compromised. compromised.
</t> </t>
</section>
<section numbered="true" toc="default">
<name>IANA Considerations</name>
</section> <!--[rfced] Fyi, we removed 'MIME' from the IANA section per guidance
on the IANA website, which indicates that 'MIME' is now
obsolete. If you have any concerns or objections, please let us
know.
<section title="IANA considerations"> One example
<t>
This document registers a new XML namespace, a new XML schema, the MIME
type for the schema and four new registries associated, respectively,
with acceptable &lt;view&gt;, &lt;presentation&gt;,
&lt;sensitivityPattern&gt; and &lt;personType&gt; values.
</t>
<section title="XML namespace registration"> Original:
<t> This document registers a new XML namespace, a new XML schema, the
</t> MIME type for the schema and four new registries associated,
This section registers a new XML namespace: respectively, with acceptable <view>, <presentation>,
<t> <sensitivityPattern> and <personType> values.
<t>
URI: urn:ietf:params:xml:ns:clue-info
</t>
<t>
Registrant Contact: IETF CLUE Working Group &lt;clue@ietf.org&gt;,
Roberta Presta &lt;roberta.presta@unina.it&gt;
</t>
<t>XML:</t>
<figure>
<artwork>
<![CDATA[
BEGIN
Current:
This document registers a new XML namespace, a new XML schema, the
media type for the schema, and four new registries associated,
respectively, with acceptable <view>, <presentation>,
<sensitivityPattern>, and <personType> values.
-->
<t>
This document registers a new XML namespace, a new XML schema, the media
type for the schema, and four new registries associated, respectively,
with acceptable &lt;view&gt;, &lt;presentation&gt;,
&lt;sensitivityPattern&gt;, and &lt;personType&gt; values.
</t>
<section numbered="true" toc="default">
<name>XML Namespace Registration</name>
<dl newline="false" spacing="normal">
<dt>URI:</dt><dd>urn:ietf:params:xml:ns:clue-info</dd>
<dt>Registrant Contact:</dt><dd>IETF CLUE Working Group &lt;clue@ietf.org&gt;,
Roberta Presta &lt;roberta.presta@unina.it&gt;</dd>
<dt>XML:</dt><dd></dd>
</dl>
<sourcecode type="xml" markers="true"><![CDATA[
<?xml version="1.0"?> <?xml version="1.0"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN" <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN"
"http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd"> "http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"> <html xmlns="http://www.w3.org/1999/xhtml">
<head> <head>
<meta http-equiv="content-type" <meta http-equiv="content-type"
content="text/html;charset=iso-8859-1"/> content="text/html;charset=iso-8859-1"/>
<title> CLUE Data Model Namespace</title> <title>CLUE Data Model Namespace</title>
</head> </head>
<body> <body>
<h1>Namespace for CLUE Data Model</h1> <h1>Namespace for CLUE Data Model</h1>
<h2>urn:ietf:params:xml:ns:clue-info</h2> <h2>urn:ietf:params:xml:ns:clue-info</h2>
<p>See <p>See
<a href="http://www.rfc-editor.org/rfc/rfcXXXX.txt"> RFC XXXX</a>. <a href="https://www.rfc-editor.org/rfc/rfc8846.txt">RFC 8846</a>.
<!--[[NOTE TO IANA/RFC-EDITOR: Please update RFC URL
and replace XXXX with the RFC number for this specification.]]-->
</p> </p>
</body> </body>
</html> </html>
]]></sourcecode>
END </section>
]]> <section numbered="true" toc="default">
</artwork> <name>XML Schema Registration</name>
</figure> <t>
</t>
</section>
<section title="XML Schema registration">
<t>
This section registers an XML schema per the guidelines in This section registers an XML schema per the guidelines in
<xref target="RFC3688"/>. <xref target="RFC3688" format="default"/>.
</t>
<t>
URI:
urn:ietf:params:xml:schema:clue-info
</t>
<t>
Registrant Contact:
CLUE working group (clue@ietf.org),
Roberta Presta (roberta.presta@unina.it).
</t>
<t>
Schema:
The XML for this schema can be found as the entirety of
<xref target="sec-schema"/> of this document.
</t> </t>
<dl newline="false" spacing="normal">
<dt>URI:</dt><dd>urn:ietf:params:xml:schema:clue-info</dd>
</section> <dt>Registrant Contact:</dt>
<dd>CLUE Working Group (clue@ietf.org),
<section title='MIME Media Type Registration for Roberta Presta (roberta.presta@unina.it).</dd>
"application/clue_info+xml"'>
<t>This section registers the
<spanx style="verb">application/clue_info+xml</spanx> MIME type.
</t>
<t>To: ietf-types@iana.org</t> <dt>Schema:</dt>
<t>Subject: <dd>The XML for this schema can be found in its entirety in
Registration of MIME media type application/clue_info+xml <xref target="sec-schema" format="default"/> of this document.</dd>
</dl>
</section>
<section numbered="true" toc="default">
<name>Media Type Registration for "application/clue_info+xml"</name>
<t>This section registers the "application/clue_info+xml" media type.
</t> </t>
<t>MIME media type name: <dl newline="false" spacing="normal">
application</t> <dt>To:</dt><dd>ietf-types@iana.org</dd>
<t>MIME subtype name: clue_info+xml</t> <dt>Subject:</dt><dd>Registration of media type application/clue_info+xm
<t>Required parameters: (none)</t> l</dd>
<t>Optional parameters: charset <vspace/> <dt>Type name:</dt><dd>application</dd>
<dt>Subtype name:</dt><dd>clue_info+xml</dd>
<dt>Required parameters:</dt><dd>(none)</dd>
<dt>Optional parameters:</dt><dd>charset
Same as the charset parameter of "application/xml" as specified in Same as the charset parameter of "application/xml" as specified in
<xref target="RFC7303"/>, Section 3.2. <xref target="RFC7303" sectionFormat="comma" section="3.2"/>.</dd>
</t> <dt>Encoding considerations:</dt><dd>Same as the encoding considerations
<t>Encoding considerations: of
Same as the encoding considerations of "application/xml" as specified in <xref target="RFC7303" sectionFormat="comma" s
"application/xml" as specified in <xref target="RFC7303"/>, Section 3.2. ection="3.2"/>.
</t> </dd>
<t>Security considerations: <dt>Security considerations:</dt><dd>This content type is designed to ca
This content type is designed to carry rry
data related to telepresence information. Some of the data data related to telepresence information. Some of the data
could be considered private. This media type does not provide any could be considered private. This media type does not provide any
protection and thus other mechanisms such as those described in protection and thus other mechanisms such as those described in
<xref target="sec:security"/> <xref target="sec_security" format="default"/>
are required to protect the data. This media type does are required to protect the data. This media type does
not contain executable content. not contain executable content.
</t> </dd>
<t>Interoperability considerations: None. <dt>Interoperability considerations:</dt><dd>None.</dd>
</t> <dt>Published specification:</dt><dd>RFC 8846</dd>
<t>Published specification: <dt>Applications that use this media type:</dt><dd>CLUE-capable telepres
RFC XXXX ence
[[NOTE TO IANA/RFC-EDITOR: systems.</dd>
Please replace XXXX with the RFC number for this specification.]]
</t>
<t>Applications that use this media type: CLUE-capable telepresence
systems.
</t>
<t>Additional Information:
Magic Number(s): (none), <vspace/>
File extension(s): .clue, <vspace/>
Macintosh File Type Code(s): TEXT. <vspace/>
</t>
<t>Person &amp; email address to contact for further information:
Roberta Presta (roberta.presta@unina.it).
</t>
<t>Intended usage:
LIMITED USE
</t>
<t>Author/Change controller:
The IETF
</t>
<t>Other information:
This media type is a specialization of
application/xml <xref target="RFC7303"/>, and many of the considerations
described there also apply to application/clue_info+xml.
</t>
</section>
<section title="Registry for acceptable &lt;view&gt; values"> <dt>Additional Information:</dt>
<dd>
<t><br/></t>
<dl newline="false" spacing="compact">
<dt>Magic Number(s):</dt><dd>none</dd>
<dt>File extension(s):</dt><dd>.clue</dd>
<dt>Macintosh File Type Code(s):</dt><dd>TEXT</dd>
</dl>
</dd>
<t> <dt>Person &amp; email address to contact for further
IANA is requested to create a registry of acceptable values for the the information:</dt><dd>Roberta Presta (roberta.presta@unina.it).</dd>
&lt;view&gt; tag as defined in <xref target="sec-view"/>. <dt>Intended usage:</dt><dd>LIMITED USE</dd>
<dt>Author/Change controller:</dt><dd>The IETF</dd>
<dt>Other information:</dt><dd>This media type is a specialization of
"application/xml" <xref target="RFC7303" format="default"/>, and many of the con
siderations
described there also apply to "application/clue_info+xml".
</dd></dl>
</section>
<section numbered="true" toc="default">
<name>Registry for Acceptable &lt;view&gt; Values</name>
<t>
IANA has created a registry of acceptable values for the
&lt;view&gt; tag as defined in <xref target="sec-view" format="default"/>.
The initial values for this registry are "room", "table", "lectern", The initial values for this registry are "room", "table", "lectern",
"individual", and "audience". "individual", and "audience".
</t> </t>
<t>
<t> <!-- [rfced] RFC 5226 has been obsoleted by RFC 8126. We have replaced RFC
New values are assigned by Expert Review per <xref target="RFC5226"/>. 5226 with RFC 8126 accordingly. Please let us know any objections.
-->
New values are assigned by Expert Review per <xref target="RFC8126" format="defa
ult"/>.
This reviewer will ensure that the requested registry entry conforms to This reviewer will ensure that the requested registry entry conforms to
the prescribed formatting. the prescribed formatting.
</t> </t>
</section>
<t> <section numbered="true" toc="default">
IANA is further requested to update this draft with the URL to the new <name>Registry for Acceptable &lt;presentation&gt; Values</name>
registry in <xref target="sec-view"/>, marked as "TBD-IANA". <t>
</t> IANA has created a registry of acceptable values for the
</section>
<section title="Registry for acceptable &lt;presentation&gt; values">
<t>
IANA is requested to create a registry of acceptable values for the the
&lt;presentation&gt; tag as defined in &lt;presentation&gt; tag as defined in
<xref target="sec-presentation"/>. <xref target="sec-presentation" format="default"/>.
The initial values for this registry are "slides" and "images". The initial values for this registry are "slides" and "images".
</t> </t>
<t>
<t> New values are assigned by Expert Review per <xref target="RFC8126" format="defa
New values are assigned by Expert Review per <xref target="RFC5226"/>. ult"/>.
This reviewer will ensure that the requested registry entry conforms to This reviewer will ensure that the requested registry entry conforms to
the prescribed formatting. the prescribed formatting.
</t> </t>
</section>
<t> <section numbered="true" toc="default">
IANA is further requested to update this draft with the URL to the new <name>Registry for Acceptable &lt;sensitivityPattern&gt; Values</name>
registry in <xref target="sec-presentation"/>, marked as "TBD-IANA". <t>
</t> IANA has created a registry of acceptable values for the
</section>
<section title="Registry for acceptable &lt;sensitivityPattern&gt;
values">
<t>
IANA is requested to create a registry of acceptable values for the the
&lt;sensitivityPattern&gt; tag as defined in &lt;sensitivityPattern&gt; tag as defined in
<xref target="sec-sensitivity-pattern"/>. <xref target="sec-sensitivity-pattern" format="default"/>.
The initial values for this registry are "uni", "shotgun", "omni", The initial values for this registry are "uni", "shotgun", "omni",
"figure8", "cardioid" and "hyper-cardioid". "figure8", "cardioid", and "hyper-cardioid".
</t> </t>
<t>
<t> New values are assigned by Expert Review per <xref target="RFC8126" format="defa
New values are assigned by Expert Review per <xref target="RFC5226"/>. ult"/>.
This reviewer will ensure that the requested registry entry conforms to This reviewer will ensure that the requested registry entry conforms to
the prescribed formatting. the prescribed formatting.
</t> </t>
</section>
<t> <section numbered="true" toc="default">
IANA is further requested to update this draft with the URL to the new <name>Registry for Acceptable &lt;personType&gt; Values</name>
registry in <xref target="sec-sensitivity-pattern"/>, marked as "TBD-IANA". <t>
</t> IANA has created a registry of acceptable values for the
</section>
<section title="Registry for acceptable &lt;personType&gt; values">
<t>
IANA is requested to create a registry of acceptable values for the the
&lt;personType&gt; tag as defined in &lt;personType&gt; tag as defined in
<xref target="sub-sec-participantType"/>. <xref target="sub-sec-participantType" format="default"/>.
The initial values for this registry are "presenter", The initial values for this registry are "presenter",
"timekeeper", "attendee", "minute taker", "translator", "chairman", "timekeeper", "attendee", "minute taker", "translator", "chairman",
"vice-chairman", "observer". "vice-chairman", and "observer".
</t> </t>
<t>
<t> New values are assigned by Expert Review per <xref target="RFC8126" format="defa
New values are assigned by Expert Review per <xref target="RFC5226"/>. ult"/>.
This reviewer will ensure that the requested registry entry conforms to This reviewer will ensure that the requested registry entry conforms to
the prescribed formatting. the prescribed formatting.
</t> </t>
</section>
<t> </section>
IANA is further requested to update this draft with the URL to the new <section anchor="sec-XML-sample" numbered="true" toc="default">
registry in <xref target="sub-sec-participantType"/>, marked as <name>Sample XML File</name>
"TBD-IANA". <t>The following XML document represents a schema-compliant example
</t>
</section>
</section>
<section title="Sample XML file" anchor="sec-XML-sample">
<t>The following XML document represents a schema compliant example
of a CLUE telepresence scenario. of a CLUE telepresence scenario.
Taking inspiration from the examples described in Taking inspiration from the examples described in
the framework draft (<xref target="I-D.ietf-clue-framework"/>), the framework specification <xref target="RFC8845" format="default"/>,
it is provided the XML representation of an endpoint-style Media the XML representation of an endpoint-style Media
Provider's ADVERTISEMENT. Provider's ADVERTISEMENT is provided.
</t><t> </t>
<t>
There are three cameras, where the central one is also capable of There are three cameras, where the central one is also capable of
capturing a zoomed-out capturing a zoomed-out
view of the overall telepresence room. view of the overall telepresence room.
Besides the three video captures coming from the cameras, Besides the three video captures coming from the cameras,
the Media Provider makes available a further multi-content capture of the Media Provider makes available a further multicontent capture of
the loudest the loudest
segment of the room, segment of the room,
obtained by switching the video source across the three cameras. obtained by switching the video source across the three cameras.
For the sake of simplicity, only one audio capture is advertised for For the sake of simplicity, only one audio capture is advertised for
the audio of the whole room.</t> the audio of the whole room.</t>
<t> <t>
The three cameras are placed in front of three participants The three cameras are placed in front of three participants
(Alice, Bob and Ciccio), (Alice, Bob, and Ciccio),
whose vcard and conference role details are also provided. whose vCard and conference role details are also provided.
</t> </t>
<t> <t>
Media captures are arranged into four capture scene views: Media captures are arranged into four capture scene views:
</t> </t>
<t> <ol spacing="normal" type="1">
<list style="numbers"> <li>(VC0, VC1, VC2) - left, center, and right camera video captures
<t>(VC0, VC1, VC2) - left, center and right camera video captures </li>
</t> <li>(VC3) - video capture associated with loudest room segment</li>
<t>(VC3) - video capture associated with loudest room segment</t> <li>(VC4) - video capture zoomed-out view of all people in the room
<t>(VC4) - video capture zoomed out view of all people in the room </li>
</t> <li>(AC0) - main audio</li>
<t>(AC0) - main audio</t> </ol>
</list> <t>
</t>
<t>
There are two encoding groups: (i) EG0, for video encodings, and (ii) There are two encoding groups: (i) EG0, for video encodings, and (ii)
EG1, for audio encodings. EG1, for audio encodings.
</t> </t>
<t>As to the simultaneous sets, VC1 and VC4 cannot be transmitted
<t>As to the simultaneous sets, VC1 and VC4 cannot be transmitted
simultaneously simultaneously
since they are captured by the same device, i.e., the central camera since they are captured by the same device, i.e., the central camera
(VC4 is a zoomed-out view while (VC4 is a zoomed-out view while
VC1 is a focused view of the front participant). VC1 is a focused view of the front participant).
On the other hand, VC3 and VC4 cannot be simultaneous either, On the other hand, VC3 and VC4 cannot be simultaneous either,
since VC3, the loudest segment of the room, since VC3, the loudest segment of the room,
might be at a certain point in time focusing on the central might be at a certain point in time focusing on the central
part of the room, i.e., the same as VC1. part of the room, i.e., the same as VC1.
The simultaneous sets would then be the following: The simultaneous sets would then be the following:
<list style="hanging"> </t>
<t hangText="SS1"> <ul empty="true">
made by VC3 and all the captures in the first capture scene view <li>
(VC0,VC1,VC2); <dl newline="false" spacing="normal">
</t> <dt>SS1:</dt>
<t hangText="SS2"> <dd>made by VC3 and all the captures in the first capture scene view
made by VC0, VC2, VC4 (VC0,VC1,and VC2)
</t> </dd>
</list>
</t>
<figure> <dt>SS2:</dt>
<artwork> <dd>made by VC0, VC2, and VC4
</dd>
</dl>
</li>
</ul>
<![CDATA[ <sourcecode type="xml"><![CDATA[
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<clueInfo xmlns="urn:ietf:params:xml:ns:clue-info" <clueInfo xmlns="urn:ietf:params:xml:ns:clue-info"
xmlns:ns2="urn:ietf:params:xml:ns:vcard-4.0" xmlns:ns2="urn:ietf:params:xml:ns:vcard-4.0"
clueInfoID="NapoliRoom"> clueInfoID="NapoliRoom">
<mediaCaptures> <mediaCaptures>
<mediaCapture <mediaCapture
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:type="audioCaptureType" captureID="AC0" mediaType="audio"> xsi:type="audioCaptureType" captureID="AC0"
mediaType="audio">
<captureSceneIDREF>CS1</captureSceneIDREF> <captureSceneIDREF>CS1</captureSceneIDREF>
<spatialInformation> <spatialInformation>
<captureOrigin> <captureOrigin>
<capturePoint> <capturePoint>
<x>0.0</x> <x>0.0</x>
<y>0.0</y> <y>0.0</y>
<z>10.0</z> <z>10.0</z>
</capturePoint> </capturePoint>
<lineOfCapturePoint> <lineOfCapturePoint>
<x>0.0</x> <x>0.0</x>
<y>1.0</y> <y>1.0</y>
<z>10.0</z> <z>10.0</z>
</lineOfCapturePoint> </lineOfCapturePoint>
</captureOrigin> </captureOrigin>
</spatialInformation> </spatialInformation>
<individual>true</individual> <individual>true</individual>
<encGroupIDREF>EG1</encGroupIDREF> <encGroupIDREF>EG1</encGroupIDREF>
skipping to change at line 2957 skipping to change at line 2895
<mobility>static</mobility> <mobility>static</mobility>
<view>room</view> <view>room</view>
<capturedPeople> <capturedPeople>
<personIDREF>alice</personIDREF> <personIDREF>alice</personIDREF>
<personIDREF>bob</personIDREF> <personIDREF>bob</personIDREF>
<personIDREF>ciccio</personIDREF> <personIDREF>ciccio</personIDREF>
</capturedPeople> </capturedPeople>
</mediaCapture> </mediaCapture>
<mediaCapture <mediaCapture
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:type="videoCaptureType" captureID="VC0" mediaType="video"> xsi:type="videoCaptureType" captureID="VC0"
mediaType="video">
<captureSceneIDREF>CS1</captureSceneIDREF> <captureSceneIDREF>CS1</captureSceneIDREF>
<spatialInformation> <spatialInformation>
<captureOrigin> <captureOrigin>
<capturePoint> <capturePoint>
<x>-2.0</x> <x>-2.0</x>
<y>0.0</y> <y>0.0</y>
<z>10.0</z> <z>10.0</z>
</capturePoint> </capturePoint>
</captureOrigin> </captureOrigin>
<captureArea> <captureArea>
<bottomLeft> <bottomLeft>
<x>-3.0</x> <x>-3.0</x>
<y>20.0</y> <y>20.0</y>
<z>9.0</z> <z>9.0</z>
</bottomLeft> </bottomLeft>
<bottomRight> <bottomRight>
<x>-1.0</x> <x>-1.0</x>
<y>20.0</y> <y>20.0</y>
<z>9.0</z> <z>9.0</z>
</bottomRight> </bottomRight>
<topLeft> <topLeft>
<x>-3.0</x> <x>-3.0</x>
<y>20.0</y> <y>20.0</y>
<z>11.0</z> <z>11.0</z>
</topLeft> </topLeft>
<topRight> <topRight>
<x>-1.0</x> <x>-1.0</x>
<y>20.0</y> <y>20.0</y>
<z>11.0</z> <z>11.0</z>
</topRight> </topRight>
</captureArea> </captureArea>
</spatialInformation> </spatialInformation>
<individual>true</individual> <individual>true</individual>
<encGroupIDREF>EG0</encGroupIDREF> <encGroupIDREF>EG0</encGroupIDREF>
<description lang="en">left camera video capture <description lang="en">left camera video capture
</description> </description>
<priority>1</priority> <priority>1</priority>
<lang>it</lang> <lang>it</lang>
<mobility>static</mobility> <mobility>static</mobility>
<view>individual</view> <view>individual</view>
<capturedPeople> <capturedPeople>
<personIDREF>ciccio</personIDREF> <personIDREF>ciccio</personIDREF>
</capturedPeople> </capturedPeople>
</mediaCapture> </mediaCapture>
<mediaCapture <mediaCapture
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:type="videoCaptureType" captureID="VC1" mediaType="video"> xsi:type="videoCaptureType" captureID="VC1"
mediaType="video">
<captureSceneIDREF>CS1</captureSceneIDREF> <captureSceneIDREF>CS1</captureSceneIDREF>
<spatialInformation> <spatialInformation>
<captureOrigin> <captureOrigin>
<capturePoint> <capturePoint>
<x>0.0</x> <x>0.0</x>
<y>0.0</y> <y>0.0</y>
<z>10.0</z> <z>10.0</z>
</capturePoint> </capturePoint>
</captureOrigin> </captureOrigin>
<captureArea> <captureArea>
<bottomLeft> <bottomLeft>
<x>-1.0</x> <x>-1.0</x>
<y>20.0</y> <y>20.0</y>
<z>9.0</z> <z>9.0</z>
</bottomLeft> </bottomLeft>
<bottomRight> <bottomRight>
<x>1.0</x> <x>1.0</x>
<y>20.0</y> <y>20.0</y>
<z>9.0</z> <z>9.0</z>
</bottomRight> </bottomRight>
<topLeft> <topLeft>
<x>-1.0</x> <x>-1.0</x>
<y>20.0</y> <y>20.0</y>
<z>11.0</z> <z>11.0</z>
</topLeft> </topLeft>
<topRight> <topRight>
<x>1.0</x> <x>1.0</x>
<y>20.0</y> <y>20.0</y>
<z>11.0</z> <z>11.0</z>
</topRight> </topRight>
</captureArea> </captureArea>
</spatialInformation> </spatialInformation>
<individual>true</individual> <individual>true</individual>
<encGroupIDREF>EG0</encGroupIDREF> <encGroupIDREF>EG0</encGroupIDREF>
<description lang="en">central camera video capture <description lang="en">central camera video capture
</description> </description>
<priority>1</priority> <priority>1</priority>
<lang>it</lang> <lang>it</lang>
<mobility>static</mobility> <mobility>static</mobility>
<view>individual</view> <view>individual</view>
<capturedPeople> <capturedPeople>
<personIDREF>alice</personIDREF> <personIDREF>alice</personIDREF>
</capturedPeople> </capturedPeople>
</mediaCapture> </mediaCapture>
<mediaCapture <mediaCapture
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:type="videoCaptureType" captureID="VC2" mediaType="video"> xsi:type="videoCaptureType" captureID="VC2"
mediaType="video">
<captureSceneIDREF>CS1</captureSceneIDREF> <captureSceneIDREF>CS1</captureSceneIDREF>
<spatialInformation> <spatialInformation>
<captureOrigin> <captureOrigin>
<capturePoint> <capturePoint>
<x>2.0</x> <x>2.0</x>
<y>0.0</y> <y>0.0</y>
<z>10.0</z> <z>10.0</z>
</capturePoint> </capturePoint>
</captureOrigin> </captureOrigin>
<captureArea> <captureArea>
<bottomLeft> <bottomLeft>
<x>1.0</x> <x>1.0</x>
<y>20.0</y> <y>20.0</y>
<z>9.0</z> <z>9.0</z>
</bottomLeft> </bottomLeft>
<bottomRight> <bottomRight>
<x>3.0</x> <x>3.0</x>
<y>20.0</y> <y>20.0</y>
<z>9.0</z> <z>9.0</z>
</bottomRight> </bottomRight>
<topLeft> <topLeft>
<x>1.0</x> <x>1.0</x>
<y>20.0</y> <y>20.0</y>
<z>11.0</z> <z>11.0</z>
</topLeft> </topLeft>
<topRight> <topRight>
<x>3.0</x> <x>3.0</x>
<y>20.0</y> <y>20.0</y>
<z>11.0</z> <z>11.0</z>
</topRight> </topRight>
</captureArea> </captureArea>
</spatialInformation> </spatialInformation>
<individual>true</individual> <individual>true</individual>
<encGroupIDREF>EG0</encGroupIDREF> <encGroupIDREF>EG0</encGroupIDREF>
<description lang="en">right camera video capture <description lang="en">right camera video capture
</description> </description>
<priority>1</priority> <priority>1</priority>
<lang>it</lang> <lang>it</lang>
<mobility>static</mobility> <mobility>static</mobility>
<view>individual</view> <view>individual</view>
<capturedPeople> <capturedPeople>
<personIDREF>bob</personIDREF> <personIDREF>bob</personIDREF>
</capturedPeople> </capturedPeople>
</mediaCapture> </mediaCapture>
<mediaCapture <mediaCapture
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:type="videoCaptureType" captureID="VC3" mediaType="video"> xsi:type="videoCaptureType" captureID="VC3"
mediaType="video">
<captureSceneIDREF>CS1</captureSceneIDREF> <captureSceneIDREF>CS1</captureSceneIDREF>
<spatialInformation> <spatialInformation>
<captureArea> <captureArea>
<bottomLeft> <bottomLeft>
<x>-3.0</x> <x>-3.0</x>
<y>20.0</y> <y>20.0</y>
<z>9.0</z> <z>9.0</z>
</bottomLeft> </bottomLeft>
<bottomRight> <bottomRight>
<x>3.0</x> <x>3.0</x>
<y>20.0</y> <y>20.0</y>
<z>9.0</z> <z>9.0</z>
</bottomRight> </bottomRight>
<topLeft> <topLeft>
<x>-3.0</x> <x>-3.0</x>
<y>20.0</y> <y>20.0</y>
<z>11.0</z> <z>11.0</z>
</topLeft> </topLeft>
<topRight> <topRight>
<x>3.0</x> <x>3.0</x>
<y>20.0</y> <y>20.0</y>
<z>11.0</z> <z>11.0</z>
</topRight> </topRight>
</captureArea> </captureArea>
</spatialInformation> </spatialInformation>
<content> <content>
<sceneViewIDREF>SE1</sceneViewIDREF> <sceneViewIDREF>SE1</sceneViewIDREF>
</content> </content>
<policy>SoundLevel:0</policy> <policy>SoundLevel:0</policy>
<encGroupIDREF>EG0</encGroupIDREF> <encGroupIDREF>EG0</encGroupIDREF>
<description lang="en">loudest room segment</description> <description lang="en">loudest room segment</description>
<priority>2</priority> <priority>2</priority>
<lang>it</lang> <lang>it</lang>
<mobility>static</mobility> <mobility>static</mobility>
<view>individual</view> <view>individual</view>
</mediaCapture> </mediaCapture>
<mediaCapture <mediaCapture
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:type="videoCaptureType" captureID="VC4" mediaType="video"> xsi:type="videoCaptureType" captureID="VC4"
mediaType="video">
<captureSceneIDREF>CS1</captureSceneIDREF> <captureSceneIDREF>CS1</captureSceneIDREF>
<spatialInformation> <spatialInformation>
<captureOrigin> <captureOrigin>
<capturePoint> <capturePoint>
<x>0.0</x> <x>0.0</x>
<y>0.0</y> <y>0.0</y>
<z>10.0</z> <z>10.0</z>
</capturePoint> </capturePoint>
</captureOrigin> </captureOrigin>
<captureArea> <captureArea>
<bottomLeft> <bottomLeft>
<x>-3.0</x> <x>-3.0</x>
<y>20.0</y> <y>20.0</y>
<z>7.0</z> <z>7.0</z>
</bottomLeft> </bottomLeft>
<bottomRight> <bottomRight>
<x>3.0</x> <x>3.0</x>
<y>20.0</y> <y>20.0</y>
<z>7.0</z> <z>7.0</z>
</bottomRight> </bottomRight>
<topLeft> <topLeft>
<x>-3.0</x> <x>-3.0</x>
<y>20.0</y> <y>20.0</y>
<z>13.0</z> <z>13.0</z>
</topLeft> </topLeft>
<topRight> <topRight>
<x>3.0</x> <x>3.0</x>
<y>20.0</y> <y>20.0</y>
<z>13.0</z> <z>13.0</z>
</topRight> </topRight>
</captureArea> </captureArea>
</spatialInformation> </spatialInformation>
<individual>true</individual> <individual>true</individual>
<encGroupIDREF>EG0</encGroupIDREF> <encGroupIDREF>EG0</encGroupIDREF>
<description lang="en">zoomed out view of all people in the <description lang="en">zoomed-out view of all people
room</description> in the room</description>
<priority>2</priority> <priority>2</priority>
<lang>it</lang> <lang>it</lang>
<mobility>static</mobility> <mobility>static</mobility>
<view>room</view> <view>room</view>
<capturedPeople> <capturedPeople>
<personIDREF>alice</personIDREF> <personIDREF>alice</personIDREF>
<personIDREF>bob</personIDREF> <personIDREF>bob</personIDREF>
<personIDREF>ciccio</personIDREF> <personIDREF>ciccio</personIDREF>
</capturedPeople> </capturedPeople>
</mediaCapture> </mediaCapture>
skipping to change at line 3269 skipping to change at line 3212
<personInfo> <personInfo>
<ns2:fn> <ns2:fn>
<ns2:text>Ciccio</ns2:text> <ns2:text>Ciccio</ns2:text>
</ns2:fn> </ns2:fn>
</personInfo> </personInfo>
<personType>chairman</personType> <personType>chairman</personType>
<personType>timekeeper</personType> <personType>timekeeper</personType>
</person> </person>
</people> </people>
</clueInfo> </clueInfo>
]]></sourcecode>
]]> </section>
</artwork> <section anchor="sec-MCC-sample" numbered="true" toc="default">
</figure> <name>MCC Example</name>
</section> <t>
<section title="MCC example" anchor="sec-MCC-sample">
<t>
Enhancing the scenario presented in the previous example, the Media Enhancing the scenario presented in the previous example, the Media
Provider is able to advertise a composed capture VC7 made by a big Provider is able to advertise a composed capture VC7 made by a big
picture representing the current speaker (VC3) and two picture representing the current speaker (VC3) and two
picture-in-picture boxes representing the previous speakers (the picture-in-picture boxes representing the previous speakers (the
previous one -VC5- and the oldest one -VC6). previous one, VC5, and the oldest one, VC6).
The provider does not want to instantiate and send VC5 and VC6, so it The provider does not want to instantiate and send VC5 and VC6, so it
does not associate any encoding group with them. Their XML does not associate any encoding group with them. Their XML
representations are provided for enabling the description of VC7. representations are provided for enabling the description of VC7.
</t> </t>
<t>A possible description for that scenario could be the following:</t>
<figure>
<artwork>
<![CDATA[ <!-- [rfced] Section 10.6: We find "penultimate loudest room segment"
and "last but two loudest room segment" difficult to follow. If
the suggested text is not correct, please clarify.
This pertains to RFC-to-be 8847 (draft-ietf-clue-protocol) as well.
Original:
<policy>SoundLevel:1</policy>
<description lang="en">penultimate loudest room segment
</description>
...
<policy>SoundLevel:2</policy>
<description lang="en">last but two loudest room segment
</description>
Perhaps:
<policy>SoundLevel:1</policy>
<description lang="en">previous loudest room segment per the
most recent iteration of the sound level detection algorithm
</description>
...
<policy>SoundLevel:2</policy>
<description lang="en">previous loudest room segment per the
second most recent iteration of the sound level detection
algorithm
</description> -->
<t>A possible description for that scenario could be the following:</t>
<sourcecode type="xml"><![CDATA[
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<clueInfo xmlns="urn:ietf:params:xml:ns:clue-info" <clueInfo xmlns="urn:ietf:params:xml:ns:clue-info"
xmlns:ns2="urn:ietf:params:xml:ns:vcard-4.0" clueInfoID="NapoliRoom"> xmlns:ns2="urn:ietf:params:xml:ns:vcard-4.0" clueInfoID="NapoliRoom">
<mediaCaptures> <mediaCaptures>
<mediaCapture <mediaCapture
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:type="audioCaptureType" captureID="AC0" mediaType="audio"> xsi:type="audioCaptureType" captureID="AC0"
mediaType="audio">
<captureSceneIDREF>CS1</captureSceneIDREF> <captureSceneIDREF>CS1</captureSceneIDREF>
<spatialInformation> <spatialInformation>
<captureOrigin> <captureOrigin>
<capturePoint> <capturePoint>
<x>0.0</x> <x>0.0</x>
<y>0.0</y> <y>0.0</y>
<z>10.0</z> <z>10.0</z>
</capturePoint> </capturePoint>
<lineOfCapturePoint> <lineOfCapturePoint>
<x>0.0</x> <x>0.0</x>
<y>1.0</y> <y>1.0</y>
<z>10.0</z> <z>10.0</z>
</lineOfCapturePoint> </lineOfCapturePoint>
</captureOrigin> </captureOrigin>
</spatialInformation> </spatialInformation>
<individual>true</individual> <individual>true</individual>
<encGroupIDREF>EG1</encGroupIDREF> <encGroupIDREF>EG1</encGroupIDREF>
skipping to change at line 3330 skipping to change at line 3295
<mobility>static</mobility> <mobility>static</mobility>
<view>room</view> <view>room</view>
<capturedPeople> <capturedPeople>
<personIDREF>alice</personIDREF> <personIDREF>alice</personIDREF>
<personIDREF>bob</personIDREF> <personIDREF>bob</personIDREF>
<personIDREF>ciccio</personIDREF> <personIDREF>ciccio</personIDREF>
</capturedPeople> </capturedPeople>
</mediaCapture> </mediaCapture>
<mediaCapture <mediaCapture
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:type="videoCaptureType" captureID="VC0" mediaType="video"> xsi:type="videoCaptureType" captureID="VC0"
mediaType="video">
<captureSceneIDREF>CS1</captureSceneIDREF> <captureSceneIDREF>CS1</captureSceneIDREF>
<spatialInformation> <spatialInformation>
<captureOrigin> <captureOrigin>
<capturePoint> <capturePoint>
<x>0.5</x> <x>0.5</x>
<y>1.0</y> <y>1.0</y>
<z>0.5</z> <z>0.5</z>
</capturePoint> </capturePoint>
<lineOfCapturePoint> <lineOfCapturePoint>
<x>0.5</x> <x>0.5</x>
<y>0.0</y> <y>0.0</y>
<z>0.5</z> <z>0.5</z>
</lineOfCapturePoint> </lineOfCapturePoint>
</captureOrigin> </captureOrigin>
</spatialInformation> </spatialInformation>
<individual>true</individual> <individual>true</individual>
<encGroupIDREF>EG0</encGroupIDREF> <encGroupIDREF>EG0</encGroupIDREF>
skipping to change at line 3360 skipping to change at line 3326
<priority>1</priority> <priority>1</priority>
<lang>it</lang> <lang>it</lang>
<mobility>static</mobility> <mobility>static</mobility>
<view>individual</view> <view>individual</view>
<capturedPeople> <capturedPeople>
<personIDREF>ciccio</personIDREF> <personIDREF>ciccio</personIDREF>
</capturedPeople> </capturedPeople>
</mediaCapture> </mediaCapture>
<mediaCapture <mediaCapture
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:type="videoCaptureType" captureID="VC1" mediaType="video"> xsi:type="videoCaptureType" captureID="VC1"
mediaType="video">
<captureSceneIDREF>CS1</captureSceneIDREF> <captureSceneIDREF>CS1</captureSceneIDREF>
<spatialInformation> <spatialInformation>
<captureOrigin> <captureOrigin>
<capturePoint> <capturePoint>
<x>0.0</x> <x>0.0</x>
<y>0.0</y> <y>0.0</y>
<z>10.0</z> <z>10.0</z>
</capturePoint> </capturePoint>
</captureOrigin> </captureOrigin>
<captureArea> <captureArea>
<bottomLeft> <bottomLeft>
<x>-1.0</x> <x>-1.0</x>
<y>20.0</y> <y>20.0</y>
<z>9.0</z> <z>9.0</z>
</bottomLeft> </bottomLeft>
<bottomRight> <bottomRight>
<x>1.0</x> <x>1.0</x>
<y>20.0</y> <y>20.0</y>
<z>9.0</z> <z>9.0</z>
</bottomRight> </bottomRight>
<topLeft> <topLeft>
<x>-1.0</x> <x>-1.0</x>
<y>20.0</y> <y>20.0</y>
<z>11.0</z> <z>11.0</z>
</topLeft> </topLeft>
<topRight> <topRight>
<x>1.0</x> <x>1.0</x>
<y>20.0</y> <y>20.0</y>
<z>11.0</z> <z>11.0</z>
</topRight> </topRight>
</captureArea> </captureArea>
</spatialInformation> </spatialInformation>
<individual>true</individual> <individual>true</individual>
<encGroupIDREF>EG0</encGroupIDREF> <encGroupIDREF>EG0</encGroupIDREF>
<description lang="en">central camera video capture <description lang="en">central camera video capture
</description> </description>
<priority>1</priority> <priority>1</priority>
<lang>it</lang> <lang>it</lang>
<mobility>static</mobility> <mobility>static</mobility>
<view>individual</view> <view>individual</view>
<capturedPeople> <capturedPeople>
<personIDREF>alice</personIDREF> <personIDREF>alice</personIDREF>
</capturedPeople> </capturedPeople>
</mediaCapture> </mediaCapture>
<mediaCapture <mediaCapture
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:type="videoCaptureType" captureID="VC2" mediaType="video"> xsi:type="videoCaptureType" captureID="VC2"
mediaType="video">
<captureSceneIDREF>CS1</captureSceneIDREF> <captureSceneIDREF>CS1</captureSceneIDREF>
<spatialInformation> <spatialInformation>
<captureOrigin> <captureOrigin>
<capturePoint> <capturePoint>
<x>2.0</x> <x>2.0</x>
<y>0.0</y> <y>0.0</y>
<z>10.0</z> <z>10.0</z>
</capturePoint> </capturePoint>
</captureOrigin> </captureOrigin>
<captureArea> <captureArea>
<bottomLeft> <bottomLeft>
<x>1.0</x> <x>1.0</x>
<y>20.0</y> <y>20.0</y>
<z>9.0</z> <z>9.0</z>
</bottomLeft> </bottomLeft>
<bottomRight> <bottomRight>
<x>3.0</x> <x>3.0</x>
<y>20.0</y> <y>20.0</y>
<z>9.0</z> <z>9.0</z>
</bottomRight> </bottomRight>
<topLeft> <topLeft>
<x>1.0</x> <x>1.0</x>
<y>20.0</y> <y>20.0</y>
<z>11.0</z> <z>11.0</z>
</topLeft> </topLeft>
<topRight> <topRight>
<x>3.0</x> <x>3.0</x>
<y>20.0</y> <y>20.0</y>
<z>11.0</z> <z>11.0</z>
</topRight> </topRight>
</captureArea> </captureArea>
</spatialInformation> </spatialInformation>
<individual>true</individual> <individual>true</individual>
<encGroupIDREF>EG0</encGroupIDREF> <encGroupIDREF>EG0</encGroupIDREF>
<description lang="en">right camera video capture <description lang="en">right camera video capture
</description> </description>
<priority>1</priority> <priority>1</priority>
<lang>it</lang> <lang>it</lang>
<mobility>static</mobility> <mobility>static</mobility>
<view>individual</view> <view>individual</view>
<capturedPeople> <capturedPeople>
<personIDREF>bob</personIDREF> <personIDREF>bob</personIDREF>
</capturedPeople> </capturedPeople>
</mediaCapture> </mediaCapture>
<mediaCapture <mediaCapture
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:type="videoCaptureType" captureID="VC3" mediaType="video"> xsi:type="videoCaptureType" captureID="VC3"
mediaType="video">
<captureSceneIDREF>CS1</captureSceneIDREF> <captureSceneIDREF>CS1</captureSceneIDREF>
<spatialInformation> <spatialInformation>
<captureArea> <captureArea>
<bottomLeft> <bottomLeft>
<x>-3.0</x> <x>-3.0</x>
<y>20.0</y> <y>20.0</y>
<z>9.0</z> <z>9.0</z>
</bottomLeft> </bottomLeft>
<bottomRight> <bottomRight>
<x>3.0</x> <x>3.0</x>
<y>20.0</y> <y>20.0</y>
<z>9.0</z> <z>9.0</z>
</bottomRight> </bottomRight>
<topLeft> <topLeft>
<x>-3.0</x> <x>-3.0</x>
<y>20.0</y> <y>20.0</y>
<z>11.0</z> <z>11.0</z>
</topLeft> </topLeft>
<topRight> <topRight>
<x>3.0</x> <x>3.0</x>
<y>20.0</y> <y>20.0</y>
<z>11.0</z> <z>11.0</z>
</topRight> </topRight>
</captureArea> </captureArea>
</spatialInformation> </spatialInformation>
<content> <content>
<sceneViewIDREF>SE1</sceneViewIDREF> <sceneViewIDREF>SE1</sceneViewIDREF>
</content> </content>
<policy>SoundLevel:0</policy> <policy>SoundLevel:0</policy>
<encGroupIDREF>EG0</encGroupIDREF> <encGroupIDREF>EG0</encGroupIDREF>
<description lang="en">loudest room segment</description> <description lang="en">loudest room segment</description>
<priority>2</priority> <priority>2</priority>
<lang>it</lang> <lang>it</lang>
<mobility>static</mobility> <mobility>static</mobility>
<view>individual</view> <view>individual</view>
</mediaCapture> </mediaCapture>
<mediaCapture <mediaCapture
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:type="videoCaptureType" captureID="VC4" mediaType="video"> xsi:type="videoCaptureType" captureID="VC4"
mediaType="video">
<captureSceneIDREF>CS1</captureSceneIDREF> <captureSceneIDREF>CS1</captureSceneIDREF>
<spatialInformation> <spatialInformation>
<captureOrigin> <captureOrigin>
<capturePoint> <capturePoint>
<x>0.0</x> <x>0.0</x>
<y>0.0</y> <y>0.0</y>
<z>10.0</z> <z>10.0</z>
</capturePoint> </capturePoint>
</captureOrigin> </captureOrigin>
<captureArea> <captureArea>
<bottomLeft> <bottomLeft>
<x>-3.0</x> <x>-3.0</x>
<y>20.0</y> <y>20.0</y>
<z>7.0</z> <z>7.0</z>
</bottomLeft> </bottomLeft>
<bottomRight> <bottomRight>
<x>3.0</x> <x>3.0</x>
<y>20.0</y> <y>20.0</y>
<z>7.0</z> <z>7.0</z>
</bottomRight> </bottomRight>
<topLeft> <topLeft>
<x>-3.0</x> <x>-3.0</x>
<y>20.0</y> <y>20.0</y>
<z>13.0</z> <z>13.0</z>
</topLeft> </topLeft>
<topRight> <topRight>
<x>3.0</x> <x>3.0</x>
<y>20.0</y> <y>20.0</y>
<z>13.0</z> <z>13.0</z>
</topRight> </topRight>
</captureArea> </captureArea>
</spatialInformation> </spatialInformation>
<individual>true</individual> <individual>true</individual>
<encGroupIDREF>EG0</encGroupIDREF> <encGroupIDREF>EG0</encGroupIDREF>
<description lang="en"> <description lang="en">
zoomed out view of all people in the room zoomed-out view of all people in the room
</description> </description>
<priority>2</priority> <priority>2</priority>
<lang>it</lang> <lang>it</lang>
<mobility>static</mobility> <mobility>static</mobility>
<view>room</view> <view>room</view>
<capturedPeople> <capturedPeople>
<personIDREF>alice</personIDREF> <personIDREF>alice</personIDREF>
<personIDREF>bob</personIDREF> <personIDREF>bob</personIDREF>
<personIDREF>ciccio</personIDREF> <personIDREF>ciccio</personIDREF>
</capturedPeople> </capturedPeople>
</mediaCapture> </mediaCapture>
<mediaCapture <mediaCapture
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:type="videoCaptureType" captureID="VC5" mediaType="video"> xsi:type="videoCaptureType" captureID="VC5"
mediaType="video">
<captureSceneIDREF>CS1</captureSceneIDREF> <captureSceneIDREF>CS1</captureSceneIDREF>
<spatialInformation> <spatialInformation>
<captureArea> <captureArea>
<bottomLeft> <bottomLeft>
<x>-3.0</x> <x>-3.0</x>
<y>20.0</y> <y>20.0</y>
<z>9.0</z> <z>9.0</z>
</bottomLeft> </bottomLeft>
<bottomRight> <bottomRight>
<x>3.0</x> <x>3.0</x>
<y>20.0</y> <y>20.0</y>
<z>9.0</z> <z>9.0</z>
</bottomRight> </bottomRight>
<topLeft> <topLeft>
<x>-3.0</x> <x>-3.0</x>
<y>20.0</y> <y>20.0</y>
<z>11.0</z> <z>11.0</z>
</topLeft> </topLeft>
<topRight> <topRight>
<x>3.0</x> <x>3.0</x>
<y>20.0</y> <y>20.0</y>
<z>11.0</z> <z>11.0</z>
</topRight> </topRight>
</captureArea> </captureArea>
</spatialInformation> </spatialInformation>
<content> <content>
<sceneViewIDREF>SE1</sceneViewIDREF> <sceneViewIDREF>SE1</sceneViewIDREF>
</content> </content>
<policy>SoundLevel:1</policy> <policy>SoundLevel:1</policy>
<description lang="en">penultimate loudest room segment <description lang="en">penultimate loudest room segment
</description> </description>
<lang>it</lang> <lang>it</lang>
<mobility>static</mobility> <mobility>static</mobility>
<view>individual</view> <view>individual</view>
</mediaCapture> </mediaCapture>
<mediaCapture <mediaCapture
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:type="videoCaptureType" captureID="VC6" mediaType="video"> xsi:type="videoCaptureType" captureID="VC6"
mediaType="video">
<captureSceneIDREF>CS1</captureSceneIDREF> <captureSceneIDREF>CS1</captureSceneIDREF>
<spatialInformation> <spatialInformation>
<captureArea> <captureArea>
<bottomLeft> <bottomLeft>
<x>-3.0</x> <x>-3.0</x>
<y>20.0</y> <y>20.0</y>
<z>9.0</z> <z>9.0</z>
</bottomLeft> </bottomLeft>
<bottomRight> <bottomRight>
<x>3.0</x> <x>3.0</x>
<y>20.0</y> <y>20.0</y>
<z>9.0</z> <z>9.0</z>
</bottomRight> </bottomRight>
<topLeft> <topLeft>
<x>-3.0</x> <x>-3.0</x>
<y>20.0</y> <y>20.0</y>
<z>11.0</z> <z>11.0</z>
</topLeft> </topLeft>
<topRight> <topRight>
<x>3.0</x> <x>3.0</x>
<y>20.0</y> <y>20.0</y>
<z>11.0</z> <z>11.0</z>
</topRight> </topRight>
</captureArea> </captureArea>
</spatialInformation> </spatialInformation>
<content> <content>
<sceneViewIDREF>SE1</sceneViewIDREF> <sceneViewIDREF>SE1</sceneViewIDREF>
</content> </content>
<policy>SoundLevel:2</policy> <policy>SoundLevel:2</policy>
<description lang="en">last but two loudest room segment <description lang="en">last but two loudest room segment
</description> </description>
<lang>it</lang> <lang>it</lang>
<mobility>static</mobility> <mobility>static</mobility>
<view>individual</view> <view>individual</view>
</mediaCapture> </mediaCapture>
<mediaCapture <mediaCapture
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:type="videoCaptureType" captureID="VC7" mediaType="video"> xsi:type="videoCaptureType" captureID="VC7"
mediaType="video">
<captureSceneIDREF>CS1</captureSceneIDREF> <captureSceneIDREF>CS1</captureSceneIDREF>
<spatialInformation> <spatialInformation>
<captureArea> <captureArea>
<bottomLeft> <bottomLeft>
<x>-3.0</x> <x>-3.0</x>
<y>20.0</y> <y>20.0</y>
<z>9.0</z> <z>9.0</z>
</bottomLeft> </bottomLeft>
<bottomRight> <bottomRight>
<x>3.0</x> <x>3.0</x>
<y>20.0</y> <y>20.0</y>
<z>9.0</z> <z>9.0</z>
</bottomRight> </bottomRight>
<topLeft> <topLeft>
<x>-3.0</x> <x>-3.0</x>
<y>20.0</y> <y>20.0</y>
<z>11.0</z> <z>11.0</z>
</topLeft> </topLeft>
<topRight> <topRight>
<x>3.0</x> <x>3.0</x>
<y>20.0</y> <y>20.0</y>
<z>11.0</z> <z>11.0</z>
</topRight> </topRight>
</captureArea> </captureArea>
</spatialInformation> </spatialInformation>
<content> <content>
<mediaCaptureIDREF>VC3</mediaCaptureIDREF> <mediaCaptureIDREF>VC3</mediaCaptureIDREF>
<mediaCaptureIDREF>VC5</mediaCaptureIDREF> <mediaCaptureIDREF>VC5</mediaCaptureIDREF>
<mediaCaptureIDREF>VC6</mediaCaptureIDREF> <mediaCaptureIDREF>VC6</mediaCaptureIDREF>
</content> </content>
<maxCaptures exactNumber="true">3</maxCaptures> <maxCaptures exactNumber="true">3</maxCaptures>
<encGroupIDREF>EG0</encGroupIDREF> <encGroupIDREF>EG0</encGroupIDREF>
<description lang="en">big picture of the current speaker + <description lang="en">big picture of the current
pips about previous speakers</description> speaker + pips about previous speakers</description>
<priority>3</priority> <priority>3</priority>
<lang>it</lang> <lang>it</lang>
<mobility>static</mobility> <mobility>static</mobility>
<view>individual</view> <view>individual</view>
</mediaCapture> </mediaCapture>
</mediaCaptures> </mediaCaptures>
<encodingGroups> <encodingGroups>
<encodingGroup encodingGroupID="EG0"> <encodingGroup encodingGroupID="EG0">
<maxGroupBandwidth>600000</maxGroupBandwidth> <maxGroupBandwidth>600000</maxGroupBandwidth>
<encodingIDList> <encodingIDList>
skipping to change at line 3758 skipping to change at line 3731
<personInfo> <personInfo>
<ns2:fn> <ns2:fn>
<ns2:text>Ciccio</ns2:text> <ns2:text>Ciccio</ns2:text>
</ns2:fn> </ns2:fn>
</personInfo> </personInfo>
<personType>chairman</personType> <personType>chairman</personType>
<personType>timekeeper</personType> <personType>timekeeper</personType>
</person> </person>
</people> </people>
</clueInfo> </clueInfo>
]]></sourcecode>
</section>
]]> </middle>
</artwork> <back>
</figure> <references>
<name>References</name>
</section> <references>
<name>Normative References</name>
<section title="Diff with draft-ietf-clue-data-model-schema-16 version">
<t>
As per Alexey Melnikov's and Stefan Winter's comments: replaced wrong
references to RFC2119 in section 11.3 and section 11.5.
The updated reference is to RFC5646.
</t>
</section>
<section title="Diff with draft-ietf-clue-data-model-schema-15 version">
<t>
Applied modifications as per the following reviews: (i) Alexey
Melnikov's discuss and comments (abstract amendments, typo corrections,
insertion of references, etc.); (ii) Kathleen Moriarty's discuss and
comments (amendments to the Security Considerations section); (iii)
Stefan Winter's OPS-DIR review (use of enumerated types in the schema).
</t>
</section>
<section title="Diff with draft-ietf-clue-data-model-schema-14 version">
<t>
Applied modifications as per the following reviews: (i) Henry S.
Thompson's APPS-DIR review; (ii) Stefan Winter's OPS-DIR review; (iii)
Francis Dupont's GEN-ART review; (iv) Rich Salz's review (as part of
the security directorate's ongoing effort to review all IETF documents
being processed by the IESG.)
</t>
</section>
<section title="Diff with draft-ietf-clue-data-model-schema-13 version">
<t>
Applied modifications as per the latest Area Director (Alissa Cooper's)
review comments.
</t>
</section>
<section title="Diff with draft-ietf-clue-data-model-schema-12 version">
<t>
Removed some typos and inconsistencies.
Applied modifications as per Alissa Cooper's review comments.
</t>
</section>
<section title="Diff with draft-ietf-clue-data-model-schema-11 version">
<t>
Applied modifications as per Mark Duckworth's review
(example corrections and maxCapturesType modification)</t>
<t>
maxCapturesType has been changed from positiveInteger to
unsignedShort excluding value 0.</t>
</section>
<section title="Diff with draft-ietf-clue-data-model-schema-10 version">
<t>
Minor modifications have been applied to address nits at page
https://www.ietf.org/tools/idnits?url=https://www.ietf.org/archive/id/
draft-ietf-clue-data-model-schema-10.txt.
</t>
</section>
<section title="Diff with draft-ietf-clue-data-model-schema-09 version">
<list style="symbols">
<t>We have introduced a &lt;captureOrigin&gt; element containing
a mandatory &lt;capturePoint&gt; and an optional
&lt;lineOfCapturePoint&gt; in the definition of
&lt;spatialInformation&gt; as per Paul's review
</t>
<t>A new type definition for switching policies (resembled by
&lt;policy&gt; element) has been provided in order to have acceptable
values in the form of "token:index".
</t>
<t>Minor modifications suggested in WGLC reviews have been applied.</t>
</list>
</section>
<section title="Diff with draft-ietf-clue-data-model-schema-08 version">
<list style="symbols">
<t>Typos correction</t>
</list>
</section>
<section title="Diff with draft-ietf-clue-data-model-schema-07 version">
<list style="symbols">
<t>IANA Considerations: text added</t>
<t>maxCaptureEncodings removed</t>
<t>personTypeType values aligned with CLUE framework</t>
<t>allowSubsetChoice added for multiple content captures</t>
<t>embeddedText moved from videoCaptureType definition to
mediaCaptureType definition
</t>
<t>typos removed from section Terminology</t>
</list>
</section>
<section title="Diff with draft-ietf-clue-data-model-schema-06 version">
<list style="symbols">
<t>
Capture Scene Entry/Entries renamed as Capture Scene View/Views in the
text, &lt;sceneEntry&gt;/&lt;sceneEntries&gt; renamed as
&lt;sceneView&gt;/&lt;sceneViews&gt; in the XML schema.
</t>
<t>
Global Scene Entry/Entries renamed as Global View/Views in the text,
&lt;globalSceneEntry&gt;/&lt;globalSceneEntries&gt; renamed as
&lt;globalView&gt;/&lt;globalViews&gt;
</t>
<t>
Security section added.
</t>
<t>
Extensibility: a new type is introduced to describe other types of
media capture (otherCaptureType), text
and example added.
</t>
<t>
Spatial information section updated: capture point optional, text now is
coherent with the framework one.
</t>
<t>
Audio capture description: &lt;sensitivityPattern&gt; added,
&lt;audioChannelFormat&gt; removed, &lt;captureArea&gt; disallowed.
</t>
<t>Simultaneous set definition: added &lt;captureSceneIDREF&gt; to refer
to capture scene identifiers as shortcuts and an optional mediaType
attribute which is mandatory to use when only capture scene identifiers
are listed.
</t>
<t>
Encoding groups: removed the constraint of the same media type.
</t>
<t>Updated text about media captures without &lt;encodingGroupIDREF&gt;
(optional in the XML schema).</t>
<t>
"mediaType" attribute removed from homogeneous groups of capture
(scene views and globlal views)
</t>
<t>
"mediaType" attribute removed from the global view textual description.
</t>
<t>"millimeters" scale value changed in "mm"</t>
</list>
</section>
<section title="Diff with draft-ietf-clue-data-model-schema-04 version">
<t>
<list syle="symbols">
<t>globalCaptureEntries/Entry renamed as globalSceneEntries/Entry;</t>
<t>sceneInformation added;</t>
<t>Only capture scene entry identifiers listed within global scene
entries (media capture identifiers removed);</t>
<t>&lt;participants&gt; renamed as &lt;people&gt; in the
&gt;clueInfo&lt; template</t>
<t>&lt;vcard&gt; renamed as &lt;personInfo&gt; to synch
with the framework terminology</t>
<t>&lt;participantType&gt; renamed as &lt;personType&gt;
to synch with the framework terminology</t>
<t>&lt;participantIDs&gt; renamed as &lt;capturedPeople&gt; in the
media capture type definition to remove ambiguity</t>
<t>Examples have been updated with the new definitions of
&lt;globalSceneEntries&gt; and of &lt;people&gt;.</t>
</list>
</t>
</section>
<section title="Diff with draft-ietf-clue-data-model-schema-03 version"> <!--draft-ietf-clue-framework-25 is 8845 -->
<t> <reference anchor='RFC8845' target='https://www.rfc-editor.org/info/rfc8845'>
<list syle="symbols"> <front>
<t>encodings section has been removed</t> <title>Framework for Telepresence Multi-Streams</title>
<t>global capture entries have been introduced</t> <seriesInfo name='RFC' value='8845' />
<t>capture scene entry identifiers are used as shortcuts in <seriesInfo name='DOI' value='10.17487/RFC8845' />
listing the content of <author initials='M' surname='Duckworth' fullname='Mark Duckworth' role='editor'
MCC (similarly to simultaneous set and global capture entries)</t> >
<t>Examples have been updated. A new example with global capture <organization />
entries has been added.</t> </author>
<t>&lt;encGroupIDREF&gt; has been made optional.</t> <author initials='A' surname='Pepperell' fullname='Andrew Pepperell'>
<t>&lt;single&gt; has been renamed into &lt;individual&gt;</t> <organization />
<t>Obsolete comments have been removed.</t> </author>
<t>participants information has been added.</t> <author initials='S' surname='Wenger' fullname='Stephan Wenger'>
</list> <organization />
</t> </author>
</section> <date month='June' year='2020' />
</front>
</reference>
<section title="Diff with draft-ietf-clue-data-model-schema-02 version"> <!--draft-ietf-clue-datachannel-18 is 8850 -->
<t> <reference anchor='RFC8850' target='https://www.rfc-editor.org/info/rfc8850'>
<list syle="symbols"> <front>
<t>captureParameters and encodingParameters have been removed from the <title>Controlling Multiple Streams for Telepresence (CLUE) Protocol Data Channe
captureEncodingType</t> l</title>
<t>data model example has been updated and validated <seriesInfo name='RFC' value='8850' />
according to the new schema. Further description of the <seriesInfo name='DOI' value='10.17487/RFC8850' />
represented scenario has been provided.</t> <author initials='C' surname='Holmberg' fullname='Christer Holmberg'>
<t>A multiple content capture example has been added.</t> <organization />
<t>Obsolete comments and references have been removed.</t> </author>
</list> <date month='June' year='2020' />
</t> </front>
</section> </reference>
<section title="Acknowledgments"> <!--draft-ietf-clue-protocol-19 is 8847 -->
<t> <reference anchor='RFC8847' target='https://www.rfc-editor.org/info/rfc8847'>
The authors thank all the CLUErs for their precious feedbacks and <front>
support. <title>Protocol for Controlling Multiple Streams for Telepresence (CLUE)</title>
Thanks also to Alissa Cooper, whose AD reviews helped us improve the <seriesInfo name='RFC' value='8847' />
quality of the document. <seriesInfo name='DOI' value='10.17487/RFC8847' />
</t> <author initials='R' surname='Presta' fullname='Roberta Presta'>
</section> <organization />
</author>
<author initials='S P' surname='Romano' fullname='Simon Pietro Romano'>
<organization />
</author>
<date month='June' year='2020' />
</front>
</reference>
</middle> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer ence.RFC.2119.xml"/>
<back> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer ence.RFC.6351.xml"/>
<references title="Normative References"> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer ence.RFC.5646.xml"/>
<!-- clue framework --> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
<?rfc include="reference.I-D.ietf-clue-framework"?> ence.RFC.7303.xml"/>
<!-- clue data channel --> <!--draft-ietf-ecrit-additional-data-38 is now RFC 7852-->
<?rfc include="reference.I-D.ietf-clue-datachannel"?> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
ence.RFC.7852.xml"/>
<!-- RFC7303 --> <!--RFC 5226 was replaced with RFC 8126-->
<?rfc include="reference.RFC.7303"?> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
ence.RFC.8126.xml"/>
<!-- clue protocol --> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
<?rfc include="reference.I-D.ietf-clue-protocol"?> ence.RFC.8174.xml"/>
<!-- ecrit --> </references>
<?rfc include="reference.I-D.ietf-ecrit-additional-data"?> <references>
<name>Informative References</name>
<!-- RFC2119 --> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
<?rfc include="reference.RFC.2119"?> ence.RFC.3688.xml"/>
<!-- RFC6351 --> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
<?rfc include="reference.RFC.6351"?> ence.RFC.4353.xml"/>
<!-- RFC5646 --> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
<?rfc include="reference.RFC.5646"?> ence.RFC.3550.xml"/>
<!-- RFC5646 --> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
<?rfc include="reference.RFC.5226"?> ence.RFC.6838.xml"/>
</references>
<references title="Informative References"> <xi:include href="https://xml2rfc.tools.ietf.org/public/rfc/bibxml/refer
ence.RFC.7667.xml"/>
</references>
</references>
<!-- RFC3688 --> <section numbered="false" toc="default">
<?rfc include="reference.RFC.3688"?> <name>Acknowledgements</name>
<t>
<!--[rfced] We replaced "precious" with "valuable" in the following
sentence as we thought it was a better word choice per the
context. Please let us know if you prefer otherwise.
<!-- RFC4353 --> Original:
<?rfc include="reference.RFC.4353"?> The authors thank all the CLUErs for their precious feedbacks and support.
<!-- RFC3550 --> Current:
<?rfc include="reference.RFC.3550"?> The authors thank all the CLUErs for their valuable feedback and support.
-->
-&gt; The authors thank all the CLUErs for their valuable feedback and
<!-- RFC6838 --> support. Thanks also to <contact fullname="Alissa Cooper"/>, whose AD review
<?rfc include="reference.RFC.6838"?> helped us improve the quality of the document.
</t>
</section>
<!-- RFC7667 --> <!-- [rfced] Throughout the text, the following terminology appears to
<?rfc include="reference.RFC.7667"?> be used inconsistently. Please review these occurrences and let
us know if/how they may be made consistent (and if 'XML Schema'
is the same as 'XML Schema data model').
</references> XML Schema vs. XML schema
</back> XML Schema data model
CLUE data model schema
telepresence data model
-->
</back>
</rfc> </rfc>
 End of changes. 469 change blocks. 
1850 lines changed or deleted 1740 lines changed or added

This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/