- From: <bugzilla@wiggum.w3.org>
- Date: Tue, 29 Jul 2008 22:40:46 +0000
- To: public-qt-comments@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=5738
Michael Dyck <jmdyck@ibiblio.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jmdyck@ibiblio.org
--- Comment #5 from Michael Dyck <jmdyck@ibiblio.org> 2008-07-29 22:40:45 ---
(In reply to comment #3)
>... C.1 Static Context Components.
>
> That table clearly says the ISSD is augmentable by a query processor, and
> may include types not in the built-in types and not explicitly imported
> by the user.
For the three components of the ISSD, the table says "augmentable" in the
column labelled "Can be overwritten or augmented by implementation?", but
this must be interpreted in light of the definition for that column in the
preceding bulleted list, which I believe says that the "augmentability"
only refers to the initial value (setting) of each component.
So, while it's quite true that the 'in-scope schema types' component can
contain types other than the xs types and explicitly imported types,
(a) the implementator is obliged to specify what those extra types are, and
(b) they're in the in-scope schema types from the start (rather than being
added as the result of a schema import).
In particular, if a processor were to implement a transitive schema import,
I don't think it could claim conformance by virtue of C.1.
--
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 Tuesday, 29 July 2008 22:41:19 UTC