wf4ever.owl

<?xml version="1.0"?>


<!DOCTYPE rdf:RDF [
    <!ENTITY terms "http://purl.org/dc/terms/" >
    <!ENTITY ro "http://purl.org/wf4ever/ro#" >
    <!ENTITY parrot "http://vocab.ctic.es/parrot#" >
    <!ENTITY owl "http://www.w3.org/2002/07/owl#" >
    <!ENTITY wfdesc "http://purl.org/wf4ever/wfdesc#" >
    <!ENTITY wfprov "http://purl.org/wf4ever/wfprov#" >
    <!ENTITY wf4ever "http://purl.org/wf4ever/wf4ever#" >
    <!ENTITY xsd "http://www.w3.org/2001/XMLSchema#" >
    <!ENTITY rdfs "http://www.w3.org/2000/01/rdf-schema#" >
    <!ENTITY rdfg "http://www.w3.org/2004/03/trix/rdfg-1/" >
    <!ENTITY dcmi-terms "http://dublincore.org/documents/dcmi-terms/" >
    <!ENTITY rdf "http://www.w3.org/1999/02/22-rdf-syntax-ns#" >
]>


<rdf:RDF xmlns="http://purl.org/wf4ever/wf4ever"
     xml:base="http://purl.org/wf4ever/wf4ever"
     xmlns:dcmi-terms="http://dublincore.org/documents/dcmi-terms/"
     xmlns:ro="http://purl.org/wf4ever/ro#"
     xmlns:parrot="http://vocab.ctic.es/parrot#"
     xmlns:wfprov="http://purl.org/wf4ever/wfprov#"
     xmlns:terms="http://purl.org/dc/terms/"
     xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
     xmlns:wfdesc="http://purl.org/wf4ever/wfdesc#"
     xmlns:owl="http://www.w3.org/2002/07/owl#"
     xmlns:xsd="http://www.w3.org/2001/XMLSchema#"
     xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
     xmlns:wf4ever="http://purl.org/wf4ever/wf4ever#"
     xmlns:rdfg="http://www.w3.org/2004/03/trix/rdfg-1/">
    <owl:Ontology rdf:about="http://purl.org/wf4ever/wf4ever">
        <rdfs:comment xml:lang="en">The wf4ever ontology.
                                  This is based on the wf4ever ontologies ro, wf and wfdesc- but adds custom classes like wf4ever:Image and wf4ever:WebServiceProcess</rdfs:comment>
        <owl:imports rdf:resource="http://purl.org/wf4ever/ro"/>
        <rdfs:seeAlso rdf:resource="http://purl.org/wf4ever/ro"/>
        <owl:imports rdf:resource="http://purl.org/wf4ever/wfdesc"/>
        <owl:imports rdf:resource="http://purl.org/wf4ever/wfprov"/>
        <parrot:hasPrologue rdf:resource="http://purl.org/wf4ever/index.html#ro"/>
        <rdfs:seeAlso rdf:resource="http://www.wf4ever-project.org/wiki/display/docs/Research+Object+Vocabulary+Specification"/>
        <owl:versionIRI rdf:resource="https://raw.github.com/wf4ever/ro/master/wf4ever.owl"/>
    </owl:Ontology>
    


    <!-- 
    ///////////////////////////////////////////////////////////////////////////////////////
    //
    // Annotation properties
    //
    ///////////////////////////////////////////////////////////////////////////////////////
     -->

    


    <!-- 
    ///////////////////////////////////////////////////////////////////////////////////////
    //
    // Datatypes
    //
    ///////////////////////////////////////////////////////////////////////////////////////
     -->

    


    <!-- 
    ///////////////////////////////////////////////////////////////////////////////////////
    //
    // Data properties
    //
    ///////////////////////////////////////////////////////////////////////////////////////
     -->

    


    <!-- http://purl.org/wf4ever/wf4ever#command -->

    <owl:DatatypeProperty rdf:about="&wf4ever;command">
        <rdfs:seeAlso xml:lang="en">The executed command, for instance &quot;cp /tmp/file1 /tmp/file2&quot;,  &quot;/usr/local/bin/analyzestuff&quot; or &quot;C:\Program.exe&quot;.

