W3C home > Mailing lists > Public > public-qt-comments@w3.org > March 2004

RE: [F&O] BEA_034

From: Ashok Malhotra <ashokma@microsoft.com>
Date: Mon, 29 Mar 2004 14:42:01 -0800
Message-ID: <EDB607C8AC991F40BE646533A1A673E801AAE725@RED-MSG-42.redmond.corp.microsoft.com>
To: "Daniela Florescu" <danielaf@bea.com>, <public-qt-comments@w3.org>

Dana:
Thank you for your comment.  This was discussed at the joint WG meeting
Cannes.  The relevant extract from the minutes reads:
"... the wg can see the value of this functionality, so we'll add this
to the "todo list" for v-next (v2), either for this specific feature,
and
possibly in relation to the more general try/catch feature."

No change to existing documents.

All the best, Ashok

-----Original Message-----
From: public-qt-comments-request@w3.org
[mailto:public-qt-comments-request@w3.org] On Behalf Of Daniela Florescu
Sent: Wednesday, February 18, 2004 12:11 PM
To: public-qt-comments@w3.org
Subject: [F&O] BEA_034


Function and Operators: request for functionality


It is often required to test if a data model instance
would validate correctly, without actually attempting the
validation operation (which, if unsuccessful, raises
an irrecoverable error).

The signature of the function is:

fn:validatesCorrectly($x as node*) as xs:boolean
/* the name doesn't matter of course */

The semantics can be defined in terms of the validate{} expression:
validatesCorrectly($x) returns true if and only if the expression 
validate{$x}
would perform correctly and not would raise a dynamic error.

(As for any other expression) a query processor is allowed to statically
evaluate the function to either true or false if there is guaranteed 
that
the dynamic phase would evaluate it to the same value.

Best regards.
Received on Monday, 29 March 2004 17:42:09 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 5 February 2014 07:13:56 UTC