Kjetil,

I have a different behavior:

-- Line 2: ttlp (file_to_string_output
('Kjetilc/information-model.ttl'),
'http://rabbit.computas.int:8180/sublima-webapp-1.0-SNAPSHOT/',
'smiltest', 0)

Done. -- 52 msec.

-- Line 3: ttlp (file_to_string_output ('Kjetilc/smil-test-data.ttl'),
'http://rabbit.computas.int:8180/sublima-webapp-1.0-SNAPSHOT/',
'smiltest', 0)

Done. -- 48767 msec.

-- Line 4: ttlp (file_to_string_output ('Kjetilc/sublima-ns.ttl'),
'http://rabbit.computas.int:8180/sublima-webapp-1.0-SNAPSHOT/',
'smiltest', 0)

Done. -- 34 msec.

-- Line 5: DB.DBA.RDF_LOAD_RDFXML (file_to_string
('Kjetilc/lingvoj-excerpt.rdf'),
'http://rabbit.computas.int:8180/sublima-webapp-1.0-SNAPSHOT/',
'smiltest')

Done. -- 149 msec.

-- Line 7:
sparql
PREFIX dct: <http://purl.org/dc/terms/>
PREFIX rdfs: <http://www.w3.org/2000/01/rdf-schema#>
PREFIX skos: <http://www.w3.org/2004/02/skos/core#>
DESCRIBE ?resource ?rest WHERE {
?resource dct:identifier
<http://rabbit.computas.int:8180/sublima-webapp-1.0-SNAPSHOT/resource/vi_tidiga__foedd_foer_tidigt_004314>
 . ?resource ?p ?rest . }

callret-0
LONG VARCHAR
_______________________________________________________________________________

# Empty TURTLE


1 Rows. -- 46 msec.


SQL> sparql select * where { graph ?g
{ 
<http://rabbit.computas.int:8180/sublima-webapp-1.0-SNAPSHOT/resource/vi_tidiga__foedd_foer_tidigt_004314>
 ?p ?o }};
g
p
o
VARCHAR
VARCHAR
VARCHAR
_______________________________________________________________________________


0 Rows. -- 36 msec.
SQL> sparql select * where { graph ?g { ?s ?p
<http://rabbit.computas.int:8180/sublima-webapp-1.0-SNAPSHOT/resource/vi_tidiga__foedd_foer_tidigt_004314>
 }};
g
s
p
VARCHAR
VARCHAR
VARCHAR
_______________________________________________________________________________


0 Rows. -- 6 msec.


If this sequence is wrong, can I get a log of ISQL actions performed on
a blank database in order to reproduce the case, please? I guess I've
missed some test data or some operations.

Best Regards,

Ivan Mikhailov
OpenLink Software
http://virtuoso.openlinksw.com

