forked from stain/scufl2-wfdesc
-
Notifications
You must be signed in to change notification settings - Fork 1
Common queries
Stian Soiland-Reyes edited this page Jun 16, 2014
·
2 revisions
These queries can be executed using SPARQL on the returned wfdesc Turtle, and assume these PREFIXes:
PREFIX prov: <http://www.w3.org/ns/prov#>
PREFIX wfdesc: <http://purl.org/wf4ever/wfdesc#>
PREFIX wfprov: <http://purl.org/wf4ever/wfprov#>
PREFIX tavernaprov: <http://ns.taverna.org.uk/2012/tavernaprov/>
PREFIX cnt: <http://www.w3.org/2011/content#>
PREFIX rdfs: <http://www.w3.org/2000/01/rdf-schema#>
PREFIX wf4ever: <http://purl.org/wf4ever/wf4ever#>
PREFIX comp: <http://purl.org/DP/components#>
The wfdesc model does not have a concept of "top-level" workflow, however you can
use a SPARQL NOT EXISTS
filter to skip any nested workflows:
SELECT ?wf WHERE {
?wf a wfdesc:Workflow .
FILTER NOT EXISTS {
?processInParent prov:specializationOf ?wf .
?parent wfdesc:hasSubProcess ?processInParent
} .
}
Thus any workflow ?wf
which (specialization) has been used as a sub-process in ?parent
are excluded from the result. As SCUFL2 workflows have unique URIs within each workflow bundle, e.g. http://ns.taverna.org.uk/2010/workflowBundle/01348671-5aaa-4cc2-84cc-477329b70b0d/workflow/Hello_Anyone/ - the above would not be excluding a workflow just because its structure has been reused elsewhere.
A variant of the above is if you are only interested in processors in top-level workflows:
SELECT ?proc WHERE {
?wf a wfdesc:Workflow ;
wfdesc:hasSubProcess ?proc .
FILTER NOT EXISTS {
?processInParent prov:specializationOf ?wf .
?parent wfdesc:hasSubProcess ?processInParent
} .
}