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

[Bug 8129] [XQTS] CVS: location hints

From: <bugzilla@jessica.w3.org>
Date: Fri, 11 Jun 2010 19:03:54 +0000
To: public-qt-comments@w3.org
Message-Id: <E1ON9WE-0006WD-Gc@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8129


Oliver Hallam <oliver@cbcl.co.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|FIXED                       |




--- Comment #11 from Oliver Hallam <oliver@cbcl.co.uk>  2010-06-11 19:03:53 ---
These issues have been fixed, but there are still some problems with the
modules tests.

Firstly, module3-lib and module4-lib still use a location hint to load the
schema.


modules-21 is as follows:

import module namespace defs = "http://www.w3.org/TestModules/defs";

defs:function2(1 cast as simple:myType)


It expects (non-existant) error XQST0081.  I assume it should have been be
XPST0081 (unbound prefix).

However the imported module uses the schema with target namespace
"http://www.w3.org/TestModules/defs" and so I believe that XQST0036 is also
appropriate.

This also applies to modules-23 and modules-24




The tests modules-25, modules-26 and modules-27 all import module4-lib.xq whose
content is as follows:




declare variable $defs:var as schema-attribute(sample:attrib) := attribute
sample:attrib{ 1 }; 


declare function defs:function1() as schema-attribute(sample:attrib)
{
  attribute sample:attrib{ 1 }
};


declare function defs:function2($param as schema-attribute(sample:attrib)) as
xs:integer
{
  $param cast as xs:integer + 1 
};



In several places in this module a newly constructed attribute (with type
annotation xs:untypedAtomic) is used where a schema-attribute(sample:attrib) is
expected.  Thus I believe any test importing this module should also expect
XPTY0004, which seems to undermine the test.

The module could be fixed by validating the constructed attributes, although
this doesn't seem to be possible in XQuery (why can we only validate
elements?).  The only way to fix this test is either to use the type
schema-attribute(sample:attrib)? and the value (), or to expand the schema such
that we can validate an element containing a sample:attrib attribute and then
extract the attribute.

-- 
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 Friday, 11 June 2010 19:03:56 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:57:31 UTC