📄 rfc 4480 rpid rich presence extensions to the presence information data format (pidf).htm
字号:
<A id=page-12 href="http://tools.ietf.org/html/rfc4480#page-12" name=page-12><SPAN class=break> </SPAN></A>
<SPAN class=grey><A href="http://tools.ietf.org/html/rfc4480">RFC 4480</A> RIPD July 2006</SPAN>
o restless
o sad
o sarcastic
o serious
o shocked
o shy
o sick
o sleepy
o stressed
o surprised
o thirsty
o unknown
o worried
Example:
<mood>
<note>I'm ready for the bar BOF!</note>
<sleepy/>
<thirsty/>
</mood>
<SPAN class=h3><A name=section-3.6>3.6</A>. Place-is Element</SPAN>
The <place-is> element describes properties of the place the person
is currently at. This offers the watcher an indication of what kind
of communication is likely to be successful. Each major media type
has its own set of attributes. Omitting the element indicates that
the property is unknown.
For audio, we define the following attributes:
noisy: The person is in a place with a level of background noise
that makes audio communications difficult.
ok: The environmental conditions are suitable for audio
communications.
quiet: The person is in a place such as a library, restaurant, place
of worship, or theater that discourages noise, conversation, and
other distractions.
unknown: The place attributes for audio are unknown.
For video, we define the following attributes:
toobright: The person is in a bright place, sufficient for good
rendering on video.
<SPAN class=grey>Schulzrinne, et al. Standards Track [Page 12]</SPAN>
<A id=page-13 href="http://tools.ietf.org/html/rfc4480#page-13" name=page-13><SPAN class=break> </SPAN></A>
<SPAN class=grey><A href="http://tools.ietf.org/html/rfc4480">RFC 4480</A> RIPD July 2006</SPAN>
ok: The environmental conditions are suitable for video.
dark: The person is in a dark place, and thus the camera may not be
able to capture a good image.
unknown: The place attributes for video are unknown.
For text (real-time text and instant messaging), we define
uncomfortable: Typing or other text entry is uncomfortable.
inappropriate: Typing or other text entry is inappropriate, e.g.,
since the user is in a vehicle or house of worship.
ok: The environmental conditions are suitable for text-based
communications.
unknown: The place attributes for text are unknown.
This list can be augmented by free-text values in a note or
additional IANA-registered values (<A href="http://tools.ietf.org/html/rfc4480#section-7">Section 7</A>).
The <place-is> element contains other elements, e.g.,
<place-is>
<audio>
<noisy />
</audio>
<video>
<dark />
</video>
</place-is>
The <place-is> element MAY be qualified with the 'from' and 'until'
attributes as described in <A href="http://tools.ietf.org/html/rfc4480#section-3.1">Section 3.1</A>.
<SPAN class=h3><A name=section-3.7>3.7</A>. Place-type Element</SPAN>
The <place-type> element describes the type of place the person is
currently at. This offers the watcher an indication of what kind of
communication is likely to be appropriate. The initial set of values
is contained in <A href="http://tools.ietf.org/html/rfc4589">RFC 4589</A> [<A title='"Location Types Registry"' href="http://tools.ietf.org/html/rfc4480#ref-12">12</A>].
This list can be augmented by free-text values or additional IANA-
registered values as described in <A href="http://tools.ietf.org/html/rfc4589">RFC 4589</A>.
<SPAN class=grey>Schulzrinne, et al. Standards Track [Page 13]</SPAN>
<A id=page-14 href="http://tools.ietf.org/html/rfc4480#page-14" name=page-14><SPAN class=break> </SPAN></A>
<SPAN class=grey><A href="http://tools.ietf.org/html/rfc4480">RFC 4480</A> RIPD July 2006</SPAN>
The <place-type> element is a choice of elements, as in
<place-type>
<pt:street/>
</place-type>
The <place-type> element MAY be qualified with the 'from' and 'until'
attributes as described in <A href="http://tools.ietf.org/html/rfc4480#section-3.1">Section 3.1</A>.
<SPAN class=h3><A name=section-3.8>3.8</A>. Privacy Element</SPAN>
The <privacy> element indicates which types of communication third
parties in the vicinity of the presentity are unlikely to be able to
intercept accidentally or intentionally. This does not in any way
describe the privacy properties of the electronic communication
channel, e.g., properties of the encryption algorithm or the network
protocol used.
audio: Inappropriate individuals are not likely to overhear audio
communications.
text: Inappropriate individuals are not likely to see text
communications.
unknown: This information is unknown.
video: Inappropriate individuals are not likely to see video
communications.
The <privacy> element can be used by logic executing on the
watcher or by a composer to filter, sort and label tuples. For
example, a composer may have rules that limit the publication of
tuples labeled "private" to a select subset of the watchers.
The <privacy> element MAY be qualified with the 'from' and 'until'
attributes as described in <A href="http://tools.ietf.org/html/rfc4480#section-3.1">Section 3.1</A>.
Example:
<privacy>
<text/>
<audio/>
</privacy>
<SPAN class=grey>Schulzrinne, et al. Standards Track [Page 14]</SPAN>
<A id=page-15 href="http://tools.ietf.org/html/rfc4480#page-15" name=page-15><SPAN class=break> </SPAN></A>
<SPAN class=grey><A href="http://tools.ietf.org/html/rfc4480">RFC 4480</A> RIPD July 2006</SPAN>
<SPAN class=h3><A name=section-3.9>3.9</A>. Relationship Element</SPAN>
The <relationship> element extends <tuple> and designates the type of
relationship an alternate contact has with the presentity. This
element is provided only if the tuple refers to somebody other than
the presentity. Relationship values include "family", "friend",
"associate" (e.g., for a colleague), "assistant", "supervisor",
"self", and "unknown". The default is "self".
If a relationship is indicated, the URI in the <contact> element
refers to the entity, such as the assistant, that has a relationship
to the presentity, not the presentity itself.
Like tuples without a <relationship> qualifier, the <contact> element
for tuples labeled with a relationship can contain either a
communication URI such as "im", "sip", "sips", "h323", "tel", or
"mailto", or a presence URI, such as "pres" or "sip".
Example:
<relationship>
<friend/>
</relationship>
<SPAN class=h3><A name=section-3.10>3.10</A>. Service Class</SPAN>
The <service-class> element extends <tuple> and designates the type
of service offered.
electronic: Delivery of information by electronic means, i.e.,
without delivering physical objects. Examples include telephone,
fax, email, instant messaging, and SMS.
postal: Delivery by the postal service, e.g., as a letter, parcel,
or postcard. Delivery could be to a post office box or central
mailroom rather than the presentity's office location, for
example.
courier: Delivery by messenger, overnight delivery, or courier.
Courier-delivered messages are usually delivered to a receptionist
rather than, say, a mailroom or receiving department.
freight: Delivery by freight carrier, typically of larger objects
that are not sent by postal mail or courier. The recipient is
often the shipping department or a loading dock.
in-person: Describes the coordinates for visits in person, as by a
visitor, i.e., usually somebody's office or residence.
<SPAN class=grey>Schulzrinne, et al. Standards Track [Page 15]</SPAN>
<A id=page-16 href="http://tools.ietf.org/html/rfc4480#page-16" name=page-16><SPAN class=break> </SPAN></A>
<SPAN class=grey><A href="http://tools.ietf.org/html/rfc4480">RFC 4480</A> RIPD July 2006</SPAN>
unknown: The type of service is unknown.
Electronic service is implied if omitted. The service types
'postal', 'courier', 'freight', and 'in-person' MUST NOT be used
unless the contact URI is empty. Additional data elements defined
elsewhere describe the physical service delivery address for the in-
person, postal, or delivery services. Such addresses might be
specified in geospatial coordinates, civic addresses, or some
specialized address format, e.g., for interstellar addresses or a
company-specific delivery system.
Example:
<service-class><postal/></service-class>
<SPAN class=h3><A name=section-3.11>3.11</A>. Sphere Element</SPAN>
The <sphere> element designates the current state and role that the
person plays. For example, it might describe whether the person is
in a work mode, at home, or participating in activities related to
some other organization such as the IETF or a church. This document
does not define names for these spheres except for two common ones,
"work" and "home", as well as "unknown".
Spheres allow the person to easily turn on or off certain rules that
depend on what groups of people should be made aware of the person's
status. For example, if the person is a Boy Scout leader, he might
set the sphere to "scouting" and then have a rule set that allows
other scout masters in his troop to see his presence status. As soon
as he switches his status to "work", "home", or some other sphere,
the fellow scouts would lose access.
The <sphere> element MAY be qualified with the 'from' and 'until'
attributes as described in <A href="http://tools.ietf.org/html/rfc4480#section-3.1">Section 3.1</A>.
Example:
<sphere>
<home/>
</sphere>
<SPAN class=h3><A name=section-3.12>3.12</A>. Status-Icon Element</SPAN>
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -