An Extensible Markup Language (XML) Configuration Access Protocol (XCAP) Usage for XML Documents Directory
draft-garcia-simple-xcap-directory-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Author | Miguel Angel García | ||
| Last updated | 2004-06-09 | ||
| 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-garcia-simple-xcap-directory-00.txt
https://www.ietf.org/archive/id/draft-garcia-simple-xcap-directory-00.txt
Abstract
The general assumption of XCAP is that a client selects a document in a XCAP server in order to manipulate data. This requires the XCAP client to know the path of the XCAP-manipulatable XML document stored in the XCAP server. This specification allows an XCAP client to retrieve its directory of XCAP-manipulatable XML documents from an XCAP server.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)