One document matched: draft-zhao-simple-aipid-00.txt
Network Working Group Y. Zhao
Internet-Draft Q. Sun
Expires: January 18, 2008 Huawei Technologies
July 17, 2007
AIPID: Application Information for the Presence Information Data Format
draft-zhao-simple-aipid-00
Status of this Memo
By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on January 18, 2008.
Copyright Notice
Copyright (C) The IETF Trust (2007).
Zhao & Sun Expires January 18, 2008 [Page 1]
Internet-Draft AIPID July 2007
Abstract
Some of the user equipment's Application Information are valuable to
be shown by the Presence Service. The typical Application
Information is what song the presentity is listening to. The
Application Information for the Presence Information Data Format
(AIPID) is an extension that adds elements to the Presence
Information Data Format (PIDF) that provide additional Application
Information about a presentity.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. AIPID Elements . . . . . . . . . . . . . . . . . . . . . . . . 5
3.1. Music Element . . . . . . . . . . . . . . . . . . . . . . 5
3.2. Website Element . . . . . . . . . . . . . . . . . . . . . 5
3.3. Video Element . . . . . . . . . . . . . . . . . . . . . . 5
3.4. Game Element . . . . . . . . . . . . . . . . . . . . . . . 5
4. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
5. The XML Schema Definition . . . . . . . . . . . . . . . . . . 7
6. Security Considerations . . . . . . . . . . . . . . . . . . . 9
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
8. Acknowledges . . . . . . . . . . . . . . . . . . . . . . . . . 11
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 12
9.1. Normative References . . . . . . . . . . . . . . . . . . . 12
9.2. Informative References . . . . . . . . . . . . . . . . . . 12
Appendix A. History of change . . . . . . . . . . . . . . . . . . 13
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 14
Intellectual Property and Copyright Statements . . . . . . . . . . 15
Zhao & Sun Expires January 18, 2008 [Page 2]
Internet-Draft AIPID July 2007
1. Introduction
Presence Service is useful to let a user share his/her information to
his/her friends. Some of these information is application-specific.
For example, when a user is listening to a pop music and he/she wants
to let his/her friends know that he/she is enjoying that music now,
he/she can set his/her presence client to catch the music information
from his media player or let his media player submit such information
to the presence client. This specification describes a typical set
of application information elements that allow a watcher to retrieve
such information about a presentity.
All elements extend the <person> in the presence data model [2].
They provide some typical application information related to the
music, video, game or website the presentity's application program is
processing. All these elements are optional.
Zhao & Sun Expires January 18, 2008 [Page 3]
Internet-Draft AIPID July 2007
2. Terminology
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 RFC 2119 [1]
Zhao & Sun Expires January 18, 2008 [Page 4]
Internet-Draft AIPID July 2007
3. AIPID Elements
3.1. Music Element
The <listening> element includes a child element <title> indicating
the name of the music the presentity is listening to. The <resource>
child-element provides a URI to let watchers know where they can
download this music. The presentity or the application can submit
some remarks to this music by using the <note> child-element.
3.2. Website Element
The <surfing> element includes a child element <title> indicating the
name of the website the presentity is surfing. The <resource> child-
element provides a URI to let watchers know how to access this
website. The presentity or the application can submit some remarks
to this website by using the <note> child-element.
3.3. Video Element
The <watching> element includes a child element <title> indicating
the name of the video the presentity is watching. The <resource>
child-element provides a URI to let watchers know where they can
download this video. The presentity or the application can submit
some remarks to this video by using the <note> child-element.
3.4. Game Element
The <gaming> element includes a child element <title> indicating the
name of the game the presentity is playing. The <resource> child-
element provides an official website to let watchers know where they
can begin to play the game. The presentity or the application can
submit some remarks to this game by using the <note> child-element.
Zhao & Sun Expires January 18, 2008 [Page 5]
Internet-Draft AIPID July 2007
4. Examples
An example using AIPID is shown below:
<?xml version="1.0" encoding="UTF-8"?>
<presence xmlns="urn:ietf:params:xml:ns:pidf"
xmlns:pdm="urn:ietf:params:xml:ns:pidf:data-model"
xmlns:rpid="urn:ietf:params:xml:ns:pidf:rpid"
xmlns:a="urn:ietf:params:xml:ns:pidf:aipid"
entity="sip:someone@example.com">
<pdm:person id="a1233">
<rpid:activities>
<rpid:meal/>
</rpid:activities>
<a:listening>
<a:title>example music</a:title>
<a:resource>http://music.example.com</a:resource>
<a:note>That's a wonderful music!</a:note>
</a:listening>
<pdm:timestamp>2007-07-16T12:14:56Z</pdm:timestamp>
</pdm:person>
</presence>
Zhao & Sun Expires January 18, 2008 [Page 6]
Internet-Draft AIPID July 2007
5. The XML Schema Definition
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema targetNamespace="urn:ietf:params:xml:ns:pidf:aipid"
xmlns:aipid="urn:ietf:params:xml:ns:pidf:aipid"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified"
attributeFormDefault="unqualified">
<xs:annotation>
<xs:documentation>
Describes AIPID tuple extensions for PIDF.
</xs:documentation>
</xs:annotation>
<xs:element name="listening">
<xs:complexType>
<xs:sequence>
<xs:element name="title" type="xs:string"/>
<xs:element name="resource" type="xs:anyURI"/>
<xs:element name="note" type="Note_t"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="surfing">
<xs:complexType>
<xs:sequence>
<xs:element name="title" type="xs:string"/>
<xs:element name="resource" type="xs:anyURI"/>
<xs:element name="note" type="Note_t"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="watching">
<xs:complexType>
<xs:sequence>
<xs:element name="title" type="xs:string"/>
<xs:element name="resource" type="xs:anyURI"/>
<xs:element name="note" type="Note_t"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="gaming">
<xs:complexType>
<xs:sequence>
Zhao & Sun Expires January 18, 2008 [Page 7]
Internet-Draft AIPID July 2007
<xs:element name="title" type="xs:string"/>
<xs:element name="resource" type="xs:anyURI"/>
<xs:element name="note" type="Note_t"/>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:schema>
Zhao & Sun Expires January 18, 2008 [Page 8]
Internet-Draft AIPID July 2007
6. Security Considerations
TBD
Zhao & Sun Expires January 18, 2008 [Page 9]
Internet-Draft AIPID July 2007
7. IANA Considerations
TBD
Zhao & Sun Expires January 18, 2008 [Page 10]
Internet-Draft AIPID July 2007
8. Acknowledges
TBD
Zhao & Sun Expires January 18, 2008 [Page 11]
Internet-Draft AIPID July 2007
9. References
9.1. Normative References
[1] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", RFC 2119, March 1997.
9.2. Informative References
[2] Rosenberg, J., "A Data Model for Presence", RFC 4479, July 2006.
Zhao & Sun Expires January 18, 2008 [Page 12]
Internet-Draft AIPID July 2007
Appendix A. History of change
This is the first version of this draft.
Zhao & Sun Expires January 18, 2008 [Page 13]
Internet-Draft AIPID July 2007
Authors' Addresses
Yang Zhao
Huawei Technologies
Bantian Longgang
Shenzhen, Guandong 518129
P.R China
Phone: +86 755 28780808
Email: yangzhao@huawei.com
Qian Sun
Huawei Technologies
Bantian Longgang
Shenzhen, Guandong 518129
P.R China
Phone: +86 755 28780808
Email: sunqian@huawei.com
Zhao & Sun Expires January 18, 2008 [Page 14]
Internet-Draft AIPID July 2007
Full Copyright Statement
Copyright (C) The IETF Trust (2007).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at
ietf-ipr@ietf.org.
Acknowledgment
Funding for the RFC Editor function is provided by the IETF
Administrative Support Activity (IASA).
Zhao & Sun Expires January 18, 2008 [Page 15]
| PAFTECH AB 2003-2026 | 2026-04-24 02:51:11 |