This ontology does not describe the syntax or format of the command line (for instance splitting into argv arguments or escaping), although reasonable effort should be made to reflect the executed command line on a typical command line shell.</rdfs:seeAlso>
        <rdfs:domain rdf:resource="&wf4ever;CommandLineTool"/>
        <rdfs:range rdf:resource="&xsd;string"/>
    </owl:DatatypeProperty>
    


    <!-- http://purl.org/wf4ever/wf4ever#filePath -->

    <owl:DatatypeProperty rdf:about="&wf4ever;filePath">
        <rdfs:comment xml:lang="en">The (possibly) relative filepath of a wf4ever:File artifact that was used or generated by a wfprov:WorkflowRun. 

Note that this file path is not uniquely identifying the artifact as different workflow runs might be writing to the same file path. 

To specify fixed file paths of a workflow wfdesc:Parameter, use wf4ever:parameterFilePath.</rdfs:comment>
        <rdfs:domain rdf:resource="&wf4ever;File"/>
        <rdfs:seeAlso rdf:resource="&wf4ever;parameterFilePath"/>
        <rdfs:range rdf:resource="&xsd;string"/>
    </owl:DatatypeProperty>
    


    <!-- http://purl.org/wf4ever/wf4ever#parameterFilePath -->

    <owl:DatatypeProperty rdf:about="&wf4ever;parameterFilePath">
        <rdfs:comment xml:lang="en">A (possibly relative) filepath used as a fixed input or output parameter for a workflow.

For instance, some workflows might always read the file &quot;relative/in.txt&quot; and always generate the output &quot;/tmp/output.txt&quot;.

To indicate that a particular wfprov:Artifact from a wfprov:WorkflowRun was a file, use wf4ever:File and wf4ever:filePath - this would typically be the case for workflow runs involving this parameter.</rdfs:comment>
        <rdfs:domain rdf:resource="&wf4ever;FileParameter"/>
        <rdfs:range rdf:resource="&xsd;string"/>
    </owl:DatatypeProperty>
    


    <!-- http://purl.org/wf4ever/wf4ever#script -->

    <owl:DatatypeProperty rdf:about="&wf4ever;script">
        <rdfs:domain rdf:resource="&wf4ever;Script"/>
        <rdfs:range rdf:resource="&xsd;string"/>
    </owl:DatatypeProperty>
    


    <!-- http://purl.org/wf4ever/wf4ever#serviceURI -->

    <owl:DatatypeProperty rdf:about="&wf4ever;serviceURI">
        <rdfs:domain rdf:resource="&wf4ever;WebService"/>
        <rdfs:range rdf:resource="&xsd;anyURI"/>
    </owl:DatatypeProperty>
    


    <!-- http://purl.org/wf4ever/wf4ever#wsdlOperationName -->

    <owl:DatatypeProperty rdf:about="&wf4ever;wsdlOperationName">
        <rdfs:domain rdf:resource="&wf4ever;SOAPService"/>
    </owl:DatatypeProperty>
    


    <!-- http://purl.org/wf4ever/wf4ever#wsdlPortName -->

    <owl:DatatypeProperty rdf:about="&wf4ever;wsdlPortName">
        <rdfs:domain rdf:resource="&wf4ever;SOAPService"/>
    </owl:DatatypeProperty>
    


    <!-- http://purl.org/wf4ever/wf4ever#wsdlURI -->

    <owl:DatatypeProperty rdf:about="&wf4ever;wsdlURI">
        <rdfs:domain rdf:resource="&wf4ever;SOAPService"/>
        <rdfs:subPropertyOf rdf:resource="&wf4ever;serviceURI"/>
    </owl:DatatypeProperty>
    

    <!-- http://purl.org/wf4ever/wf4ever#rootURI -->

    <owl:DatatypeProperty rdf:about="&wf4ever;rootURI">
        <rdfs:label xml:lang="en">Root URI</rdfs:label>
        <rdfs:subPropertyOf rdf:resource="&wf4ever;serviceURI"/>
        <rdfs:comment xml:lang="en">The root URI of a web service</rdfs:comment>        
    </owl:DatatypeProperty>


    <!-- 
    ///////////////////////////////////////////////////////////////////////////////////////
    //
    // Classes
    //
    ///////////////////////////////////////////////////////////////////////////////////////
     -->

    


    <!-- http://purl.org/wf4ever/wf4ever#BeanshellScript -->

    <owl:Class rdf:about="&wf4ever;BeanshellScript">
        <rdfs:subClassOf rdf:resource="&wf4ever;Script"/>
    </owl:Class>
    


    <!-- http://purl.org/wf4ever/wf4ever#CommandLineTool -->

    <owl:Class rdf:about="&wf4ever;CommandLineTool">
        <rdfs:subClassOf rdf:resource="&wfdesc;ProcessImplementation"/>
        <rdfs:seeAlso xml:lang="en">A command line tool, typically executed locally, through SSH or a job submission system.</rdfs:seeAlso>
    </owl:Class>
    


    <!-- http://purl.org/wf4ever/wf4ever#Dataset -->

    <owl:Class rdf:about="&wf4ever;Dataset">
        <rdfs:subClassOf rdf:resource="&wfprov;Artifact"/>
        <rdfs:comment xml:lang="en">A dataset or reference database.</rdfs:comment>
    </owl:Class>
    


    <!-- http://purl.org/wf4ever/wf4ever#Document -->

    <owl:Class rdf:about="&wf4ever;Document">
        <rdfs:subClassOf rdf:resource="&wfprov;Artifact"/>
        <rdfs:comment xml:lang="en">A human readable document, like a HTML page, a PDF, plain text file or a LibreOffice document.</rdfs:comment>
    </owl:Class>
    


    <!-- http://purl.org/wf4ever/wf4ever#File -->

    <owl:Class rdf:about="&wf4ever;File">
        <rdfs:subClassOf rdf:resource="&wfprov;Artifact"/>
        <rdfs:comment xml:lang="en">A file wfprov:Artifact that was used or generated by a wfprov:WorkflowRun. 

