draft-ietf-simple-rpid-10.txt
`
`Page 10 of 41
`
`Internet-Draft
`
`RPID
`
`December 2005
`
`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, ship 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 «activities? element MAY be qualified with the 'from' and 'until'
`attributes as described in Section 3.1.
`Example:
`
`«activities?
`«note?Enjoying the morning paper</note>
`«vacation/?
`«breakfast/?
`«other?reading</other?
`«/activities?
`
`3.3 Class Element
`The «class? 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 «class? element MUST NOT be qualified with the 'from' and 'until'
`attributes as described in Section 3.1.
`
`3.4 Device Identifier
`The «devicelD? element in the «tuple? element references the device
`that provides a particular service. The element is defined
`
`Schulzrinne, et al.
`
`Expires June 23, 2006
`
`[Page 10]
`
`r.u.//NT.\TDv Potent p;iinoc\TPVMC.KWak\TPVMCP02-Comm HubXPrior Art\draft-ietf-sim... 1/17/2007
`
`Epic Games Ex. 1029
`Page 237
`
`

`

`draft-ietf-simple-rpid-10.txt
`
`Page 11 of 41
`
`Internet-Draft
`
`RPID
`
`December 2005
`
`syntactically in the data model [14] schema. One service can be
`provided by multiple devices, so that each service tuple may contain
`zero or more <deviceID> elements. There is no significance in the
`order of these elements.
`The <deviceID> element MUST NOT be qualified with the 'from' and
`'until' attributes as described in Section 3.1.
`3.5 Mood Element
`The <mood> element describes the mood of the presentity. They are
`enumerated chosen by the presentity. The mood itself is provided as
`the element name of a defined child element of the <mood> element
`(e.g., <happy/>); one such child element is REQUIRED. The user MAY
`also specify a natural-language description of, or reason for, the
`mood in the <text> child of the <mood> 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 [16] mood values and the values enumerated in the
`Affective Knowledge Representation that has been defined by Lisetti
`[15] :
`A mood enumeration consists of one or more elements using elements
`drawn from the list below, a string enclosed in the <other> element
`or IANA-registered values from other namespaces (Section 7).
`The <activities> element MAY be qualified with the 'from' and 'until'
`attributes as described in Section 3.1.
`afraid
`amazed
`angry
`annoyed
`anxious
`ashamed
`bored
`brave
`calm
`cold
`confused
`contented
`cranky
`curious
`depressed
`disappointed
`disgusted
`
`Schulzrinne, et al.
`
`Expires June 23, 2006
`
`[Page 11]
`
`file-Z/NATPV Patent Filines\IPVMC-Kwok\IPVMCP02-Comm Hub\Prior Art\drafl-ietf-sim... 1/17/2007
`
`Epic Games Ex. 1029
`Page 238
`
`

`

`draft-ietf-simple-rpid-10.txt
`
`Page 12 of 41
`
`Internet-Draft
`
`RPID
`
`December 2005
`
`distracted
`embarrassed
`excited
`flirtatious
`frustrated
`grumpy
`guilty
`happy
`hot
`humbled
`humiliated
`hungry
`hurt
`impressed
`in_awe
`in_love
`indignant
`interested
`invincible
`jealous
`lonely
`mean
`moody
`nervous
`neutral
`offended
`other
`playful
`proud
`relieved
`remorseful
`restless
`sad
`sarcastic
`serious
`shocked
`shy
`sick
`sleepy
`stressed
`surprised
`thirsty
`unknown
`worried
`Example:
`
`Schulzrinne, et al.
`
`Expires June 23, 2006
`
`[Page 12]
`
`Fi1p. //N \TPV Patent Filin2s\IPVMC-Kwok\IPVMCP02-Comm Hub\Prior Art\draft-ietf-sim... 1/17/2007
`
`Epic Games Ex. 1029
`Page 239
`
`

