rfc8846v4.txt   rfc8846.txt 
skipping to change at line 194 skipping to change at line 194
Capture Device: A device that converts physical input, such as Capture Device: A device that converts physical input, such as
audio, video, or text, into an electrical signal, in most cases to audio, video, or text, into an electrical signal, in most cases to
be fed into a media encoder. be fed into a media encoder.
Capture Encoding: A specific encoding of a Media Capture, to be sent Capture Encoding: A specific encoding of a Media Capture, to be sent
by a Media Provider to a Media Consumer via RTP. by a Media Provider to a Media Consumer via RTP.
Capture Scene: A structure representing a spatial region captured by Capture Scene: A structure representing a spatial region captured by
one or more Capture Devices, each capturing media representing a one or more Capture Devices, each capturing media representing a
portion of the region. The spatial region represented by a portion of the region. The spatial region represented by a
Capture Scene MAY correspond to a real region in physical space, Capture Scene may correspond to a real region in physical space,
such as a room. A Capture Scene includes attributes and one or such as a room. A Capture Scene includes attributes and one or
more Capture Scene Views, with each view including one or more more Capture Scene Views, with each view including one or more
Media Captures. Media Captures.
Capture Scene View (CSV): A list of Media Captures of the same media Capture Scene View (CSV): A list of Media Captures of the same media
type that together form one way to represent the entire Capture type that together form one way to represent the entire Capture
Scene. Scene.
CLUE Participant: This term is imported from the CLUE protocol CLUE Participant: This term is imported from the CLUE protocol
document [RFC8847]. document [RFC8847].
skipping to change at line 219 skipping to change at line 219
way to encode a Media Capture to become a Capture Encoding. way to encode a Media Capture to become a Capture Encoding.
Encoding Group: A set of encoding parameters representing a total Encoding Group: A set of encoding parameters representing a total
media encoding capability to be subdivided across potentially media encoding capability to be subdivided across potentially
multiple Individual Encodings. multiple Individual Encodings.
Endpoint: A CLUE-capable device that is the logical point of final Endpoint: A CLUE-capable device that is the logical point of final
termination through receiving, decoding and rendering, and/or termination through receiving, decoding and rendering, and/or
initiation through capturing, encoding, and sending of media initiation through capturing, encoding, and sending of media
streams. An endpoint consists of one or more physical devices streams. An endpoint consists of one or more physical devices
that source and sink media streams and exactly one participant that source and sink media streams, and exactly one participant
[RFC4353] (which, in turn, includes exactly one SIP User Agent). [RFC4353] (which, in turn, includes exactly one SIP User Agent).
Endpoints can be anything from multiscreen/multicamera rooms to Endpoints can be anything from multiscreen/multicamera rooms to
handheld devices. handheld devices.
Media: Any data that, after suitable encoding, can be conveyed over Media: Any data that, after suitable encoding, can be conveyed over
RTP, including audio, video, or timed text. RTP, including audio, video, or timed text.
Media Capture: A source of Media, such as from one or more Capture Media Capture: A source of Media, such as from one or more Capture
Devices or constructed from other media streams. Devices or constructed from other media streams.
Media Consumer: A CLUE-capable device that intends to receive Media Consumer: A CLUE-capable device that intends to receive
Capture Encodings. Capture Encodings.
Media Provider: A CLUE-capable device that intends to send Capture Media Provider: A CLUE-capable device that intends to send Capture
Encodings. Encodings.
Multiple Content Capture (MCC): A Capture that mixes and/or switches Multiple Content Capture (MCC): A Capture that mixes and/or switches
other Captures of a single type (e.g., all audio or all video.) other Captures of a single type (for example, all audio or all
Particular Media Captures may or may not be present in the video). Particular Media Captures may or may not be present in
resultant Capture Encoding depending on time or space. Denoted as the resultant Capture Encoding depending on time or space.
"MCCn" in the example cases in this document. Denoted as "MCCn" in the example cases in this document.
Multipoint Control Unit (MCU): A CLUE-capable device that connects Multipoint Control Unit (MCU): A CLUE-capable device that connects
two or more endpoints together into one single multimedia two or more endpoints together into one single multimedia
conference [RFC7667]. An MCU includes a Mixer, similar to those conference [RFC7667]. An MCU includes a Mixer, similar to those
in [RFC4353], but without the requirement to send media to each in [RFC4353], but without the requirement to send media to each
participant. participant.
Plane of Interest: The spatial plane within a scene containing the Plane of Interest: The spatial plane within a scene containing the
most-relevant subject matter. most-relevant subject matter.
Provider: Same as Media Provider. Provider: Same as a Media Provider.
Render: The process of generating a representation from Media, such Render: The process of generating a representation from Media, such
as displayed motion video or sound emitted from loudspeakers. as displayed motion video or sound emitted from loudspeakers.
Scene: Same as Capture Scene. Scene: Same as a Capture Scene.
Simultaneous Transmission Set: A set of Media Captures that can be Simultaneous Transmission Set: A set of Media Captures that can be
transmitted simultaneously from a Media Provider. transmitted simultaneously from a Media Provider.
Single Media Capture: A capture that contains media from a single Single Media Capture: 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 or a video capture from a single camera. microphone or a video capture from a single camera.
Spatial Relation: The arrangement of two objects in space, in Spatial Relation: The arrangement of two objects in space, in
contrast to relation in time or other relationships. contrast to relation in time or other relationships.
skipping to change at line 476 skipping to change at line 476
</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 https://www.iana.org/assignments/clue. 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 https://www.iana.org/assignments/clue. 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 https://www.iana.org/assignments/clue. 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"/>
skipping to change at line 601 skipping to change at line 601
<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 Acceptable values (enumerations) for this type are managed by
IANA in the "CLUE Schema &lt;sensitivityPattern&gt; registry", IANA in the "CLUE Schema &lt;sensitivityPattern&gt;" registry,
accessible at https://www.iana.org/assignments/clue. 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>
skipping to change at line 1321 skipping to change at line 1321
The <view> element is an optional tag describing what is represented The <view> element is an optional tag describing what is represented
in the spatial area covered by a media capture. It has been in the spatial area covered by a media capture. It has been
specified as a simple string with an annotation pointing to an IANA specified as a simple string with an annotation pointing to an IANA
registry that is defined ad hoc: registry that is defined ad hoc:
<!-- 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 https://www.iana.org/assignments/clue. accessible at https://www.iana.org/assignments/clue.
</xs:documentation> </xs:documentation>
</xs:annotation> </xs:annotation>
</xs:element> </xs:element>
The current possible values, as per the CLUE framework document The current possible values, as per the CLUE framework document
[RFC8845], are: "room", "table", "lectern", "individual", and [RFC8845], are: "room", "table", "lectern", "individual", and
"audience". "audience".
11.19. <presentation> 11.19. <presentation>
skipping to change at line 1343 skipping to change at line 1343
The <presentation> element is an optional tag used for media captures The <presentation> element is an optional tag used for media captures
conveying information about presentations within the telepresence conveying information about presentations within the telepresence
session. It has been specified as a simple string with an annotation session. It has been specified as a simple string with an annotation
pointing to an IANA registry that is defined ad hoc: pointing to an IANA registry that is defined ad hoc:
<!-- 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 https://www.iana.org/assignments/clue. accessible at https://www.iana.org/assignments/clue.
</xs:documentation> </xs:documentation>
</xs:annotation> </xs:annotation>
</xs:element> </xs:element>
The current possible values, as per the CLUE framework document The current possible values, as per the CLUE framework document
[RFC8845], are "slides" and "images". [RFC8845], are "slides" and "images".
11.20. <embeddedText> 11.20. <embeddedText>
skipping to change at line 1420 skipping to change at line 1420
The <sensitivityPattern> element is an optional field describing the The <sensitivityPattern> element is an optional field describing the
characteristics of the nominal sensitivity pattern of the microphone characteristics of the nominal sensitivity pattern of the microphone
capturing the audio signal. It has been specified as a simple string capturing the audio signal. It has been specified as a simple string
with an annotation pointing to an IANA registry that is defined ad with an annotation pointing to an IANA registry that is defined ad
hoc: hoc:
<!-- 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 <sensitivityPattern> registry", accessible IANA in the "CLUE Schema &lt;sensitivityPattern&gt;" registry,
at https://www.iana.org/assignments/clue. accessible at https://www.iana.org/assignments/clue.
</xs:documentation> </xs:documentation>
</xs:annotation> </xs:annotation>
</xs:element> </xs:element>
The current possible values, as per the CLUE framework document The current possible values, as per the CLUE framework document
[RFC8845], are "uni", "shotgun", "omni", "figure8", "cardioid", and [RFC8845], are "uni", "shotgun", "omni", "figure8", "cardioid", and
"hyper-cardioid". "hyper-cardioid".
13. Video Captures 13. Video Captures
skipping to change at line 1528 skipping to change at line 1528
represent a capture scene for a fixed media type. represent a capture scene for a fixed media type.
The XML schema representation of a <captureScene> element is the The XML schema representation of a <captureScene> element is the
following: following:
<!-- 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>
Each capture scene is identified by a "sceneID" attribute. The Each capture scene is identified by a "sceneID" attribute. The
skipping to change at line 1799 skipping to change at line 1799
21. <people> 21. <people>
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 <people> element. As it can be seen captures is conveyed via the <people> element. As it can be seen
from the XML schema depicted below, for each participant, a <person> from the XML schema depicted below, for each participant, a <person>
element is provided. element is provided.
<!-- 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>
21.1. <person> 21.1. <person>
<person> includes all the metadata related to a person represented <person> includes all the metadata related to a person represented
within one or more media captures. Such element provides the vCard within one or more media captures. Such element provides the vCard
of the subject (via the <personInfo> element; see Section 21.1.2) and of the subject (via the <personInfo> element; see Section 21.1.2) and
its conference role(s) (via one or more <personType> elements; see its conference role(s) (via one or more <personType> elements; see
Section 21.1.3). Furthermore, it has a mandatory "personID" Section 21.1.3). Furthermore, it has a mandatory "personID"
attribute (Section 21.1.1). attribute (Section 21.1.1).
skipping to change at line 1853 skipping to change at line 1853
The value of the <personType> element determines the role of the The value of the <personType> element determines the role of the
represented participant within the telepresence session organization. represented participant within the telepresence session organization.
It has been specified as a simple string with an annotation pointing It has been specified as a simple string with an annotation pointing
to an IANA registry that is defined ad hoc: to an IANA registry that is defined ad hoc:
<!-- 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 https://www.iana.org/assignments/clue. accessible at https://www.iana.org/assignments/clue.
</xs:documentation> </xs:documentation>
</xs:annotation> </xs:annotation>
</xs:element> </xs:element>
The current possible values, as per the CLUE framework document The current possible values, as per the CLUE framework document
[RFC8845], are: "presenter", "timekeeper", "attendee", "minute [RFC8845], are: "presenter", "timekeeper", "attendee", "minute
taker", "translator", "chairman", "vice-chairman", and "observer". taker", "translator", "chairman", "vice-chairman", and "observer".
A participant can play more than one conference role. In that case, A participant can play more than one conference role. In that case,
 End of changes. 15 change blocks. 
22 lines changed or deleted 22 lines changed or added

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