[Bug 26958] On not precluding updates in XQuery 3.0

https://www.w3.org/Bugs/Public/show_bug.cgi?id=26958

--- Comment #3 from Jonathan Robie <jonathan.robie@gmail.com> ---
(In reply to Michael Kay from comment #2)

Our requirement is to support in-situ updates of maps and arrays, but I agree
that thinking of this in terms of the databases that need it is helpful.

I'd like to rely on database models already in use in XML databases, JSON-based
NoSQL databases, and relational databases. In most places I know of, data is
stored as either JSON or XML, but not as a hybrid of both. I want to have
databases that can store collections of XML documents or JSON objects, and I
want to be able to query and use both kinds of data.  They may well be
different physical stores.

In MongoDB and most similar databases, each JSON object is stored independently
of other objects, a given map or array cannot be contained by two different
maps or arrays. I believe this is also true of JSON support in SQL. This also
mirrors what would happen in a naive file-based implementation if we serialize
JSON and allow it to be updated. If we did anything different, I just don't
think many vendors would implement our model. JSON does not have pointers, if
you need cross references among maps you can do it by creating a GUID to
represent the identity of a map, and use the same GUID for references to the
map. I do not think we should try to go beyond this. Let's keep it simple.

I'll address the issue of XML contained in JSON in the next comment.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Friday, 3 October 2014 13:44:17 UTC