- From: Michael Rys <mrys@microsoft.com>
- Date: Mon, 16 Feb 2004 18:35:04 -0800
- To: "Daniela Florescu" <danielaf@bea.com>
- Cc: <public-qt-comments@w3.org>
I think that there is a much larger use case for allowing to query typed data. So I am reluctant to bind the output typing to the input typing of data. If you only mean the syntactic schema import part and allow implementations to use external means to populate the in-scope schema definitions for providing the type information for the input data, I could live with that, although I think that would minimize the portability if users cannot write the import schema statement to indicate that they have imported that information (even if it was already imported by the implementation). Best regards Michael > -----Original Message----- > From: Daniela Florescu [mailto:danielaf@bea.com] > Sent: Monday, February 16, 2004 4:20 PM > To: Michael Rys > Cc: public-qt-comments@w3.org > Subject: Re: [XQuery] MS-XQ-LC1-124 > > > Thus we would like to propose: > > 1. Make default validation mode to be skip > > Agreed. > > > 2. Remove Schema context from the spec > > Agreed. > > > 3. Make support for validation modes lax and strict and the validate > > keyword an optional feature. > > XQuery has already too many optional features (people are > already complaining that it doesn't look like a standard) > We should try to minimize them, not to add more of them. > > Could we tie it with schema import ? > > Best regards, > Dana
Received on Monday, 16 February 2004 21:34:34 UTC