Re: XQuery Updates: Call for Use Cases

1)       There is no specification concerning the issues of XQuery DDL
syntax and semantics so far. Are you planning to include CREATE and DROP
document (and e.t.c.) statements to the update specification or this the
subject for individual specification?

2)       The "Changing values" functionality seems to be the potential cause
of the appearance of the ambiguities during the document update: as far as
changing the typed-value of the node doesn't uniquely determines the
modification of the node' content.

3)       "The XQuery Update Facility
<http://www.w3.org/TR/xquery-update-requirements/#terminology-must> MUST be
able to change the properties of existing nodes while preserving their
identity". I guess it is very problematically to fulfil this property in
some native XDBMS implementations, since such a properties of the node like
'parent' property is strongly connected to the node identity (for instance,
when numbering scheme is used for node identification)

 

Regards, Leonid Novak.