`

`draft-ietf-simple-rpid-10.txt
`
`Page 13 of 41
`
`Internet-Draft
`
`RPID
`
`December 2005
`
`<mood>
`<note>I'm ready for the bar BOF!</note>
`<sleepy/>
`<thirsty/>
`</mood>
`
`3.6 Place-is Element
`The <place-is> element describes properties of the place the person
`is currently at. This offers the watcher an indication 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.
`ok: The environmental conditions are suitable for video.
`dark: The person is in a dark place, and thus the camera may not be
`be able to capture a good image.
`unknown: The place attributes for video are unknown.
`For text, we define the following attributes:
`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 (Section 7).
`
`Schulzrinne, et al.
`
`Expires June 23, 2006
`
`[Page 13]
`
`f,le//N\TPV Patent FilinpS\TPVMC-Kwok\TPVMCP02-Comm Hub\Prior Art\draft-ietf-sim... 1/17/2007
`
`Epic Games Ex. 1029
`Page 240
`
`

`

`draft-ietf-simple-rpid-10.txt
`
`Page 14 of 41
`
`Internet-Draft
`
`RPID
`
`December 2005
`
`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 Section 3.1.
`3.7 Place-type Element
`The <place-type> element describes the type of place the person is
`currently at. This offers the watcher an indication what kind of
`communication is likely to be appropriate. We define an initial set
`of values below:
`aircraft: The person is traveling in a plane, helicopter or balloon,
`airport: The person is located in an airport, heliport or similar
`location.
`arena: The person is in an enclosed area used for sports events,
`automobile: The person is in a self-propelled passenger vehicle,
`bank: The person is in a business establishment in which money is
`kept for saving or commercial purposes or is invested, supplied
`for loans, or exchanged.
`bar: The person is in a bar or saloon.
`bus: The person is traveling in a public or charter bus.
`bus-station: The person is in a terminal that serves bus passengers;
`bus depot or bus terminal.
`cafe: The person is in a cafe or coffeeshop.
`classroom: The person is in an academic classroom or lecture hall,
`club: The person is in a dance club or discotheque.
`construction: The person is on a construction site,
`convention-center: The person is in a convention center,
`cycle: The person is riding a bicycle, motorcycle or similar vehicle,
`government-building: The person is in a government building, such as
`those used by the legislative, executive, or judicial branches of
`governments, including court houses, police stations and military
`installations.
`
`Schulzrinne, et al.
`
`Expires June 23, 2006
`
`[Page 14]
`
`file7/N\TPV Patent Filinps\TPVMC-Kwok\IPVMCP02-Comm HubVPrior Art\draft-ietf-sim... 1/17/2007
`
`Epic Games Ex. 1029
`Page 241
`
`

`

`draft-ietf-simple-rpid-10.txt
`
`Page 15 of 41
`
`Internet-Draft
`
`RPID
`
`December 2005
`
`hospital: The person is in a hospital, hospice, medical clinic,
`mental institution, or doctor's office.
`hotel: The person is in a hotel, motel, inn or other lodging
`establishment.
`industrial: The person is in an industrial setting, such as a
`manufacturing floor or power plant.
`library: The person is in a library or other public place which
`literary and artistic materials, such as books, periodicals,
`newspapers, pamphlets, prints, records, and tapes, are kept for
`reading, reference, or lending.
`office: The person is in a business setting, such as an office.
`outdoors: The person is in a general outdoor area, such as a park or
`city streets.
`other: The person is in a place without a <place-type>
`representation. The enclosed string describes the type of place.
`parking: The person is in a parking lot or parking garage.
`place-of-worship: A building where congregations gather for religious
`observances, such as a church, chapel, meetinghouse, mosque,
`shrine, synagogue, or temple.
`prison: The person is in a prison, penitentiary, jail, brig, or
`criminal mental institution.
`public: The person is in a public area such as a shopping mall,
`street, park, public building, train station, airport or in public
`conveyance such as a bus, train, plane or ship. This general
`description encompasses the more precise descriptors "street",
`"public-transport", "aircraft", "ship", "bus", "train", "airport",
`"mall" and "outdoors".
`public-transport: The person is using any form of public transport,
`including aircraft, bus, train or ship.
`residence: The person is in a private or residential setting, not
`necessarily the personal residence of the person, e.g., a friend's
`home.
`restaurant: The person is in a restaurant or other public dining
`establishment.
`school: The person is in a school or university, but not necessarily
`in a classroom or library.
`shopping-area: The person is frequenting a shopping mall or shopping
`area, i.e., a large, often enclosed shopping complex containing
`various stores, businesses, and restaurants usually accessible by
`common passageways.
`stadium: The person is in a large, usually open structure for sports
`events, including a racetrack.
`store: The person is located in a place where merchandise is offered
`for sale; a shop.
`
`Schulzrinne, et al.
`
`Expires June 23, 2006
`
`[Page 15]
`
`fiU.-//N-\TPV Patent FilinpS\IPVMC-Kwok\IPVMCP02-Comm Hub\Prior Art\draft-ietf-sim... 1/17/2007
`
`Epic Games Ex. 1029
`Page 242
`
`

`