A wf4ever:File can specify a (possibly relative) wf4ever:filePath.

Note that this file path is not uniquely identifying the artifact as different workflow runs might be writing to the same file path. Hence a wf4ever:File  should generally not be identified using a &lt;file:///absolute/path&gt; URI, unless the RDF serialization is using a relative URI reference to a resource  &lt;some/path&gt; which is also aggregated as a child resource within a RO, so resolving &lt;some/path&gt; within &lt;file:///some/ro/&gt; would generate &lt;file:///some/ro/some/path&gt; identifying the wf4ever:File locally. 

In some cases, file URIs with hostname can be used to uniquely identify a file, say &lt;file://server.example.com/home/user/file.txt&gt; - such a identification scheme should only be used if the server hostname is considered fixed and the paths are considered immutable. 

To specify fixed file paths of a workflow wfdesc:Parameter, use wf4ever:parameterFilePath.</rdfs:comment>
        <rdfs:seeAlso rdf:resource="&wf4ever;filePath"/>
    </owl:Class>
    


    <!-- http://purl.org/wf4ever/wf4ever#FileParameter -->

    <owl:Class rdf:about="&wf4ever;FileParameter">
        <rdfs:subClassOf rdf:resource="&wfdesc;Parameter"/>
        <rdfs:subClassOf>
            <owl:Restriction>
                <owl:onProperty rdf:resource="&wf4ever;parameterFilePath"/>
                <owl:someValuesFrom rdf:resource="&xsd;string"/>
            </owl:Restriction>
        </rdfs:subClassOf>
        <rdfs:comment xml:lang="en">A wfdesc:Parameter (typically an Input or Output) which is read/written from a fixed (possibly relative) file path, specified with wf4ever:parameterFilePath

For instance, some workflows might always read the file &quot;relative/in.txt&quot; and always generate the output &quot;/tmp/output.txt&quot;.

Note that this path is not in anyway identifying the wfdesc:Parameter, as workflows could be reading/writing the same file paths.

To indicate that a particular value from a wfprov:WorkflowRun was a file, use wf4ever:File and wf4ever:filePath.</rdfs:comment>
    </owl:Class>
    


    <!-- http://purl.org/wf4ever/wf4ever#Image -->

    <owl:Class rdf:about="&wf4ever;Image">
        <rdfs:subClassOf rdf:resource="&wfprov;Artifact"/>
        <rdfs:comment xml:lang="en">A visual image or photograph, formats like JPEG, PNG, TIFF</rdfs:comment>
    </owl:Class>
    


    <!-- http://purl.org/wf4ever/wf4ever#RESTService -->

    <owl:Class rdf:about="&wf4ever;RESTService">
        <rdfs:subClassOf rdf:resource="&wf4ever;WebService"/>
        <rdfs:comment xml:lang="en">A RESTful web service, accessed using HTTP or HTTPS.

