W3C home > Mailing lists > Public > public-qt-comments@w3.org > November 2010

[Bug 11095] Lack of clarity on 'unknown' types

From: <bugzilla@jessica.w3.org>
Date: Thu, 04 Nov 2010 13:52:51 +0000
To: public-qt-comments@w3.org
Message-Id: <E1PE0FH-0007rI-Fk@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11095

--- Comment #2 from Jonathan Robie <jonathan.robie@redhat.com> 2010-11-04 13:52:51 UTC ---
(In reply to comment #1)
> I believe this problem can be fixed by modifying XQuery 3.0 section 2.5.4 as
> follows:
> 
> 1) Define S as containing every type from every module in an XQuery program.

I don't like that, because it means that the schemas in all modules used in an
XQuery must be consistent. That breaks an important aspect of XQuery's design -
we need to be able to have modules written for different versions of a schema
that evolves over time, or modules for different XML vocabularies that use the
same names but are not in a namespace.

Implementations are already allowed to know the types in an instance document
and to use them in these judgements, but whether they do this is
implementation-defined:

> potentially, the schema used for validating the instance document; 
> whether a processor adds this schema to S is implementation-defined.

If a library creates derived types in an instance, the type information in that
instance can be used to determine whether the type is an instance of xs:int.

If we want to say an implementation is not allowed to raise the error, we
should require this, and not leave it implementation-defined.

-- 
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 Thursday, 4 November 2010 13:52:53 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 March 2012 18:15:08 GMT