The Extensible Markup Language (XML) Configuration Access Protocol (XCAP)
draft-rosenberg-simple-xcap-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Author | Jonathan Rosenberg | ||
| Last updated | 2003-05-26 | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
htmlized
pdfized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of
the expired Internet-Draft can be found at:
https://www.ietf.org/archive/id/draft-rosenberg-simple-xcap-00.txt
https://www.ietf.org/archive/id/draft-rosenberg-simple-xcap-00.txt
Abstract
This specification defines the Extensible Markup Language (XML) Configuration Access Protocol (XCAP). XCAP allows a client to read, write and modify application configuration data, stored in XML format on a server. XCAP is not a new protocol. XCAP maps XML document sub-trees and element attributes to HTTP URIs, so that these components can be directly accessed by HTTP.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)