W3C home > Mailing lists > Public > public-qt-comments@w3.org > January 2011

[Bug 11682] under-specification of func-available-environment-variables and unc-available-environment-variable

From: <bugzilla@jessica.w3.org>
Date: Sun, 09 Jan 2011 21:01:38 +0000
To: public-qt-comments@w3.org
Message-Id: <E1Pc2OQ-000228-9A@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11682

--- Comment #2 from Daniela Florescu <dflorescu@mac.com> 2011-01-09 21:01:37 UTC ---
I disagree with the answer in #2. 

All the mentioned problems in my original bug report are more a justification
to eliminate 
such functions from the XQuery 3.0 standard, rather then to complicate the
specification
unnecessarily even more in order to "fix" those problems.

I think those functions should be eliminated from the standard for the
following reasons:
- they are not part of any user requirements
- the are 100% implementation dependent (no standard semantics of any kind)
- they are untestable
- they make no technical sense on environments that use virtualized
infrastructure (aka cloud)
- if implemented, they create a security breach

For all the above reasons, obliging all XQuery processors to implement such
functions makes
no sense. They should not be part of "core" XQuery.

However, this looks like a great submission for particular modules, to be
standardized by
EXPath for example. That's the entire purpose of such organization.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Sunday, 9 January 2011 21:01:40 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:45:45 UTC