- From: <bugzilla@jessica.w3.org>
- Date: Mon, 27 Oct 2014 23:20:35 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26958 Michael Kay <mike@saxonica.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED |--- --- Comment #14 from Michael Kay <mike@saxonica.com> --- I do not want F+O discussions of operators such as map:merge to contain any mention of concepts like "copying" a map or array. It's a meaningless concept at that level. Specs should be testable, and there is no way of testing whether map:merge has copied a map or array or not, therefore the spec should have nothing to say on the subject. Any discussion of identity-based semantics for maps and arrays must be confined solely to the Update specs, plus if necessary a permissive enabling statement in the data model to legitimize it. I don't think the issue is resolved by leaving it to the editors, since I suspect that different editors will go off in different directions. Therefore re-opening. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Monday, 27 October 2014 23:20:36 UTC