This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Currently, persistence is completely undefined in the XQuery Update Facility. 3.2.2 applyUpdates says: > Propagation of XDM changes to an underlying physical representation is beyond > the scope of this specification. For example, the effect on physical storage > of deleting a node that has no parent is beyond the scope of this > specification. I think that an implementation should document whether the resources a user cares about, such as files or database data, are actually changed. For instance, most users probably want to know whether an implementation actually deletes a node in an XML file or a row of a relational database as a result of a delete expression. Thus, the mapping of updates from the XDM instance to software systems should probably be implementation-defined. However, it is also true that there are some error conditions that can not be completely documented. We need to find a reasonable way to allow for this.
The Working Group, of which you are a member, discussed this bug and agreed that it is not in the scope of XQuery Update 1.0 to address the subject of persistence beyond the persistence of updates within an XDM instance. Since you have raised no objection to this decision, we are marking this bug CLOSED.