`draft-ietf-simple-rpid-10.txt
`
`Page 16 of 41
`
`Internet-Draft
`
`RPID
`
`December 2005
`
`street: The person is walking in a street.
`theater: The person is in a theater, lecture hall, auditorium,
`circus, class room, movie theater or similar facility designed for
`presentations, talks, plays, movies, music performances and other
`events involving an audience.
`train: The person is traveling in a train, monorail, maglev, cable
`car or similar conveyance.
`train-station: The person is in a terminal where trains load or
`unload passengers or goods; railway station, railroad station,
`railroad terminal, train depot.
`truck: The person is in a truck, used primarily to carry goods rather
`than people.
`underway: The person is in a land, water, or air craft which is under
`way (in motion).
`unknown: The type of place is unknown.
`warehouse: The person is in a place in which goods or merchandise are
`stored; a storehouse or self-storage facility.
`water: The person is on water, such as an ocean, lake, river, canal
`or other waterway.
`watercraft: The person is traveling in a boat or ship.
`This list can be augmented by free-text values or additional IANA-
`registered values (Section 7).
`The <place-type> element is a choice of elements, as in
`<place-type>
`<street/>
`</place-type>
`
`The <place-type> element MAY be qualified with the 'from' and 'until'
`attributes as described in Section 3.1.
`
`3.8 Privacy Element
`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.
`
`Schulzrinne, et al.
`
`Expires June 23, 2006
`
`[Page 16]
`
`file://N:\TPV Patent Filines\IPVMC-Kwok\IPVMCP02-Comm Hub\Prior Art\draft-ietf-sim... 1/17/2007
`
`Epic Games Ex. 1029
`Page 243
`
`

`

`draft-ietf-simple-rpid-10.txt
`
`Page 17 of 41
`
`Internet-Draft
`
`RPID
`
`December 2005
`
`audio: Audio communication is likely only to be heard by the intended
`recipient.
`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 «privacys 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 as "private" to a select subset of the watchers.
`The «privacys element MAY be qualified with the 'from' and 'until'
`attributes as described in Section 3.1.
`Example:
`
`«privacys
`<text/s
`«audio/>
`«/privacys
`
`3.9 Relationship Element
`The «relationships element extends «tuples 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 «contacts element
`refers to the entity, such as the assistant, that has a relationship
`to the presentity, not the presentity itself.
`Like tuples without a «relationships qualifier, the «contacts 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:
`
`«relationships
`
`Schulzrinne, et al.
`
`Expires June 23, 2006
`
`[Page 17]
`
`file //N \TPV Patent Filings\TPVMC-Kwok\IPVMCP02-Comm HubVPrior Art\draft-ietf-sim... 1/17/2007
`
`Epic Games Ex. 1029
`Page 244
`
`