On Wed, 2008-12-17 at 13:53 +0100, Kjetil Kjernsmo wrote:
> All,
> 
> I've been analysing the problem I have with the RDF/XML serialisation. 
> 
> Now it seems like the problem of lost rdf:types was indeed fixed in .10-pre5 
> (not that I really grokked was the problem was). 
> 
> It seems that what remains is a problem with what DESCRIBE returns. I realise 
> that it is not standardised and that it is configureable, but it may seem 
> that the default is not very reasonable.
> 
> This is my test query again:
> > A test query looks like this:
> >
> > PREFIX dct: <http://purl.org/dc/terms/>
> > PREFIX rdfs: <http://www.w3.org/2000/01/rdf-schema#>
> > PREFIX skos: <http://www.w3.org/2004/02/skos/core#>
> > DESCRIBE ?resource ?rest WHERE {
> >
> > ?resource dct:identifier
> > <http://rabbit.computas.int:8180/sublima-webapp-1.0-SNAPSHOT/resource/vi_ti
> >diga__foedd_foer_tidigt_004314> . ?resource ?p ?rest .
> > }
> 
> It returns all properties and objects of the resource that has this 
> dct:identifier:
> 
>  <j.3:Resource rdf:about="http://www.kanalen.org/vitidiga/";>
>     <j.3:url rdf:resource="http://www.kanalen.org/vitidiga/"/>
>     <j.1:dateAccepted rdf:datatype="http://www.w3.org/2001/XMLSchema#dateTime";
>     >2004-09-13T14:32:37.000+01:00</j.1:dateAccepted>
>     <j.1:title xml:lang="no">Vi tidiga - född för tidigt </j.1:title>
>     <n0pred:describedBy 
> rdf:resource="http://sublima.computas.com/status/godkjent_av_administrator"/>
>     <j.3:committer 
> rdf:resource="http://rabbit.computas.int:8180/sublima-webapp-1.0-SNAPSHOT/user/det_usr00022"/>
>     <j.1:language rdf:resource="http://www.lingvoj.org/lang/sv"/>
>     <j.1:identifier 
> rdf:resource="http://rabbit.computas.int:8180/sublima-webapp-1.0-SNAPSHOT/resource/vi_tidiga__foedd_foer_tidigt_004314"/>
>     <j.1:subject 
> rdf:resource="http://rabbit.computas.int:8180/sublima-webapp-1.0-SNAPSHOT/topic/topic000325"/>
>     <j.1:description xml:lang="no">Vi tidiga är en mötesplats för föräldrar 
> till för tidigt födda barn. Syftet med sidorna är att hjälpa nordiska 
> föräldrar till för tidigt födda barn att hitta information - och ge en 
> möjlighet att stötta varandra.    </j.1:description>
>     <j.1:publisher 
> rdf:resource="http://rabbit.computas.int:8180/sublima-webapp-1.0-SNAPSHOT/agent/Frldrakanalen"/>
>   </j.3:Resource>
> 
> This is as expected, the ?resource ?p ?rest triple is there to make it return 
> the same for the nodes that it links to also. It does this too, e.g.
> 
> <skos:Concept 
> rdf:about="http://rabbit.computas.int:8180/sublima-webapp-1.0-SNAPSHOT/topic/topic000325";>
> 
> This was what went wrong previously.
> 
> But then something weird happens: It also returns a lot of other matches 
> to ?resource, e.g.:
> 
> <rdf:Description 
> rdf:about="http://www.sjukvardsradgivningen.se/artikel.asp?CategoryID=22952";>
>     <j.1:language rdf:resource="http://www.lingvoj.org/lang/sv"/>
>     <n0pred:describedBy 
> rdf:resource="http://sublima.computas.com/status/godkjent_av_administrator"/>
>   </rdf:Description>
>   <rdf:Description 
> rdf:about="http://netdoktor.passagen.se/default.ns?lngItemID=4194";>
>     <j.1:language rdf:resource="http://www.lingvoj.org/lang/sv"/>
>     <n0pred:describedBy 
> rdf:resource="http://sublima.computas.com/status/godkjent_av_administrator"/>
>   </rdf:Description>
> 
> The following query tests what the identifier is:
> 
> SELECT ?identifier WHERE  { 
> <http://www.sjukvardsradgivningen.se/artikel.asp?CategoryID=22952> 
> <http://purl.org/dc/terms/identifier> ?identifier . }
> 
> returns 
> http://rabbit.computas.int:8180/sublima-webapp-1.0-SNAPSHOT/resource/trygghetslarm_005975
> 
> So, from my perspective, it seems rather wrong that the resource 
> http://www.sjukvardsradgivningen.se/artikel.asp?CategoryID=22952
> is returned when it does not have a dct:identifier property with the object
> http://rabbit.computas.int:8180/sublima-webapp-1.0-SNAPSHOT/resource/vi_tidiga__foedd_foer_tidigt_004314
> 
> Any comments on that?
> 
> Kind regards 
> 
> Kjetil Kjernsmo
> -- 



Reply via email to