- From: <bugzilla@farnsworth.w3.org>
- Date: Mon, 21 Apr 2008 14:54:32 +0000
- To: public-qt-comments@w3.org
- CC:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=5646 ------- Comment #1 from frans.englich@telia.com 2008-04-21 14:54 ------- Yupp, making fn:put an updating expression has been suggested a couple of times, and its low amount of specification has been pointed out too: http://www.w3.org/Bugs/Public/show_bug.cgi?id=5314 Don's summary in 5314 isn't very useful in my opinion, essentially stating that things are as they are because they were written as so, not detailing the reasoning behind it. Leaving conflict analysis(or just in general having fn:put() an update operation and hence within the "update framework") implementation defined has negative impacts on interoperability, so the advantages it brings must be strong and clear to outweight it. Currently I don't see how conflict analysis would constrain implementers, but rather that it would make the language more predictable for users.
Received on Monday, 21 April 2008 14:55:06 UTC