`

`draft-ietf-simple-rpid-10.txt
`
`Page 18 of 41
`
`Internet-Draft
`
`RPID
`
`December 2005
`
`<friend/>
`</relationship>
`
`3.10 Service Class
`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 mail
`room 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.
`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>
`
`3.11 Sphere Element
`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 or at home or participating in activities related to
`some other organization such as the IETF or a church. This document
`
`Schulzrinne, et al.
`
`Expires June 23, 2006
`
`[Page 18]
`
`file://N:\IPV Patent Filings\IPVMC-Kwok\IPVMCP02-Comm Hub\Prior Art\draft-ietf-sim... 1/17/2007
`
`Epic Games Ex. 1029
`Page 245
`
`

`

`dra ft-ietf-si mpl e-rpi d -10.txt
`
`Page 19 of 41
`
`Internet-Draft
`
`RPID
`
`December 2005
`
`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" or "home" or some other sphere,
`the fellow scouts would lose access.
`The «spheres element MAY be qualified with the 'from' and 'until'
`attributes as described in Section 3.1.
`Example:
`
`«spheres
`< home/>
`</spheres
`
`3.12 Status-Icon Element
`The <status-icon> element includes a URI pointing to an image (icon)
`representing the current status of the person or service. The
`watcher MAY use this information to represent the status in a
`graphical user interface. Presentities SHOULD provide images of
`sizes and aspect ratios that are appropriate for rendering as an
`icon. Support for JPEG, PNG and GIF formats is RECOMMENDED.
`Watchers resolving the URI MUST validate whether the local copy of
`the icon is current when receiving a notification, using the standard
`cache control mechanism in the URI-identified retrieval protocol.
`Example:
`
`«status-icon>http://www.example.com/playing.gif«/status-icon>
`
`3.13 Time Offset
`The <time-offset> element describes the number of minutes of offset
`from UTC at the person's current location. A positive number
`indicates that the local time-of-day is ahead (i.e., east of)
`
`Schulzrinne, et al.
`
`Expires June 23, 2006
`
`[Page 19]
`
`file://N:\IPV Patent Filines\IPVMC-Kwok\IPVMCP02-Comm Hub\Prior Art\draft-ietf-sim... 1/17/2007
`
`Epic Games Ex. 1029
`Page 246
`
`

`

