Sorry, I wasn't notified of your reply in time somehow.
1. No separation at all:
Look at one of sandboxes:
Code:
http://www.iringsandbox.org/repositories/SandboxPt8/query
Query:
Code:
PREFIX rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>
SELECT *
WHERE
{?uri rdf:type <http://dm.rdlfacade.org/data#ClassOfEvent>}
LIMIT 1000
Query:
Code:
SELECT *
WHERE
{<http://tpl.rdlfacade.org/data#R98830569416> ?p ?o}
ORDER BY ?label
LIMIT 1000
Everything goes together - part 2 type instances, template roles. Some reasoning on client's side required.
2. Separate graphs:
Look at
http://jord-dev.org/endpoint/ , the last of Query List, looking for R-number
Code:
PREFIX RDL: <http://jord-dev.org/rdl/>
PREFIX afn: <http://jena.hpl.hp.com/ARQ/function#>
SELECT * {
GRAPH <http://irm.dnv.com/ontologies/iring.map> {
?R RDL:rdsWipEquivalent ?RDS .
FILTER (afn:localname(?R)= "R6565765")
}
}
Only part of triple server is searched, graph
http://irm.dnv.com/ontologies/iring.map with bridge from R to RDS numbers.
3. Complete separation. That's what we know well:
http://posccaesar.org/endpoint/sparql - only proper Part 2 instances.
Code:
http://www.iringsandbox.org/repositories/tempInitSet/query
- only templates