FW: cwm bug? xsd namespace

Hi Yosi,

I don't know if this is a bug or not, but it sure seems odd, and it puzzled Sean
Palmer too.  Depending on how the xsd namespace is declared, the rule below fires or doesn't fire.

--------------------------------------------

#  File: junk2.n3
#  Test with:
#       cwm junk2.n3 --think --strings
# Gives the following with the right xsd namespace:
#       FIRED base: http://example#aaa ex:p2 bbb
# Gives no output if the example namespace is used.
#
#  Hmm, cwm seems to have special knowledge of the xsd namespace.
# If I declare it like this then the rule below fires,
# but if I declare it with an http://example namespace, it doesn't.
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
# @prefix xsd: <http://example/xsd#> .

@prefix ex: <http://example/httpspec#> .
@prefix log: <http://www.w3.org/2000/10/swap/log#>.
@prefix string: <http://www.w3.org/2000/10/swap/string#> .

"http://example#aaa"^^xsd:anyURI ex:p1 <http://example#bbb> .

{       ?u ex:p1 ?reply .
        ("FIRED base: " ?u " ex:p2 "
                ?reply "\n") string:concatenation ?fired .
} =>    {
        ?u ex:p2 ?reply .
        # Debugging:
        "a" log:outputString ?fired .
        } .

--------------------------------------------------


David Booth, Ph.D.
HP Software
+1 617 629 8881 office  |  dbooth@hp.com
http://www.hp.com/go/software

Opinions expressed herein are those of the author and do not represent the official views of HP unless explicitly stated otherwise.