`draft-ietf-simple-rpid-10.txt
`
`Page 20 of 41
`
`Internet-Draft
`
`RPID
`
`December 2005
`
`Universal Time, while a negative number indicates that the local
`time-of-day is behind (i.e., west of) Universal Time. Transitions
`into and out of daylight savings time may temporarily cause a
`difference between the true offset from UTC and the time offset
`element.
`An optional attribute, description, can be used to describe the
`offset, e.g., by labeling the time zone. This description is meant
`for human consumption.
`Publishers on mobile devices SHOULD NOT publish this information
`unless they know the time offset information to reflect the current
`location. (For example, many laptop users do not update their time
`zone when traveling.) Publishers SHOULD update the information
`whenever they discover that their UTC offset has changed.
`Example:
`
`<time-offset description="America/New_York">-300
`</time-offset>
`
`3.14 User-Input Element
`The <user-input> element records the user-input or usage state of the
`service or device, based on human user input, e.g., keyboard,
`pointing device or voice. If contained in a «persons element, it
`summarize any user input activity across all services and devices
`operated by the presentity. The mechanism for such aggregation is
`beyond the scope of this document, but generally reflects the most
`recent user input across all devices and services. The element can
`assume one of two values, namely 'active' or 'idle', with an optional
`'last-input' attribute that records when the last user input has been
`received. An optional 'idle-threshold' element records how long the
`presentity will wait before reporting the service or device to be
`idle, measured in seconds.
`(A two-state model was chosen since it would otherwise be necessary
`to send repeated last-input updates during continuous activity.)
`A service that wants to indicate user input activity sends a «user­
`input 'active' indication when the user has provided user input
`within a configurable interval of time, the idle-threshold. If the
`user ceases to provide input and the idle threshold has elapsed, the
`tuple is marked with a <user-input> 'idle' indication instead,
`optionally including the time of last activity in the 'last-input'
`
`Schulzrinne, et al.
`
`Expires June 23, 2006
`
`[Page 20]
`
`ftle://N:\IPV Patent Filings\IPVMC-Kwok\IPVMCP02-Comm HubVPrior Art\draft-ietf-sim... 1/17/2007
`
`Epic Games Ex. 1029
`Page 247
`
`

`

`draft-i etf-simple-rp id-10.txt
`
`Page 21 of 41
`
`Internet-Draft
`
`RPID
`
`December 2005
`
`attribute. An example is below:
`<user-input idle-threshold="600"
`last-input="2004-10-21T13:20:00.000-05:00">idle</user-input>
`Depending on device or service capabilities, user input may be
`detected only for a particular application, i.e., when the
`application has user focus or when a user has sent a message or
`placed a call, or can be based on user input across all applications
`running on one end system.
`The <user-input> element may be used by a watcher, typically in
`combination with other data, to estimate how likely a user is to
`answer when contacting the service. A tuple that has not been used
`in a while may still be OPEN, but a watcher may choose to first
`contact a URI in a tuple that is both OPEN and has been used more
`recently.
`The <user-input> attribute can be omitted if the presentity wants to
`indicate that the device has not been used for a while, but does not
`want to reveal the precise duration, as in:
`<user-input>idle</user-input>
`Configuration MUST include the option to omit the 'last-input'
`attribute.
`4. Example
`The example below describes the presentity
`'pres:someoneOexample.com' , which has a SIP contact,
`' sip:someone@example.com', representing a service. It also has a
`device contact, as an email box. The presentity is in a meeting, in
`a public office setting. The 'until' information indicates that he
`will be there until 5.30 pm local time. The presentity also has an
`assistant, sip:secretary@example.com, who happens to be available for
`communications.
`
`<?xml version="1.0" encoding="UTF-8"?>
`«presence xmlns="urn:ietf:params:xml:ns:pidf"
`xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
`xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model"
`xmlns:rpid="urn:ietf:params:xml:ns:pidf:rpid"
`xsi:schemaLocation="urn:ietf:params:xml:ns:pidf pidf.xsd
`urn:ietf:params:xml:ns:pidf:data-model data-model.xsd
`urn:ietf:params:xml:ns:pidf:rpid rpid.xsd"
`
`Schulzrinne, et al.
`
`Expires June 23, 2006
`
`[Page 21]
`
`file://N:\IPV Patent Filin2s\IPVMC-Kwok\IPVMCP02-Comm Hub\Prior Art\draft-ietf-sim... 1/17/2007
`
`Epic Games Ex. 1029
`Page 248
`
`

`

`draft-ietf-simple-rpid-10.txt
`
`Page 22 of 41
`
`Internet-Draft
`
`RPID
`
`December 2005
`
`ent ity="pres:someone@example.com">
`«tuple id="bs35r9"s
`«statuss
`«basicsopen«/basics
`«/statuss
`<dm:deviceID>urn:device:0 003ba4 811e3 «/dm:deviceIDs
`«rpid : relationships«rpid : self /></rpid: relationship>
`«rpid: service-classs«rpid: electronic/x/rpid: service-class>
`«contact priority^"0.8"sim: someone@mobile.example.net</contact>
`«note xml:lang="en"sDon't Disturb Please!«/notes
`«note xml:lang="fr">Ne derangez pas, s'il vous plait«/note>
`<timestamps2005-10-27T16 : 49:29Z«/timestamps
`«/tuples
`«tuple id="ty4658"s
`«statuss
`«basicsopen«/basics
`«/statuss
`<rpid:relationships«rpid:assistant/s«/rpid:relationships
`«contact priority="1.0"smailto:secretary@example.com«/contacts
`«/tuples
`«tuple id="eg92n8"s
`«statuss
`«basicsopen«/basics
`«/statuss
`«dm:deviceIDsurn:x-mac:00 03ba4 811e3 «/dm:deviceIDs
`«rpid:classsemail«/rpid:classs
`<rpid:service-classs«rpid: electronic/s</rpid:service-classs
`«rpid:status-iconshttp:I/example.com/mail.png«/rpid:status-icons
`«contact priority="1.0"smailto:someone@example.com«/contact>
`«/tuples
`«notesl'll be in Tokyo next week«/note>
`<dm:device id="pcl47"s
`«rpid:user-input idle -threshold=" 6 00"
`last-input="2 004-10 -21T13:20:00-05:00"sidle«/rpid:user-input >
`«dm:deviceIDsurn:device:0003ba4811e3«/dm;deviceIDs
`«dm:notesPC«/dm:notes
`«/dm:devices
`«dm:person id="pl"s
`«rpid:activities from="2005-05-30T12:00:00+05:00"
`until="2 005-05-30T17:00:00 + 05:00 " >
`«rpid:notesFar away«/rpid:notes
`«rpid:away/>
`
`Schulzrinne, et al.
`
`Expires June 23, 2006
`
`[Page 22]
`
`file://N:\IPV Patent Filings\IPVMC-Kwok\IPVMCP02-Comm Hub\Prior Art\draft-ietf-sim... 1/17/2007
`
`Epic Games Ex. 1029
`Page 249
`
`

`

`dra ft-i etf-si mple-rpid-10.txt
`
`Page 23 of 41
`
`Internet-Draft
`
`RPID
`
`December 2005
`
`c/rpid:activities>
`crpid:das s>cal endarc/rpid: class>
`crpid:mood>
`crpid:angry/>
`crpid:other>broodingc/rpid:other>
`c/rpid:mood>
`crpid:place-is>
`crpid: audio
`crpid:noisy/>
`c/rpid: audio
`c/rpid:place-is>
`crpid:place -type>crpid:residence/>c/rpid:place-type>
`crpid: privacy;» crpid: unknown/ >c/rpid: privacy>
`crpid:sphere>bowling leaguec/rpid:sphere>
`crpid: status - icoohttp: / /example . com/play. gif c/rpid: status-icon>
`crpid:time-offset>-240c/rpid:time-offset>
`cdm:note>Scoring 120c/dm:note>
`cdm: time st amp >2 005- 05 - 3 0T16 : 09 :44 + 05 : OOc/drn: timestamp:»
`c/dm: person:»
`c/presence>
`
`5.
`
`XML Schema Definitions
`The RPID schema is shown below. Due to limitations in composing
`schemas, not all XML documents that validate against the schema below
`are semantically valid RPID documents. In particular, the schema
`allows each element to appear anyhere in PIDF or data-model elements,-
`Table 1 restricts where these elements can appear for semantically
`valid RPID documents. Elements that do not have from/until
`parameters MUST NOT appear more than once in each cperson>, ctuple>
`or cdevice>.
`5.1 urn: ietf : params : xml: ns : pidf: rpid
`
`c?xml version="1.0" encoding="UTF-8"?>
`cxs:schema targetNamespace="urn:ietf:params:xml:ns:pidf:rpid"
`xmlns="urn:ietf:params:xml:ns:pidf:rpid"
`xmlns:dm="urn:ietf:params :xml:ns:pidf:data-model"
`xmlns:xs="http://www.w3.org/2001/XMLSchema"
`elementFormDefault="qualified"
`attributeFormDefault="unqualified">
`
`Schulzrinne, et al.
`
`Expires June 23, 2006
`
`[Page 23]
`
`file://N:\IPV Patent Filings\IPVMC-Kwok\IPVMCP02-Comm Hub\Prior Art\drafi-ietf-sim... 1/17/2007
`
`Epic Games Ex. 1029
`Page 250
`
`

`

`draft-ietf-simple-rpid-10.txt
`
`Page 24 of 41
`
`Internet-Draft
`
`RPID
`
`December 2005
`
`<xs:include schemaLocation="common-schema.xsd"/>
`<xs:simpleType name="activeldle">
`<xs:restriction base="xs:string">
`<xsenumeration value="active"/>
`<xs:enumeration value="idle"/>
`</xs:restriction>
`</xs:simpleType>
`<xs:element name="activities">
`<xs:annotation>
`<xs:documentation>
`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.
`</xs:documentation>
`</xs:annotation>
`<xs:complexType>
`<xs:sequence>
`<xs:element name="note" type="Note_t" minOccurs="0"/>
`<xs:choice>
`<xs:element name="unknown" type="empty" minOccurs="0"/>
`<xs:sequence maxOccurs="unbounded">
`<xs:choice>
`<xs:element name="appointment"
`type="empty" />
`<xs:element name="away"
`type="empty" />
`<xs:element name="breakfast"
`type="empty" />
`<xs:element name="busy"
`type="empty" />
`<xs:element name="dinner"
`type="empty" />
`<xs :element name="holiday"
`type="empty" />
`<xs:element name="in-transit"
`type="empty" />
`<xs:element name="looking-for-work"
`type="empty" />
`<xs:element name="meal"
`type="empty" />
`<xs :element name="meeting"
`type="empty" />
`<xs:element name="on-the-phone"
`type="empty" />
`<xs:element name="performance"
`
`Schulzrinne, et al.
`
`Expires June 23, 2006
`
`[Page 24]
`
`file://N:\IPV Patent Filings\IPVMC-Kwok\IPVMCP02-Comm HubVPrior Art\draft-ietf-sim... 1/17/2007
`
`Epic Games Ex. 1029
`Page 251
`
`

`

`draft-ietf-simple-rpid-10.txt
`
`Page 25 of 41
`
`Internet-Draft
`
`RPID
`
`December 2005
`
`type="empty" /?
`<xs:element name="permanent-absence"
`type="empty" /?
`<xs:element name="playing"
`type="empty" /?
`<xs:element name="presentation"
`type="empty" />
`<xs:element name="shopping"
`type="empty" /?
`<xs:element name="sleeping"
`type="empty" /?
`<xs:element name="spectator"
`type="empty" /?
`<xs:element name="steering"
`type="empty" />
`<xs:element name="travel
`type="empty" /?
`<xs:element name="tv"
`type="empty" />
`<xs:element name="vacation"
`type="empty" /?
`<xs:element name="working"
`type="empty" /?
`<xs:element name="worship"
`type="empty" /?
`<xs:element name="other"
`type="Note_t" />
`<xs:any namespace="##other"
`maxOccurs="unbounded" processcontents="lax"/>
`</xs:choice?
`</xs:sequence?
`</xs:choice?
`</xs:sequence?
`<xs : attribut.eGroup ref = "f romUntil"/?
`<xs:attribute name="id" type="xs:ID"/?
`<xs:anyAttribute namespace="##any" processContents="lax"/?
`</xs:complexType?
`</xs:element?
`<xs:element name="class" type="xs:token"?
`<xs:annotation?
`<xsdocumentation?
`Describes the class of the service, device or person.
`</xs:documentation?
`</xs:annotation?
`</xs:element ?
`<xs:element name="mood"?
`
`Schulzrinne, et al.
`
`Expires June 23, 2006
`
`[Page 25]
`
`file://N:\IPV Patent Filings\IPVMC-Kwok\IPVMCP02-Comm Hub\Prior Art\draft-ietf-sim... 1/17/2007
`
`Epic Games Ex. 1029
`Page 252
`
`

`

`draft-ietf-simple-rpid-10.txt
`
`Page 26 of 41
`
`Internet-Draft
`
`RPID
`
`December 2005
`
`<xs:annotations
`<xs : documentations
`Describes the mood of the presentity.
`</xs :documentation
`</xs:annotation)
`<xs : cotnplexType >
`<xs:sequence)
`<xs:element name="note" type = "Note_t" minOccurs="0"/>
`<xs:choices
`<xs:element name="unknown" type="empty"/>
`<xs:sequence maxOccurs="unbounded"s
`<xs:choices
`<xs:element name="afraid"
`type="empty"/>
`<xs:element name="amazed"
`type="empty"/>
`<xs;element name="angry"
`type="empty"/s
`<xs;element name="annoyed"
`type="empty"/>
`<xs:element name="anxious"
`type="empty" />
`<xs:element name="ashamed"
`type="empty" />
`<xs:element name="bored"
`type="empty" />
`<xs:element name="brave"
`type="empty" />
`<xs:element name="calm"
`type="empty" />
`<xs:element name="cold"
`type="empty" />
`<xs:element name="confused"
`type="empty" />
`<xs:element name="contented"
`type="empty" />
`<xs:element name="cranky"
`type="empty" />
`<xs:element name="curious"
`type="empty" />
`<xs:element name="depressed"
`type="empty" />
`<xs:element name="disappointed"
`type="empty" />
`<xs:element name="disgusted"
`type="empty" />
`<xs:element name="distracted"
`type="empty" />
`
`Schulzrinne, et al.
`
`Expires June 23, 2006
`
`[Page 26]
`
`file://N:\IPV Patent Filings\IPVMC-Kwok\IPVMCP02-Comm HubXPrior Art\draft-ietf-sim... 1/17/2007
`
`Epic Games Ex. 1029
`Page 253
`
`

