Extensible Markup Language (XML) Formats for Representing Resource Lists
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 31
- Abstract
- In multimedia communications, presence, and instant messaging systems, there is a need to define Uniform Resource Identifiers (URIs) that represent services that are associated with a group of users. One example is a resource list service. If a user sends a Session Initiation Protocol (SIP) SUBSCRIBE message to the URI representing the resource list service, the server will obtain the state of the users in the associated group, and provide it to the sender. To facilitate definition of these services, this specification defines two Extensible Markup Language (XML) documents. One document contains service URIs, along with their service definition and a reference to the associated group of users. The second document contains the user lists that are referenced from the first. This list of users can be utilized by other applications and services. Both documents can be created and managed with the XML Configuration Access Protocol (XCAP). [STANDARDS-TRACK]
- Publication Date
- 2007-05-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC4826- Link
- https://doi.org/10.17487/RFC4826
- Author(s)
- Jonathan Rosenberg
- Keyword(s)
- HTTP, SIP, XML, REST, Buddy List, Simple, Presence
Latest version of IETF RFC 4826
Document Versions — IETF RFC 4826
-
▶ IETF RFC 4826 (2007-05-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- IETF RFC 2119 [Active*]
- IETF RFC 2141 [Superseded*]
- IETF RFC 2648 [Active*]
- IETF RFC 3023 [Superseded*]
- IETF RFC 3261 [Active*]
- IETF RFC 3688 [Active*]
- IETF RFC 3986 [Active, Amended*]
- IETF RFC 4288 [Superseded*]
- IETF RFC 4825 [Active*]
- W3C.xml.20001006 — W3C Recommendation, 6 October 2000, October 2000 EXTERNAL
Bibliographic Reference(s)
- Rosenberg, J., "Presence Authorization Rules" , Work in Progress, October 2006. EXTERNAL
- IETF RFC 3265 [Superseded*]
- IETF RFC 3856 [Active*]
- IETF RFC 3859 [Active*]
- IETF RFC 4662 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC4826.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 4826, Extensible Markup Language (XML) Formats for Representing Resource Lists. Available at https://doi.org/10.17487/RFC4826
Snippet:
IETF RFC 4826, Extensible Markup Language (XML) Formats for Representing Resource Lists. Available at https://doi.org/10.17487/RFC4826
HTML (ISO 690 compliant)
Preview:
IETF RFC 4826, Extensible Markup Language (XML) Formats for Representing Resource Lists. Available at https://doi.org/10.17487/RFC4826
Snippet:
<span class="citation"><cite>IETF RFC 4826</cite>, Extensible Markup Language (XML) Formats for Representing Resource Lists. Available at <a href="https://doi.org/10.17487/RFC4826" target="_blank" rel="noopener">https://doi.org/10.17487/RFC4826</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 4826, Extensible Markup Language (XML) Formats for Representing Resource Lists
doi: 10.17487/RFC4826
url: https://doi.org/10.17487/RFC4826
doi: 10.17487/RFC4826
url: https://doi.org/10.17487/RFC4826
Snippet:
<li> <cite id="bib-rfc4826">IETF RFC 4826</cite>, Extensible Markup Language (XML) Formats for Representing Resource Lists <span class="doi">10.17487/RFC4826</span> </li>
Referenced By
- IETF RFC 4825 [Active*]
- IETF RFC 5318 [Active*]
- IETF RFC 5360 [Active*]
- IETF RFC 5362 [Active*]
- IETF RFC 5364 [Active*]
- IETF RFC 5365 [Active*]
- IETF RFC 5366 [Active*]
- IETF RFC 5367 [Active*]
- IETF RFC 5368 [Active*]
- IETF RFC 5989 [Active*]