CurrentPROPOSED STANDARDIETF stream

RFC 4825: The Extensible Markup Language (XML) Configuration Access Protocol (XCAP)

In plain English — editorial summary, not part of the RFC

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 maps XML document sub-trees and element attributes to HTTP URIs, so that these components can be directly accessed by HTTP. [STANDARDS-TRACK]

Document record

Document ID
RFC4825
Published
May 2007
Authors
J. Rosenberg
Status
PROPOSED STANDARD
Stream
IETF
Area
rai
Pages
71
Also known as
—

Topics

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/4825-the-extensible-markup-language-xml-configuration-access-protocol-xcap