`

`draft-ietf-simple-rpid-10.txt
`
`Page 27 of 41
`
`Internet-Draft
`
`RPID
`
`December 2005
`
`<xs:element name="embarrassed"
`type="empty" />
`<xs:element name="excited"
`type="empty" />
`<xs:element name="flirtatious"
`type="empty" />
`<xs:element name="frustrated"
`type="empty" />
`<xs:element name="grumpy"
`type="empty" />
`<xs:element name="guilty"
`type="empty" />
`<xs:element name="happy"
`type="empty" />
`<xs:element name="hot"
`type="empty" />
`<xs:element name="humbled"
`type="empty" />
`<xs .-element name= "humiliated"
`type="empty" />
`<xs:element name="hungry"
`type="empty" />
`<xs:element name="hurt"
`type="empty" />
`<xs:element name="impressed"
`type="empty" />
`<xs:element name="in_awe"
`type="empty" />
`<xs:element name="in_love"
`type="empty" />
`<xs:element name="indignant"
`type="empty" />
`<xs:element name="interested"
`type="empty" />
`<xs:element name="invincible"
`type="empty" />
`<xs:element name="jealous"
`type="empty" />
`<xs:element name="lonely"
`type="empty" />
`<xs:element name="mean"
`type="empty" />
`<xs:element name="moody"
`type="empty" />
`<xs:element name="nervous"
`type="empty" />
`<xs:element name="neutral"
`type="empty" />
`
`Schulzrinne, et al.
`
`Expires June 23, 2006
`
`[Page 27]
`
`file://N:\IPV Patent Filings\IPVMC-Kwok\IPVMCP02-Comm Hub\Prior Art\draft-ietf-sim... 1/17/2007
`
`Epic Games Ex. 1029
`Page 254
`
`

`

`draft-i etf-simple-rpid-10.txt
`
`Page 28 of 41
`
`Internet-Draft
`
`RPID
`
`December 2005
`
`<xs-.element name="offended"
`type="empty" />
`<xs:element name="playful"
`type="empty" />
`<xs:element name="proud"
`type="empty" />
`<xs:element name="relieved"
`type="empty" />
`<xs:element name="remorseful"
`type="empty" />
`<xs:element name="restless"
`type="empty" />
`<xs:element name="sad"
`type="empty" />
`<xs:element n