has related match
skos:relatedMatch is used to state an associative mapping link between two conceptual resources in different concept schemes.
[{ sym>ML>data / data>ML>data } -> ML -> sym]
Broader concepts are typically rendered as parents in a concept hierarchy (tree).
has broader
Relates a concept to a concept that is more general in meaning.
By convention, skos:broader is only used to assert an immediate (i.e. direct) hierarchical link between two conceptual resources.
notation
A notation, also known as classification code, is a string of characters such as "T58.5" or "303.4833" used to uniquely identify a concept within the scope of a given concept scheme.
By convention, skos:notation is used with a typed literal in the object position of the triple.
Other Patterns that do not fit in any other category
Concept Scheme
A set of concepts, optionally including statements about semantic relationships between those concepts.
Thesauri, classification schemes, subject heading lists, taxonomies, 'folksonomies', and other types of controlled vocabulary are all examples of concept schemes. Concept schemes are also embedded in glossaries and terminologies.
A concept scheme may be defined to include concepts from different sources.
has member
Relates a collection to one of its members.
[{sym->ML->data/data} -> ML -> data -> ML -> sym]
[{{data(1)/sym -> ML -> sym}/{data(1) -> ML -> data} -> ML -> data} / {data -> ML -> data} -> ML -> data]
A Data variable is a workflow template artifact that represents a variable in the workflow specification. Example: @prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> . @prefix opmw: <http://www.opmw.org/ontology/> . <http://www.opmw.org/export/resource/DataVariable/AQUAFLOW_NTM_SUM_CORRDO> a opmw:WorkflowTemplateArtifact , opmw:DataVariable ; rdfs:label "Data variable Sum_CorrDO" ; opmw:hasDimensionality "0"^^xsd:int ; opmw:isGeneratedBy <http://www.opmw.org/export/resource/WorkflowTemplateProcess/AQUAFLOW_NTM_CREATEPLOTS> ; opmw:template <http://www.opmw.org/export/resource/WorkflowTemplate/AQUAFLOW_NTM> .
Data Variable
Presence of documentation on used data sets: yes, no
A SWeML system can have one or more models
SWeMLs can have one or more system components
Property that binds a workflow template process to the workflow template artifact that generates it. Example: @prefix opmw: <http://www.opmw.org/ontology/> . <http://www.opmw.org/export/resource/WorkflowTemplateProcess/AQUAFLOW_EDM_REAERATIONEDM> a opmw:WorkflowTemplateProcess; opmw:uses <http://www.opmw.org/export/resource/DataVariable/PARAMETERSFILE>.
uses
editorial note
A note for an editor, translator or maintainer of the vocabulary.
Entity Classification [Node Classification]
A workflow execution account represents the execution from the perspective of the system. Example: @prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> . @prefix opmw: <http://www.opmw.org/ontology/> . @prefix opmo: <http://openprovenance.org/model/opmo#> . <http://www.opmw.org/export/resource/WorkflowExecutionAccount/ACCOUNT1335533097598> a opmo:Account , opmw:WorkflowExecutionAccount> ; rdfs:label "Execution account created on 1335533097598" ; opmw:executedInWorkflowSystem <http://www.opmw.org/export/resource/Agent/SHELL> ; opmw:hasEndTime "2012-04-25T07:17:48-07:00"^^xsd:dateTime ; opmw:hasExecutionDiagram "http://wind.isi.edu/marbles/assets/components/workflow_portal/users/1/Water/runs/run_144.png"^^xsd:anyURI ; opmw:hasStartTime "2012-04-25T07:17:05-07:00"^^xsd:dateTime ; opmw:hasStatus "SUCCESS" ;
Workflow Execution Account
hasInputVar
p-plan:hasInputVar binds a p-plan:Step to the p-plan:Variable that takes as input for the planned execution
[{sym / data} -> ML -> data -> ML -> data]
has top concept
Relates, by convention, a concept scheme to a concept which is topmost in the broader/narrower concept hierarchies for that scheme, providing an entry point to these hierarchies.
A SWeML system linking to at least one statistical model
[{{sym/data -> ML -> data}/sym -> ML -> sym}/sym -> KR -> data]
has narrower transitive
skos:narrowerTransitive is a transitive superproperty of skos:narrower.
By convention, skos:narrowerTransitive is not used to make assertions. Rather, the properties can be used to draw inferences about the transitive closure of the hierarchical relation, which is useful e.g. when implementing a simple query expansion algorithm in a search application.
[{ sym>ML>data / data>ML>sym } -> ML -> sym]
Property that asserts which Step preceeds the current one.
isPrecededBy
hasOutputVar
p-plan:hasOutputVar binds a p-plan:Step to the p-plan:Variable that will be produced as output in the planned execution
Bundle
A p-plan:Bundle is a specific type of prov:Bundle that contains the provenance assertions of the execution of a p-plan:Plan
[sym / data -> ML -> sym / data -> KR -> data]
Facts and statistics collected together and used as a basis for reasoning, discussion or calculation.
has narrower match
skos:narrowMatch is used to state a hierarchical mapping link between two conceptual resources in different concept schemes.
note
A general note, for any purpose.
This property may be used directly, or as a super-property for more specific note types.
Paper in which the SWeML system is described
Country to which authors describing the SWeML systems in their paper are affiliated to
isOutputVarOf
p-plan:isOutputVarOf is intended to link an output variable of a step to the step.
Ordered Collection
An ordered collection of concepts, where both the grouping and the ordering are meaningful.
Ordered collections can be used where you would like a set of concepts to be displayed in a specific order, and optionally under a 'node label'.
Property that binds a workflow template artifact to the workflow template process that generates it. Example: @prefix opmw: <http://www.opmw.org/ontology/> . <http://www.opmw.org/export/resource/DataVariable/AQUAFLOW_EDM_REAERATIONPARAMS> a opmw:DataVariable, opmw:WorkflowTemplateArtifact; opmw:isGeneratedBy <http://www.opmw.org/export/resource/WorkflowTemplateProcess/AQUAFLOW_EDM_REAERATIONEDM>.
is Generated By
Linking the semantic web resource with the resource type
isSubPlanOfPlan
A p-plan:Plan may be a subplan of another bigger p-plan:Plan. p-plan:isSubPlanOfPlan is used to state the link among the two different plans. Note that if p1 is a p-plan:subPlan of p2, p1will not necessarily be a step of p2. A multistep will represent p1 in p2, and link to p1 with the p-plan.hasStepDecomposition relationship.
[Classification of Diseases (ICD9, ICD10)]
Property used to link an execution artifact to its file name (independently of its URI). Example: @prefix opmw: <http://www.opmw.org/ontology/> . @prefix opmv: <http://purl.org/net/opmv/ns#> . <http://www.opmw.org/export/resource/WorkflowExecutionArtifact/DCF49186981194248009E24BAD6A6412> a opmv:Artifact, opmw:WorkflowExecutionArtifact. opmw:hasFileName "NTMParams_SMN_2010_03_14Z"^^xsd:string.
has File Name
TransX [TransE, TransD, TransH, TransR, ...]
Bayes [Bayes models, Bayesian network, Naive Bayes Classifier]
Genetic Algorithms [Evolutionary Algorithms]
Property used to link a workflow template to its graphical representation. Example: @prefix opmw: <http://www.opmw.org/ontology/> . <http://www.opmw.org/export/resource/WorkflowTemplate/AQUAFLOW_NTM> a opmw:WorkflowTemplate; opmw:hasTemplateDiagram "http://wind.isi.edu/marbles/assets/components/workflow_portal/users/1/Water/runs/run_148.png"xsd:anyURI.
has Template Diagram
has close match
skos:closeMatch is used to link two concepts that are sufficiently similar that they can be used interchangeably in some information retrieval applications. In order to avoid the possibility of "compound errors" when combining mappings across more than two concept schemes, skos:closeMatch is not declared to be a transitive property.
[{data -> ML -> data / data -> ML -> data / data/sym/sym -> KR -> data -> ML -> data } -> ML -> data]
Property that binds a workflow execution process to its correspondant process template. Example: @prefix opmw: <http://www.opmw.org/ontology/> . @prefix opmv: <http://purl.org/net/opmv/ns#> . <http://www.opmw.org/export/resource/WorkflowExecutionProcess/REAERATIONEDM133549210450086> a opmv:Process, opmw:WorkflowExecutionProcess; opmw:correspondsToTemplateProcess <http://www.opmw.org/export/resource/WorkflowTemplateProcess/AQUAFLOW_EDM_REAERATIONEDM>.
corresponds to Template Process
Linking a paper with the countries of author's affiliations
A workflow execution process represents the execution of a step in workflow template. The execution process also describes the specific method used to acomplish the task described in the proces template. Example: @prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> . @prefix opmw: <http://www.opmw.org/ontology/> . @prefix opmv: <http://purl.org/net/opmv/ns#> . @prefix opmo: <http://openprovenance.org/model/opmo#> . <http://www.opmw.org/export/resource/WorkflowExecutionProcess/CONVERTTOSTANDARDFORMAT133553> a opmw:/WorkflowExecutionProcess , opmv:Process ; rdfs:label "Execution process ConvertToStandardFormat" ; opmo:account <http://www.opmw.org/export/resource/WorkflowExecutionAccount/ACCOUNT1335533097598> ; opmv:used <http://www.opmw.org/export/resource/WorkflowExecutionArtifact/6C7CF277338D9590EE18534D4D78924F> ; opmv:wasControlledBy <http://www.opmw.org/export/resource/Agent/ADMIN> ; opmw:hasWorkflowTemplateProcess <http://www.opmw.org/export/resource/WorkflowTemplateProcess/AQUAFLOW_EDM_CONVERTTOSTANDARDFORMAT> .
Workflow Execution Process
Describes in- and outputs to SWeML systems
Processing engine, that processes semantic web resources e.g. SPARQL query engine, reasoner
System has documentation providing details about e.g. training steps or split, used datasets and evaluation metrics
Documenation characteristics e.g. used dataset, training parameters, evaluation metrics
Concept
An idea or notion; a unit of thought.
Property used to annotate a workflow execution artifact with the size in bytes of its file. Example @prefix opmw: <http://www.opmw.org/ontology/> . @prefix opmv: <http://purl.org/net/opmv/ns#> . <http://www.opmw.org/export/resource/WorkflowExecutionArtifact/DCF49186981194248009E24BAD6A6412> a opmv:Artifact, opmw:WorkflowExecutionArtifact. opmw:hasLocation "68"^^xsd:int.
has Size
[International System of Cytogenetic Nomenclature]
A workflow execution artifact represents a resource used or generated in the execution of a workflow. Example: @prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> . @prefix opmw: <http://www.opmw.org/ontology/> . @prefix opmv: <http://purl.org/net/opmv/ns#> . @prefix opmo: <http://openprovenance.org/model/opmo#> . <http://www.opmw.org/export/resource/WorkflowExecutionArtifact/25F1016C12EBE301EE7AADBC0B085C45> a opmw:WorkflowExecutionArtifact , opmv:Artifact; rdfs:label "Execution artifact with id: 25f1016c12ebe301ee7aadbc0b085c45" ; opmo:account <http://www.opmw.org/export/resource/WorkflowExecutionAccount/ACCOUNT1335533097598> ; opmv:wasGeneratedBy <http://www.opmw.org/export/resource/WorkflowExecutionProcess/p1> ; opmw:hasLocation "http://wings.isi.edu/opmexport/resource/1/144/Formatted_SMN_2010_03_10Z"^^xsd:anyURI ; opmw:hasSize "8618"^^xsd:int ; opmw:hasWorkflowTemplateArtifact <http://www.opmw.org/export/resource/DataVariable/AQUAFLOW_EDM_FORMATTEDDATA>.
Workflow Execution Artifact
skos:prefLabel, skos:altLabel and skos:hiddenLabel are pairwise disjoint properties.
The range of skos:altLabel is the class of RDF plain literals.
alternative label
An alternative lexical label for a resource.
Acronyms, abbreviations, spelling variants, and irregular plural/singular forms may be included among the alternative labels for a concept. Mis-spelled terms are normally included as hidden labels (see skos:hiddenLabel).
A SWeML system has a corresponding pattern
Presence of documentation on used metrics in evaluation: yes, no
Advanded pattern type: a chain of Atomic and Fusion Patterns
Property that specifies whether a component is abstract or not.
is Concrete
example
An example of the use of a concept.
[Medical Information Mart for Intensive Care]
A workflow template represents the design of the workflow. In such design, the different steps and inputs don't have to be bound to a specific tool or dataset. It is a generic view of the workflow, which is instantiated in each execution. Example: @prefix dc: <http://purl.org/dc/terms/> . @prefix opmw: <http://www.opmw.org/ontology/> . <http://www.opmw.org/export/resource/WorkflowTemplate/AQUAFLOW_NTM> a opmw:WorkflowTemplate; rdfs:label "AquaFlow_NTM" ; dc.contributor <http://www.opmw.org/export/resource/Agent/WATER> ; dc:modified "2011-06-08T09:57:12-07:00"^^xsd:dateTime ; opmw:hasVersion "2"^^xsd:int .
Workflow Template
Presence of documentation on used infrastructure: yes, no
[{sym -> ML -> data / data} -> ML -> data]
definition
A statement or formal explanation of the meaning of a concept.
Presence of documentation on performed processing steps, such as pre-processing, cross-validation: yes, no
Paper type, e.g. Workshop or Conference paper
[sym -> ML1 -> sym -> ML2 -> data -> ML1]
Property used to link a workflow template to its native template (encoded in the syntax of the workflow system where it was designed: scufl, owl, etc.). Example: @prefix opmw: <http://www.opmw.org/ontology/> . <http://www.opmw.org/export/resource/WorkflowTemplate/AQUAFLOW_NTM> a opmw:WorkflowTemplate; opmw:hasNativeSystemTemplate "http://wind.isi.edu/marbles/assets/components/workflow_portal/users/1/Water/ontology/Water/AquaFlow_NTM.owl"xsd:anyURI.
has Native System Template
Basic pattern type: a single algorithmic module consumes a single input
Property used to annotate a resource with it version number. Example: @prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> . @prefix xsd: <http://www.w3.org/2001/XMLSchema#> . @prefix owl: <http://www.w3.org/2002/07/owl#> . @prefix opmw: <http://www.opmw.org/ontology/> . @prefix opmv: <http://purl.org/net/opmv/ns#> . @prefix opmo: <http://openprovenance.org/model/opmo#> . <http://www.opmw.org/export/resource/WorkflowTemplate/AQUAFLOW_NTM> a opmw:WorkflowTemplate; opmw:versionNumber "2"^^xsd:int.
version Number
Linking the semantic web resource with the resource size
A representation of symbolic data such as semantic entities or relations.
Resource type of the semantic web resources resource, e.g. ontology, queries
Image and Video - Image/Video processing
The range of skos:prefLabel is the class of RDF plain literals.
A resource has no more than one value of skos:prefLabel per language tag, and no more than one value of skos:prefLabel without language tag.
preferred label
The preferred lexical label for a resource, in a given language.
Presence of input/output data provenance collection: yes, no
Collection
A meaningful collection of concepts.
Labelled collections can be used where you would like a set of concepts to be displayed under a 'node label' in the hierarchy.
ARM [Association Rule learning, Association Rule Mining]
A workflow template artifact is part of a workflow template. It explains what kind of artifact is used or generated by the process template, along with possible restrictions that it may have. There are two different types of workflow template artifacts: data variables and parameter variables.
Workflow Template Artifact
Variable
A p-plan:Variable represents a description of the input of the planned Activity (p-plan:Step)
Keywords assigned to the publication by the authors
These concept mapping relations mirror semantic relations, and the data model defined below is similar (with the exception of skos:exactMatch) to the data model defined for semantic relations. A distinct vocabulary is provided for concept mapping relations, to provide a convenient way to differentiate links within a concept scheme from links between concept schemes. However, this pattern of usage is not a formal requirement of the SKOS data model, and relies on informal definitions of best practice.
is in mapping relation with
Relates two concepts coming, by convention, from different schemes, and that have comparable meanings
GHSOM [Growing Hierarchical Self Organizing Map]
SWeMLs can have one or more processing engines
skos:exactMatch is disjoint with each of the properties skos:broadMatch and skos:relatedMatch.
has exact match
skos:exactMatch is used to link two concepts, indicating a high degree of confidence that the concepts can be used interchangeably across a wide range of information retrieval applications. skos:exactMatch is a transitive property, and is a sub-property of skos:closeMatch.
Entity
A p-plan:Entity represents the input of the execution of a p-plan:Activity. It corresponds to a p-plan:Variable.
scope note
A note that helps to clarify the meaning and/or the use of a concept.
A workflow process template is an abstraction of the workflow execution process step that aims to describe the method followed by the scientist instead of its specific instantiation. Example: @prefix opmw: <http://www.opmw.org/ontology/> . @prefix water: <http://www.isi.edu/ac/Water/library.owl#> . <http://www.opmw.org/export/resource/WorkflowTemplateProcess/AQUAFLOW_NTM_CALCULATEHOURLYAVERAGES> a opmw:ProcessTemplate, water:CalculateHourlyAverages; opmw:template <http://www.opmw.org/export/resource/WorkflowTemplate/AQUAFLOW_NTM>; opmw:uses <http://www.opmw.org/export/resource/DataVariable/AQUAFLOW_NTM_FILTEREDDATA>.
Workflow Template Process
[{data -> ML -> data / sym} -> ML -> data]
[{sym -> ML -> data / data -> ML -> data} ->ML-> data]
[data -> ML -> sym -> { data/sym -> KR } -> sym]
Linking a SWeML system with a research area it is associated with
Plan
A p-plan:Plan is a specific type of prov:Plan. It is composed of smaller steps that use and produce Variables.
GMM [Gaussian Mixture Model, Mixture Models]
has broader match
skos:broadMatch is used to state a hierarchical mapping link between two conceptual resources in different concept schemes.
Positioning of the Paper in relation to research araeas e.g. Explainable AI or Semantic Web Mining
Property that represents the dimensionality of the artifact: 0 is a single file, 1 for a collection, etc. Example: @prefix opmw: <http://www.opmw.org/ontology/> . <http://www.opmw.org/export/resource/DataVariable/AQUAFLOW_NTM_DAILYDATA> a opmw:DataVariable, opmw:WorkflowTemplateArtifact; opmw:hasDimensionality "1"^^xsd:int.
has Dimensionality
[{data -> ML -> data / sym} -> ML -> sym]
Narrower concepts are typically rendered as children in a concept hierarchy (tree).
has narrower
Relates a concept to a concept that is more specific in meaning.
This data property binds a workflow template to the tool used for its design and creation. The tool is represented by its URL. Example: @prefix opmw: <http://www.opmw.org/ontology/> . <http://www.opmw.org/export/resource/WorkflowTemplate/AQUAFLOW_EDM> a opmw:WorkflowTemplate; opmw:createdInWorkflowSystem "http://wings.isi.edu"^^xsd:anyURI.
created in Workflow System
is top concept in scheme
Relates a concept to the concept scheme that it is a top level concept of.
Property used to dessignate which workflow Data Variables belong to a workflow template. Example: @prefix opmw: <http://www.opmw.org/ontology/> . <http://www.opmw.org/export/page/resource/DataVariable/AQUAFLOW_EDM_HOURLYDATA> a opmw:DataVariable; opmw:isVariableOfTemplate <http://www.opmw.org/export/resource/WorkflowTemplate/AQUAFLOW_EDM>.
Property that binds a workflow execution process to the specific component (code, scripts, etc.) used in the execution. Example: @prefix opmw: <http://www.opmw.org/ontology/> . @prefix opmv: <http://purl.org/net/opmv/ns#> . <http://www.opmw.org/export/resource/WorkflowExecutionProcess/REAERATIONEDM133549210450086> a opmv:Process, opmw:WorkflowExecutionProcess; opmw:hasExecutableComponent <http://www.opmw.org/export/resource/ReaerationEDM/COMPONENTREAERATIONEDM>.
has Executable Component
is in semantic relation with
Links a concept to a concept related by meaning.
This property should not be used directly, but as a super-property for all properties denoting a relationship of meaning between concepts.
MultiStep
A multi step is the representation of a plan that appears as a step of another plan.
Linking the system to the task it is solving
history note
A note about the past state/use/meaning of a concept.
Advanced pattern type: a chain of Atomic Patterns
Property used to link an execution artifact to the physical location of its file in the server. Example @prefix opmw: <http://www.opmw.org/ontology/> . @prefix opmv: <http://purl.org/net/opmv/ns#> . <http://www.opmw.org/export/resource/WorkflowExecutionArtifact/DCF49186981194248009E24BAD6A6412> a opmv:Artifact, opmw:WorkflowExecutionArtifact. opmw:hasLocation "http://www.opmw.org/datasets/resource/1/148/NTMParams_SMN_2010_03_14Z"^^xsd:anyURI.
has Location
Task that the SWeML system supposed to solve
Property to bind an execution account to the system where it was executed (which could be different from the one used for designing its workflow template). Example: @prefix opmw: <http://www.opmw.org/ontology/> . @prefix opmo: <http://openprovenance.org/model/opmo#> . <http://www.opmw.org/export/resource/WorkflowExecutionAccount/acc1> a opmo:Account, opmw:executionAccount; opmw:executedInWorkflowSystem <http://www.opmw.org/export/resource/Agent/SHELL>. <http://www.opmw.org/export/resource/Agent/SHELL> a opmw:Agent.
executed in Workflow System
Linking the system with the application domain it is working in
Property which states that none of the activities contained in the account finished executing after the End Time. Example: @prefix opmw: <http://www.opmw.org/ontology/> . @prefix opmo: <http://openprovenance.org/model/opmo#> . <http://www.opmw.org/export/resource/WorkflowExecutionAccount/ACCOUNT1335506667949> a opmw:WorkflowExecutionAccount,opmo:Account; opmw:overallEndTime "2012-04-25T10:28:55-07:00"^^xsd:dateTime.
overall End Time
isVariableofPlan
p-plan:IsVariableOfPlan binds a p-plan:Variable to the p-plan:Plan it corresponds to.
high maturity level (stable, enterprise, tool)
change note
A note about a modification to a concept.
Property used to state whether an ececution account was successful or not. Example: @prefix opmw: <http://www.opmw.org/ontology/> . @prefix opmo: <http://openprovenance.org/model/opmo#> . <http://www.opmw.org/export/resource/WorkflowExecutionAccount/ACCOUNT1335506667949> a opmo:Account, opmw:ExecutionAccount; opmw:hasStatus "SUCCESS"^^xsd.string.
has Status
correspondsToVariable
p-plan:correspondsToVariable binds a p-plan:Entity (used by a p-plan:Activity in the execution of a plan) to the p-plan:Variable it represented it in the p-plan:Plan.
The application domain in which the SWeML systems solve tasks (e.g. Chemistry, Legal)
Presence of documentation on used parameters: yes, no
System has a certain maturity according to different characteristics (stability, UI)
Linking the symbol formalism with the semantic web resource data
Property that links an execution account to its diagram. The diagram shows how the template has been instantiated with different components. Example: @prefix opmw: <http://www.opmw.org/ontology/> . @prefix opmo: <http://openprovenance.org/model/opmo#> . <http://www.opmw.org/export/resource/WorkflowExecutionAccount/ACCOUNT1335506667949> a opmw:WorkflowExecutionAccount,opmo:Account; opmw:hasExecutionDiagram "http://wind.isi.edu/marbles/assets/components/workflow_portal/users/1/Water/runs/run_148.png"^^sxd:anyURI.
has Execution Diagram
[{ sym>ML>sym / sym>ML>data } -> ML -> sym]
Hierarchical Relation Extraction [Hypernym discovery]
has broader transitive
skos:broaderTransitive is a transitive superproperty of skos:broader.
By convention, skos:broaderTransitive is not used to make assertions. Rather, the properties can be used to draw inferences about the transitive closure of the hierarchical relation, which is useful e.g. when implementing a simple query expansion algorithm in a search application.
Size of the semantic web resource(s) in triples
Formalism of the semantic web resource data
Linking SWeMLs to Knowledge Representation component(s) in different steps of the workflow
Linking SWeMLs to Machine Learning component(s) in different steps of the workflow
is in scheme
Relates a resource (for example a concept) to a concept scheme in which it is included.
A concept may be a member of more than one concept scheme.
[{sym -> ML -> data / data} -> ML -> sym]
Linking the system reported in the paper
Property used to dessignate which workflow Steps (or Workflow Template Processes) belong to a workflow template. Example: @prefix opmw: <http://www.opmw.org/ontology/> . <http://www.opmw.org/export/resource/WorkflowTemplateProcess/AQUAFLOW_EDM_CALCULATEHOURLYAVERAGES> a opmw:WorkflowTemplateProcess; opmw:isStepOfTemplate <http://www.opmw.org/export/resource/WorkflowTemplate/AQUAFLOW_EDM>.
Type of usage of the semantic web resource
Step
A p-plan:Step represents the planned execution activity
isInputVarOf
p-plan:isInputVarOf links an input variable of a step to the step.
Property used to dessignate which workflow Parameter Variables belong to a workflow template. Example: @prefix opmw: <http://www.opmw.org/ontology/> . <http://www.opmw.org/export/resource/ParameterVariable/AQUAFLOW_EDM_DATE> a opmw:ParameterVariable; opmw:isParameterOfTemplate <http://www.opmw.org/export/resource/WorkflowTemplate/AQUAFLOW_EDM>.
Property used to state the value of the artifact (in case of being a parameter). Example: @prefix opmw: <http://www.opmw.org/ontology/> . @prefix opmv: <http://purl.org/net/opmv/ns#> . <http://www.opmw.org/export/resource/WorkflowExecutionArtifact/DEPTH0.61959237> a opmv:Artifact, opmw:WorkflowExecutionArtifact; opmw:hasValue "0.61959237"^^xsd:string.
has Value
Presence of documentation on used software and libraries: yes, no
Linking the system with component models
correspondsToStep
p-plan:correspondsToStep links a p-plan:Activity to its planned p-plan:Step
Basic pattern type: a single algorithmic module consumes more than one input
Property which states that none of the activities in the current account started executing before the start time. Example: @prefix opmw: <http://www.opmw.org/ontology/> . @prefix opmo: <http://openprovenance.org/model/opmo#> . <http://www.opmw.org/export/resource/WorkflowExecutionAccount/ACCOUNT1335506667949> a opmw:WorkflowExecutionAccount,opmo:Account; opmw:overallStartTime "2012-04-25T10:28:07-07:00"^^xsd:dateTime.
overall Start Time
An parameter variable represents a description of an input parameter of a process. Parameter variables can only be used by process. Example: @prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> . @prefix opmw: <http://www.opmw.org/ontology/> . <http://www.opmw.org/export/resource/ParameterVariable/AQUAFLOW_NTM_LATITUDE> a opmw:/WorkflowTemplateArtifact , opmw:ParameterVariable ; rdfs:label "Parameter variable Latitude" ; opmw:template <http://www.opmw.org/export/resource/WorkflowTemplate/AQUAFLOW_NTM> .
Parameter Variable
A p-plan:Activity represents the execution process planned in a p-plan:Step
Activity
For any resource, every item in the list given as the value of the skos:memberList property is also a value of the skos:member property.
has member list
Relates an ordered collection to the RDF list containing its members.
Property that binds an execution account to the template of the whole workflow. The template contains the plan for the workflow. Example: @prefix opmw: <http://www.opmw.org/ontology/> . @prefix opmo: <http://openprovenance.org/model/opmo#> . <http://www.opmw.org/export/resource/WorkflowExecutionProcess/acc1> a opmo:Account, opmw:workflowExecutionAccount; opmw:correspondsToTemplate <http://www.opmw.org/export/resource/WorkflowTemplate/AQUAFLOW_EDM>.
corresponds to Template
Property that binds a workflow template to its documentation. Example: @prefix opmw: <http://www.opmw.org/ontology/> . <http://www.opmw.org/export/resource/WorkflowTemplate/AQUAFLOW_NTM> a opmw:WorkflowTemplate; opmw:hasDocumentation "A copy of the documentation related to this template "^^xsd:string.
has Documentation
Presence of documentation on used training, development and test set used in evaluation: yes, no
The range of skos:hiddenLabel is the class of RDF plain literals.
hidden label
A lexical label for a resource that should be hidden when generating visual displays of the resource, but should still be accessible to free text search operations.
isDecomposedAsPlan
The p-plan:isDecomposedAsPlan relationship binds a p-plan:MultiStep to the p-plan:Plan holding the definition of that step. That is, p-plan:isDecomposedAsPlan links the MultiStep to the Plan sptecification where it is decomposed.
[Chemical Entities of Biological Interest]
isStepOfPlan
p-plan:isStepOfPlan links a p-plan:Step to the p-plan:Plan which it corresponds to.
Property that binds a workflow execution artifact to its correspondant workflow template artifact. Example: @prefix opmw: <http://www.opmw.org/ontology/> . @prefix opmv: <http://purl.org/net/opmv/ns#> . <http://www.opmw.org/export/resource/WorkflowExecutionArtifact/DEPTH1.2150836> a opmv:Artifact, opmw:WorkflowExecutionArtifact; opmw:correspondsToTemplateArtifact <http://www.opmw.org/export/resource/ParameterVariable/AQUAFLOW_EDM_DEPTH>.
corresponds to Template Artifact
[{sym -> KR -> data / data} -> ML -> sym]
Property used to link an execution account or a workflow execution process to the correspondent log file produced by the enacting workflow engine. Example: @prefix opmw: <http://www.opmw.org/ontology/> . @prefix opmo: <http://openprovenance.org/model/opmo#> . <http://www.opmw.org/export/resource/WorkflowExecutionAccount/ACCOUNT1335506667949> a opmw:WorkflowExecutionAccount,opmo:Account; opmw:hasOriginalLogFile "http://wind.isi.edu/marbles/assets/components/workflow_portal/users/1/Water/runs/run_148.ttl"^^sxd:anyURI.
has Original Log File
skos:related is disjoint with skos:broaderTransitive
has related
Relates a concept to a concept with which there is an associative semantic relationship.
Advanced pattern type: combination of two (or more) Atomic Patterns via a Fusion Pattern
Linking the corresponding step of a pattern workflow with a specific system component
An ontology to describe a Semantic-Web Machine Learning System (SWeMLS)
Semantic-Web Machine Learning System (SWeMLS) Ontology