Hello Barry,

Sorry for bothering you. Our server environment was something wrong.
These queries work well on the Sesame workbench after rebooting the
server cleanly. I am trying to figure out what has happened in our side.

Thanks for your help,
Fumi

2011/12/8 Fumihiro Kato <[email protected]>:
> Hi Barry,
>
> I did these tests on the Sesame workbench manually.
>
> Best,
> Fumi
>
> On Wed, Dec 7, 2011 at 8:22 PM, Barry Bishop <[email protected]> 
> wrote:
>> Hello Fumi,
>>
>> I tried repeating this with Tomcat7, but had the same result, i.e. things
>> seem to work fine.
>>
>> I have created a test case using exactly these steps (all Java code) and
>> have tried using the Sesame workbench + Sesame server to execute each step
>> manually.
>>
>> What is your test set up? How does it differ from what I have been doing?
>>
>> Best,
>> barry
>>
>>
>> On 07/12/11 10:32, Fumihiro Kato wrote:
>>>
>>> Hello Barry,
>>>
>>> Thank you for supporting this topic.
>>>
>>> I also use OWLIM-SE 4.3.4238. Our tomcat version is 7.0.16.
>>> The first SELECT example (?s rdfs:label "Tokyo" .)  is no problem for us.
>>> But (ex:東京 rdfs:label ?o .) and (ex:東京 ?p ?o .) return no results.
>>>
>>> Best Regards,
>>> Fumi
>>>
>>> On Tue, Dec 6, 2011 at 9:15 PM, Barry Bishop<[email protected]>
>>>  wrote:
>>>>
>>>> Hello Fumi,
>>>>
>>>> I just tried with the latest release (OWLIM-SE 4.3.4238) and I can't
>>>> reproduce this problem using these steps:
>>>>
>>>>
>>>> PREFIX rdfs:<http://www.w3.org/2000/01/rdf-schema#>
>>>> PREFIX ex:<http://example.org#>
>>>> INSERT DATA {
>>>>    ex:東京 rdfs:label "Tokyo" .
>>>> }
>>>>
>>>>
>>>> PREFIX rdfs:<http://www.w3.org/2000/01/rdf-schema#>
>>>> PREFIX ex:<http://example.org#>
>>>> SELECT * {
>>>>    ?s rdfs:label "Tokyo" .
>>>> }
>>>> =>  Returns ?s=ex:東京
>>>>
>>>>
>>>> PREFIX rdfs:<http://www.w3.org/2000/01/rdf-schema#>
>>>> PREFIX ex:<http://example.org#>
>>>> SELECT * {
>>>>    ex:東京 rdfs:label ?o .
>>>> }
>>>> =>  returns ?o="Tokyo"
>>>>
>>>> PREFIX rdfs:<http://www.w3.org/2000/01/rdf-schema#>
>>>> PREFIX ex:<http://example.org#>
>>>> SELECT * {
>>>>    ex:東京 ?p ?o .
>>>> }
>>>> =>  Returns both bindings as expected
>>>>
>>>>
>>>> Which version of OWLIM are you using?
>>>>
>>>>
>>>> Best,
>>>> barry
>>>>
>>>> --
>>>> Barry Bishop
>>>> OWLIM Product Manager
>>>> Ontotext AD
>>>> Tel: +43 650 2000 237
>>>> email: [email protected]
>>>> www.ontotext.com
>>>>
>>>>
>>>>
>>>> On 05/12/11 10:45, Nikolay Krustev wrote:
>>>>>
>>>>> Hello Fumi,
>>>>>
>>>>> Thank you for your question.
>>>>> One of our Core Team devs will look into this issue and send feedback.
>>>>>
>>>>> Regards,
>>>>>
>>>>> Nikolay
>>>>>
>>>>> -----Original Message-----
>>>>> From: [email protected]
>>>>> [mailto:[email protected]] On Behalf Of Fumihiro
>>>>> Kato
>>>>> Sent: Monday, December 05, 2011 9:02 AM
>>>>> To: [email protected]
>>>>> Subject: [Owlim-discussion] An IRI issue in SPARQL
>>>>>
>>>>> Hello all,
>>>>>
>>>>> I have been trying to use IRIs with OWLIM-SE, it seems that a
>>>>> SPARQL query does not match any IRIs including unicode characters.
>>>>> For instance, I have uploaded the following simple turtle into an OWLIM
>>>>> repository.
>>>>>
>>>>>
>>>>>
>>>>> ----------------------------------------------------------------------------------
>>>>>     @prefix rdfs:<http://www.w3.org/2000/01/rdf-schema#>    .
>>>>>
>>>>>     <http://example.org/東京>    rdfs:label "Tokyo" .
>>>>>
>>>>>
>>>>> ----------------------------------------------------------------------------------
>>>>>
>>>>> Then the repository does not return any result when I send the
>>>>> following SPARQL query to it.
>>>>>
>>>>>
>>>>>
>>>>> ----------------------------------------------------------------------------------
>>>>>     SELECT *
>>>>>     WHERE {
>>>>>        <http://example.org/東京>    ?p ?o .
>>>>>     }
>>>>>
>>>>>
>>>>> ----------------------------------------------------------------------------------
>>>>>
>>>>> I thought that this was one of Sesame's issues at first. However,
>>>>> I confirmed a sesame memory repository accepted the query
>>>>> and returned a proper result. Therefore I guess this problem is
>>>>> in OWLIM.
>>>>>
>>>>> Any clues?
>>>>> Fumi
>>>>> _______________________________________________
>>>>> OWLIM-discussion mailing list
>>>>> [email protected]
>>>>> http://ontotext.com/mailman/listinfo/owlim-discussion
>>>>>
>>>>> _______________________________________________
>>>>> OWLIM-discussion mailing list
>>>>> [email protected]
>>>>> http://ontotext.com/mailman/listinfo/owlim-discussion
_______________________________________________
OWLIM-discussion mailing list
[email protected]
http://ontotext.com/mailman/listinfo/owlim-discussion

Reply via email to