rfc 4480 rpid rich presence extensions to the presence information data format (pidf).htm

有关IMS SIP及Presence应用的RFC文档包

   documents.

<SPAN class=h3><A name=section-3.2>3.2</A>.  Activities Element</SPAN>

   The &lt;activities&gt; element describes what the person is currently
   doing, expressed as an enumeration of activity-describing elements.
   A person can be engaged in multiple activities at the same time,
   e.g., traveling and having a meal.  The &lt;activities&gt; element can be
   quite helpful to the watcher in judging how appropriate a
   communication attempt is and which means of communications is most
   likely to succeed and not annoy the person.  The activity indications
   correspond roughly to the category field in calendar entries, such as
   <A href="http://tools.ietf.org/html/rfc2445#section-4.8.1.2">Section&nbsp;4.8.1.2 of RFC 2445</A> [<A title='"Internet Calendaring and Scheduling Core Object Specification (iCalendar)"' href="http://tools.ietf.org/html/rfc4480#ref-13">13</A>].

   An activities enumeration consists of one or more elements using
   elements drawn from the list below, a string enclosed in the &lt;other&gt;
   element, or IANA-registered values from other namespaces (<A href="http://tools.ietf.org/html/rfc4480#section-7">Section 7</A>).

   If a person publishes an activity of "permanent-absence", it is
   likely that all services will report a status of CLOSED.  In general,
   services MAY advertise either service status for any activity value.

   Activities such as &lt;appointment&gt;, &lt;breakfast&gt;, &lt;dinner&gt;, &lt;holiday&gt;,
   &lt;lunch&gt;, &lt;meal&gt;, &lt;meeting&gt;, &lt;performance&gt;, &lt;travel&gt;, or &lt;vacation&gt;
   can often be derived from calendar information.

   appointment:  The person has a calendar appointment, without
      specifying exactly of what type.  This activity is indicated if
      more detailed information is not available or the person chooses
      not to reveal more information.

   away:  The person is physically away from all interactive
      communication devices.  This activity element was included since
      it can often be derived automatically from security systems,
      energy management systems, or entry badge systems.  Although this
      activity would typically be associated with a status of CLOSED
      across all services, a person may declare himself or herself away








<SPAN class=grey>Schulzrinne, et al.         Standards Track                     [Page 7]</SPAN>
<A id=page-8 href="http://tools.ietf.org/html/rfc4480#page-8" name=page-8><SPAN class=break> </SPAN></A>
<SPAN class=grey><A href="http://tools.ietf.org/html/rfc4480">RFC 4480</A>                          RIPD                         July 2006</SPAN>


      to discourage communication, but indicate that he or she still can
      be reached if needed.  However, communication attempts might reach
      an answering service, for example.

   breakfast:  The person is eating the first meal of the day, usually
      eaten in the morning.

   busy:  The person is busy, without further details.  Although this
      activity would typically be associated with a status of CLOSED
      across all services, a person may declare himself or herself busy
      to discourage communication, but indicate that he or she still can
      be reached if needed.

   dinner:  The person is having his or her main meal of the day, eaten
      in the evening or at midday.

   holiday:  This is a scheduled national or local holiday.

   in-transit:  The person is riding in a vehicle, such as a car, but
      not steering.  The &lt;place-type&gt; element provides more specific
      information about the type of conveyance the person is using.

   looking-for-work:  The presentity is looking for (paid) work.

   lunch:  The person is eating his or her midday meal.

   meal:  The person is scheduled for a meal, without specifying whether
      it is breakfast, lunch, or dinner, or some other meal.

   meeting:  The person is in an assembly or gathering of people, as for
      a business, social, or religious purpose.  A meeting is a sub-
      class of an appointment.

   on-the-phone:  The person is talking on the telephone.  This activity
      is included since it can often be derived automatically.

   other:  The person is engaged in an activity with no defined
      representation as an &lt;activities&gt; element.  The enclosed string
      describes the activity in plain text.

   performance:  A performance is a sub-class of an appointment and
      includes musical, theatrical, and cinematic performances as well
      as lectures.  It is distinguished from a meeting by the fact that
      the person may either be lecturing or be in the audience, with a
      potentially large number of other people, making interruptions
      particularly noticeable.





