W3C home > Mailing lists > Public > public-qt-comments@w3.org > August 2006

[Bug 3578] Issues with May 8th Usecase Draft

From: <bugzilla@wiggum.w3.org>
Date: Thu, 03 Aug 2006 03:20:31 +0000
CC:
To: public-qt-comments@w3.org
Message-Id: <E1G8Tl9-0007b2-Jr@wiggum.w3.org>

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

           Summary: Issues with May 8th Usecase Draft
           Product: XPath / XQuery / XSLT
           Version: Working drafts
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Update Facility Use Cases
        AssignedTo: andrew.eisenberg@us.ibm.com
        ReportedBy: simeon@us.ibm.com
         QAContact: public-qt-comments@w3.org


Use Case "R"
============

Q4: Tries to set Annabel Lee's rating to "B". But Annabel Lee was 
inserted (Q1) without any rating, so "replace value of" would
have an empty target.

Use Case "Parts"
================

The intro talks about a "partlist.xml", but the queries access
a "part-list.xml"

Q3: Neither solution 1, nor solution 3 lead to the expected result.
Solution 1 doesn't delete piston, window and lock.
The recursive function is solution 2 is also incorrect, as it
deletes in "part-tree.xml" at the first call and in "part-list.xml"
at subsequent calls.

Q4: The note says that "as last into" should be used if position is
important, but the expected result shows that the "radio" element
is inserted as the first child of "car", not as the last one.

Use Case "SOAP"
===============

A few typos:
* count($returnDepartingAirports)>1
(the one is missing)
* has a call to currentdateTime() instead of current-dateTime() 
* should use string() instead of string-value()
* call to local:airports($in) fails because $in is undefined;
  local:airports($out//env:Body) should be used

Use Case "Address Book"
=======================

- Typo: a comma is missing after 
"do replace value of $v2/contact with $v1/contact"

I believe the current version of the address book use case raises a 
replace-replace
conflict. The reason is that there is a loop within which we do the same 
replace:

for $a in doc("archive.xml")/archived-agenda/entry, 
    $v1 in doc("copy1.xml")/agenda-version/entry, 
    $v2 in doc("copy2.xml")/agenda-version/entry
where $a/name = $v1/name
  and $v1/name = $v2/name
...
return
...
            do replace value of 
               doc("archive.xml")/*/last-synch-time
            with current-dateTime()

here doc("archive.xml")/*/last-synch-time

keeps pointing to the same node and therefore there will be multiple 
replaces
over the same node in the pending update list, which raises a conflict 
when applying
them.

- Jerome
Received on Thursday, 3 August 2006 03:20:41 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 March 2012 18:14:44 GMT