XQuery Update Facility 1.0 Requirements /**/ code { font-family: monospace; }
div.constraint, div.issue, div.note, div.notice { margin-left: 2em; }
div.issue p.title { margin-left: -2em; }
ol.enumar { list-style-type: decimal; } ol.enumla { list-style-type: lower-alpha; } ol.enumlr { list-style-type: lower-roman; } ol.enumua { list-style-type: upper-alpha; } ol.enumur { list-style-type: upper-roman; }
li p { margin-top: 0.3em; margin-bottom: 0.3em; }
sup small { font-style: italic; color: #8F8F8F; } div.exampleInner pre { margin-left: 1em; margin-top: 0em; margin-bottom: 0em} div.exampleOuter {border: 4px double gray; margin: 0em; padding: 0em} div.exampleInner { background-color: #d5dee3; border-top-width: 4px; border-top-style: double; border-top-color: #d3d3d3; border-bottom-width: 4px; border-bottom-style: double; border-bottom-color: #d3d3d3; padding: 4px; margin: 0em } div.exampleWrapper { margin: 4px } div.exampleHeader { font-weight: bold; margin: 4px}
div.issue { border-bottom-color: black; border-bottom-style: solid; border-bottom-width: 1pt; margin-bottom: 20pt; }
th.issue-toc-head { border-bottom-color: black; border-bottom-style: solid; border-bottom-width: 1pt; }
table.small { font-size: x-small; } a.judgment:visited, a.judgment:link { font-family: sans-serif; color: black; text-decoration: none } a.processing:visited, a.processing:link { color: black; text-decoration: none } a.env:visited, a.env:link { color: black; text-decoration: none } /**/ This version: http://www.w3.org/TR/2011/NOTE-xquery-update-10-requirements-20110125/ Latest version: http://www.w3.org/TR/xquery-update-10-requirements/ Previous version: http://www.w3.org/TR/2008/CR-xquery-update-10-requirements-20080314/ Editors: Don Chamberlin, IBM Almaden Research Center <[email protected]> Jonathan Robie, Red Hat <[email protected]> Copyright W3C ® MIT ERCIM Keio liability trademark document use This document specifies goals and requirements for the XQuery Update Facility. This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index This is a Working Group Note Process Document XML Query Working Group XML Activity This document includes, for each requirement, a corresponding status, indicating the current situation of the requirement in XQuery Update Facility 1.0 "Green" status "Yellow" status "Red" status No substantive changes have been made to this specification since its publication as a Proposed Recommendation. Please report errors in this document using W3C's public Bugzilla system http://www.w3.org/XML/2005/04/qt-bugzilla [email protected] http://lists.w3.org/Archives/Public/public-qt-comments/ Publication as a Working Group Note This document was produced by a group operating under the 5 February 2004 W3C Patent Policy public list of any patent disclosures Essential Claim(s) section 6 of the W3C Patent Policy 1 Goals Usage Scenarios Requirements Terminology General Requirements Relationship to XQuery 1.0 XML Query Update Functionality Transaction characteristics A References This document describes the requirements for the XQuery Update Facility. [XQuery 1.0] The following usage scenarios describe how the XQuery Update Facility may be used in various environments, and represent a wide range of activities and needs that illustrate the problem space to be addressed. They are intended to be used as design cases during the development of the XQuery Update Facility, and should be reviewed when critical decisions are made. These usage scenarios should also prove useful in helping non-members of the XML Query Working Group understand the intent and goals of the project. 2.1 Updating persistent XML stores Modify XML in persistent XML stores, including native XML databases, XML files stored on a file system, or XML stored in SQL databases. 2.2 Modify XML messages Modify XML messages to change status and add information created while processing the message. 2.3 Add to existing XML document Add new data to an existing XML document; for instance, add a new entry to a BLOG or a data log. 2.4 Updating XML registries Perform updates on configuration files, user profiles, or administrative logs represented in XML. 2.5 Creating edited copies Create a new copy of an XML document or subtree that differs from the original in the way specified by the update. For instance, updates could be used to modify a web message in order to add new information and change headers to reflect the modified status. 2.6 Modifying XML views Modifying XML views of non-XML sources, such as a [SQL/XML] The following key words are used throughout the document to specify the extent to which an item is a requirement for the work of the XML Query Working Group: This word means that the item is an absolute requirement. This word means that there may exist valid reasons not to treat this item as a requirement, but the full implications should be understood and the case carefully weighed before discarding this item. This word means that an item deserves attention, but further study is needed to determine whether the item should be treated as a requirement. When the words MUST SHOULD MAY 3.2.1 Query Update Syntax The syntax for updates MAY MUST Status: One syntax MUST Status: 3.2.2 Declarativity The XQuery Update Facility MUST MUST Status: 3.2.3 Protocol Independence The XQuery Update Facility MUST Status: 3.2.4 Error Conditions The XQuery Update Facility MUST Status: 3.2.5 Static Type Checking The XQuery Update Facility SHOULD Status: 3.3.1 Based on Data Model The XQuery Update Facility MUST [XQuery 1.0 and XPath 2.0 Data Model] Status: Note: The properties of a Data Model instance that can be modified by the XQuery Update Facility are discussed in 3.4 XML Query Update Functionality 3.3.2 Based on XQuery The XQuery Update Facility MUST [XQuery 1.0] MUST MUST Status: 3.4.1 Locus of modifications The XQuery Update Facility MUST MUST Status: 3.4.2 Delete The XQuery Update Facility MUST Status: 3.4.3 Insert The XQuery Update Facility MUST Status: 3.4.4 Replace The XQuery Update Facility MUST Status: 3.4.5 Changing values The XQuery Update Facility MUST Status: 3.4.6 Modifying properties The XQuery Update Facility SHOULD Status: 3.4.7 Moving nodes The XQuery Update Facility MAY Status: 3.4.8 Conditional updates The XQuery Update Facility MUST Status: 3.4.9 Iterative updates The XQuery Update Facility MUST Status: 3.4.10 Validation The XQuery Update Facility MAY Note: The XQuery 1.0 validate expression creates a new copy of each validated node, with a new identity. This requirement involves preservation of identity. 3.4.11 Compositionality The XQuery Update Facility MUST Status: The XQuery Update Facility MAY Status: 3.4.12 Parameterization The XQuery Update Facility SHOULD Status: In this section, the terms Atomicity, Consistency, Isolation, and Durability are taken from the ACID model of transaction characteristics for databases, which is described in [Transaction Processing Concepts and Techniques] 3.5.1 Atomicity The XQuery Update Facility MUST MUST Status: 3.5.2 Consistency At the end of an outermost update operation (that is, an update operation invoked from the external environment), the data model MUST MUST Status: The XQuery Update Facility MAY Status: 3.5.3 Isolation The XQuery Update Facility SHOULD 3.5.4 Durability The XQuery Update Facility MUST Gray, J. and Reuter, A. 1994. Transaction Processing Concepts and Techniques International Organization for Standardization (ISO). ISO/IEC 9075-14:2008, Information Technology - Database Languages - SQL - Part 14, XML-Related Specifications (SQL/XML) XQuery 1.0 and XPath 2.0 Data Model (XDM) (Second Edition) et. al. latest version XQuery 1.0: An XML Query Language (Second Edition) et. al. latest version