RFC 5261: An Extensible Markup Language (XML) Patch Operations Framework Utilizing XML Path Language (XPath) Selectors
In plain English — editorial summary, not part of the RFC
Extensible Markup Language (XML) documents are widely used as containers for the exchange and storage of arbitrary data in today's systems. In order to send changes to an XML document, an entire copy of the new version must be sent, unless there is a means of indicating only the portions that have changed. This document describes an XML patch framework utilizing XML Path language (XPath) selectors. These selector values and updated new data content constitute the basis of patch operations described in this document. In addition to them, with basic <add>, <replace>, and <remove> directives a set of patches can then be applied to update an existing XML document. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5261
- Published
- September 2008
- Authors
- J. Urpalainen
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 40
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5262Presence Information Data Format (PIDF) Extension for Partial PresenceCurrent
September 2008
- RFC 5263Session Initiation Protocol (SIP) Extension for Partial Notification of Presence InformationUpdated
September 2008
- RFC 5264Publication of Partial Presence InformationCurrent
September 2008
- RFC 5278IANA Registration of Enumservices for Voice and Video MessagingUpdated
July 2008
- RFC 5244Definition of Events for Channel-Oriented Telephony SignallingCurrent
June 2008
- RFC 5239A Framework for Centralized ConferencingCurrent
June 2008
- RFC 5285A General Mechanism for RTP Header ExtensionsObsoleted
July 2008
- RFC 5219A More Loss-Tolerant RTP Payload Format for MP3 AudioCurrent
February 2008
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?