RE: [XPath] Request XPath implementations be required to do some static type checking on the schema-element function

 
> implementations are allowed to raise these errors or warnings

Thanks Michael. I understand.  I would like the specification to be
changed from MAY to MUST.  That is, implementations MUST raise an error
or warning.

/Roger


-----Original Message-----
From: Michael Rys [mailto:mrys@microsoft.com] 
Sent: Thursday, March 27, 2008 2:08 PM
To: Costello, Roger L.; public-qt-comments@w3.org
Subject: RE: [XPath] Request XPath implementations be required to do
some static type checking on the schema-element function

Dear Roger, such error messages are being raised by the static typing
semantics and implementations are allowed to raise these errors or
warnings either doing dynamic or static typing.

Best regards
Michael

-----Original Message-----
From: public-qt-comments-request@w3.org
[mailto:public-qt-comments-request@w3.org] On Behalf Of Costello, Roger
L.
Sent: Thursday, March 27, 2008 4:45 AM
To: public-qt-comments@w3.org
Subject: [XPath] Request XPath implementations be required to do some
static type checking on the schema-element function


Hi Folks,

I would like to request a small change to the XPath 2.0 specification.

I would like to request that XPath implementations be required to
generate an error or warning message for expressions like this:

    schema-element(Book)/Foo

where Foo is not a valid child of Book, according to the in-scope
schema.

Further, implementations be required to generate an error or warning
message for expressions like this:

   schema-element(Book)/Author/FirstNam

where, according to the in-scope schema, Author is a valid child of
Book but FirstNam (note that I misspelled Name) is not.

Thank you very much for your consideration.

  -- Roger L. Costello

Received on Thursday, 27 March 2008 19:32:03 UTC