The wf4ever:serviceURI should somewhat identify the endpoint, but would often not be uniquely identifying the RESTService as the exact URI accessed could depend on the input values.

TODO: Should a URI template be specified?</rdfs:comment>
    </owl:Class>
    


    <!-- http://purl.org/wf4ever/wf4ever#RScript -->

    <owl:Class rdf:about="&wf4ever;RScript">
        <rdfs:subClassOf rdf:resource="&wf4ever;Script"/>
    </owl:Class>
    


    <!-- http://purl.org/wf4ever/wf4ever#SOAPService -->

    <owl:Class rdf:about="&wf4ever;SOAPService">
        <rdfs:subClassOf rdf:resource="&wf4ever;WebService"/>
        <rdfs:comment xml:lang="en">A SOAP service is a method described in a WSDL 1.1 or WSDL 2.0 specification.

A SOAP service method is considered unique given a wf4ever:wsdlURI, wf4ever:wsdlOperationName and wf4ever:wsdlPortName. 

TODO: Do we need to distinguish between WSDL and SOAP? WSDL 1.1 and WSDL 2.0? RPC/Encoded vs.Wrapped Document/Literal?</rdfs:comment>
        <owl:hasKey rdf:parseType="Collection">
            <rdf:Description rdf:about="&wf4ever;wsdlURI"/>
        </owl:hasKey>
        <owl:hasKey rdf:parseType="Collection">
            <rdf:Description rdf:about="&wf4ever;wsdlPortName"/>
        </owl:hasKey>
        <owl:hasKey rdf:parseType="Collection">
            <rdf:Description rdf:about="&wf4ever;wsdlOperationName"/>
        </owl:hasKey>
    </owl:Class>
    


    <!-- http://purl.org/wf4ever/wf4ever#Script -->

    <owl:Class rdf:about="&wf4ever;Script">
        <rdfs:subClassOf rdf:resource="&wfdesc;ProcessImplementation"/>
        <rdfs:seeAlso xml:lang="en">A script which can be evaluated. Scripts of reasonable small sizes can be embedded in this description using wf4ever:script.</rdfs:seeAlso>
    </owl:Class>
    


    <!-- http://purl.org/wf4ever/wf4ever#WebService -->

    <owl:Class rdf:about="&wf4ever;WebService">
        <rdfs:subClassOf rdf:resource="&wfdesc;ProcessImplementation"/>
        <rdfs:comment>A (typically remote) web service, like REST or SOAP. For the purpose of being a wfdesc:ProcessImplementation of a wfdesc:Process, a &apos;service&apos; is considered more like a specific method then an endpoint.</rdfs:comment>
    </owl:Class>
    


    <!-- http://purl.org/wf4ever/wf4ever#WorkflowResearchObject -->

    <owl:Class rdf:about="&wf4ever;WorkflowResearchObject">
        <owl:equivalentClass>
            <owl:Class>
                <owl:intersectionOf rdf:parseType="Collection">
                    <rdf:Description rdf:about="&ro;ResearchObject"/>
                    <owl:Restriction>
                        <owl:onProperty rdf:resource="http://www.openarchives.org/ore/terms/aggregates"/>
                        <owl:someValuesFrom rdf:resource="&wfdesc;Workflow"/>
                    </owl:Restriction>
                </owl:intersectionOf>
            </owl:Class>
        </owl:equivalentClass>
        <rdfs:comment xml:lang="en">A workflow research object is a research object that aggregates at least one workflow description. It might of course aggregates any other kind of resources, but MUST aggregate at least one wfdesc:Workflow.

Such research objects have characteristics that are of particular interest for the Wf4Ever infrastructure, because workflows can be run, are composed of processes, and are subject to decay and repair.</rdfs:comment>
    </owl:Class>
    


</rdf:RDF>



<!-- Generated by the OWL API (version 3.3.1957) http://owlapi.sourceforge.net -->