W3C home > Mailing lists > Public > public-qt-comments@w3.org > January 2007

[Bug 4286] Implementation-defined persistence

From: <bugzilla@wiggum.w3.org>
Date: Mon, 29 Jan 2007 21:59:44 +0000
CC:
To: public-qt-comments@w3.org
Message-Id: <E1HBeXQ-0000m6-Qq@wiggum.w3.org>

http://www.w3.org/Bugs/Public/show_bug.cgi?id=4286

           Summary: Implementation-defined persistence
           Product: XPath / XQuery / XSLT
           Version: Working drafts
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Update Facility
        AssignedTo: andrew.eisenberg@us.ibm.com
        ReportedBy: jonathan.robie@datadirect.com
         QAContact: public-qt-comments@w3.org


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.
Received on Monday, 29 January 2007 21:59:52 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:45:32 UTC