Hi Everyone,
I am on of the developers at the Swiss Institute of Bioinformatics for
uniprot.org. We have for a while now a sparql endpoint in beta.
beta.sparql.uniprot.org. I am trying to generate a Service Description
for that endpoint that is as useful as possible and I have some
questions.
The first questions is about the uri of a named graph in an endpoint.
Taking the following extracted example. I have a named graph in the
endpoint.
Is it correct to use the same uri for both the concept of the named
graph and the name of the named graph?
@prefix : <http://www.w3.org/ns/sparql-service-description#>
@prefix void: <http://rdfs.org/ns/void#> .
<http://purl.uniprot.org/tissues/>
:graph <#_3> .
:name <http://purl.uniprot.org/tissues/> .
<#_3>
void:classes "1" ;
void:datadump
<ftp://ftp.uniprot.org/pub/databases/uniprot/current_release/tissues.rdf.gz>
;
void:distinctObjects "3560" ;
void:distinctSubjects "1872" ;
void:triples "6108"^^<http://www.w3.org/2001/XMLSchema#long> ;
a :Graph ;
:name <http://purl.uniprot.org/tissues/> .
Or should the first part be
<#_2>
:graph <#_3> .
:name <http://purl.uniprot.org/tissues/> .
I also have a question about declaring the entailment regime. If no
reasoning was applied, should an entailment regime be declared? if yes
which one?
If only owl:sameAs reasoning as done by OWLIM is used which entailment
regime URI should I use?
The last question is: in the attached example files, which properties
are you missing i.e. you think would generally be useful?
Regards,
Jerven
--
Jerven Bolleman
me@jerven.eu