<SPAN class=grey>Schulzrinne, et al.         Standards Track                     [Page 8]</SPAN>
<A id=page-9 href="http://tools.ietf.org/html/rfc4480#page-9" name=page-9><SPAN class=break> </SPAN></A>
<SPAN class=grey><A href="http://tools.ietf.org/html/rfc4480">RFC 4480</A>                          RIPD                         July 2006</SPAN>


   permanent-absence:  The person will not return for the foreseeable
      future, e.g., because it is no longer working for the company.
      This activity is associated with a status of CLOSED across all
      services.

   playing:  The person is occupying himself or herself in amusement,
      sport, or other recreation.

   presentation:  The person is giving a presentation, lecture, or
      participating in a formal round-table discussion.

   shopping:  The person is visiting stores in search of goods or
      services.

   sleeping:  This activity category can often be generated
      automatically from a calendar, local time information, or
      biometric data.

   spectator:  The person is observing an event, such as a sports event.

   steering:  The person is controlling a vehicle, watercraft, or plane.

   travel:  The person is on a business or personal trip, but not
      necessarily in-transit.

   tv:  The person is watching television.

   unknown:  The activity of the person is unknown.  This element is
      generally not used together with other activities.

   vacation:  A period of time devoted to pleasure, rest, or relaxation.

   working:  The presentity is engaged in, typically paid, labor, as
      part of a profession or job.

   worship:  The presentity is participating in religious rites.

   The &lt;activities&gt; 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:

     &lt;activities&gt;
       &lt;note&gt;Enjoying the morning paper&lt;/note&gt;
       &lt;vacation/&gt;
       &lt;breakfast/&gt;
       &lt;other&gt;reading&lt;/other&gt;
     &lt;/activities&gt;



<SPAN class=grey>Schulzrinne, et al.         Standards Track                     [Page 9]</SPAN>
<A id=page-10 href="http://tools.ietf.org/html/rfc4480#page-10" name=page-10><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.3>3.3</A>.  Class Element</SPAN>

   The &lt;class&gt; element describes the class of the service, device, or
   person.  Multiple elements can have the same class name within a
   presence document, but each person, service, or device can only have
   one class label.  The naming of classes is left to the presentity.
   The presentity can use this information to group similar services,
   devices, or person elements or to convey information that the
   presence agent can use for filtering or authorization.  This
   information is not generally presented to the watcher user interface.

   The &lt;class&gt; element MUST NOT 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.4>3.4</A>.  Device Identifier</SPAN>

   The &lt;deviceID&gt; element in the &lt;tuple&gt; element references the device
   that provides a particular service.  The element is defined
   syntactically in the data model [<A title='"A Data Model for Presence"' href="http://tools.ietf.org/html/rfc4480#ref-16">16</A>] schema.  One service can be
   provided by multiple devices, so that each service tuple may contain
   zero or more &lt;deviceID&gt; elements.  There is no significance in the
   order of these elements.

   The &lt;deviceID&gt; element MUST NOT 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.5>3.5</A>.  Mood Element</SPAN>

   The &lt;mood&gt; element describes the mood of the presentity.  The mood
   values are enumerated chosen by the presentity.  The mood itself is
   provided as the element name of a defined child element of the &lt;mood&gt;
   element (e.g., &lt;happy/&gt;); one such child element is REQUIRED.  The
   user MAY also specify a natural-language description of, or reason
   for, the mood in the &lt;note&gt; child of the &lt;mood&gt; element, which is
   OPTIONAL.  (This definition follows the Jabber Extension JEP-107.)
   It is RECOMMENDED that an implementation support the mood values
   proposed in Jabber Extension JEP-0107, which in turn are a superset
   of the Wireless Village [<A title='"The Wireless Village Initiative: Presence Attributes 1.1"' href="http://tools.ietf.org/html/rfc4480#ref-18">18</A>] mood values and the values enumerated in
   the Affective Knowledge Representation that has been defined by
   Lisetti [<A title='"Personality, Affect, and Emotion Taxonomy for Socially Intelligent Agents"' href="http://tools.ietf.org/html/rfc4480#ref-17">17</A>]:

   A mood enumeration consists of one or more elements using elements
   drawn from the list below, a string enclosed in the &lt;other&gt; element,
   or IANA-registered values from other namespaces (<A href="http://tools.ietf.org/html/rfc4480#section-7">Section 7</A>).

   The &lt;mood&gt; 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=grey>Schulzrinne, et al.         Standards Track                    [Page 10]</SPAN>
<A id=page-11 href="http://tools.ietf.org/html/rfc4480#page-11" name=page-11><SPAN class=break> </SPAN></A>
<SPAN class=grey><A href="http://tools.ietf.org/html/rfc4480">RFC 4480</A>                          RIPD                         July 2006</SPAN>


   o  afraid
   o  amazed
   o  angry
   o  annoyed
   o  anxious
   o  ashamed
   o  bored
   o  brave
   o  calm
   o  cold
   o  confused
   o  contented
   o  cranky
   o  curious
   o  depressed
   o  disappointed
   o  disgusted
   o  distracted
   o  embarrassed
   o  excited
   o  flirtatious
   o  frustrated
   o  grumpy
   o  guilty
   o  happy
   o  hot
   o  humbled
   o  humiliated
   o  hungry
   o  hurt
   o  impressed
   o  in_awe
   o  in_love
   o  indignant
   o  interested
   o  invincible
   o  jealous
   o  lonely
   o  mean
   o  moody
   o  nervous
   o  neutral
   o  offended
   o  other
   o  playful
   o  proud
   o  relieved
   o  remorseful



<SPAN class=grey>Schulzrinne, et al.         Standards Track                    [Page 11]</SPAN>