| Line 22: | Line 22: | ||
|ReusableOWLBuildingBlock=http://windermere.aston.ac.uk/~monika/ontologies/Standards-Enforcer-Pattern.owl | |ReusableOWLBuildingBlock=http://windermere.aston.ac.uk/~monika/ontologies/Standards-Enforcer-Pattern.owl | ||
|Consequences=The pattern can be applied to use cases in all those domains where a standard is enforced to regulate processes. The main advantage of this pattern is that it provides the capability to link processes, operations, activities and services to their governing standards in a generic and compositional manner. In some scenarios it is possible that a process or an operation does not enforce all prescribed guidelines but enforces atleast some. The pattern accounts for that through the definition of the process enforcing the standard. | |Consequences=The pattern can be applied to use cases in all those domains where a standard is enforced to regulate processes. The main advantage of this pattern is that it provides the capability to link processes, operations, activities and services to their governing standards in a generic and compositional manner. In some scenarios it is possible that a process or an operation does not enforce all prescribed guidelines but enforces atleast some. The pattern accounts for that through the definition of the process enforcing the standard. | ||
| − | |Scenario=As an exemplifier for SEP, we present a use case from the domain | + | |Scenario=As an exemplifier for SEP, we present a use case from the domain of algal biomass production which depicts theapplication of SEP to an ontology that models algal biomassproduction. The Minimum Descriptive Language (MDL) standard proposed by the Algal Biomass Association is enforced by theproduction operation. MDL recommends a set of descriptive metrics touniformly characterise the analysis of large scale algaloperations. In this use case, the ontology defines the concepts andrelationships for the operation and incorporates SEP by enforcing aguideline for measuring Carbon input to the operation. |
}} | }} | ||
{{Element list header}} | {{Element list header}} | ||
|
Last modified date is: 2012-08-13 |
Diagram
| Name: | Standard Enforcer Pattern |
|---|---|
| Submitted by: | MonikaSolanki |
| Also Known As: | SEP |
| Intent: | The remit of the SEP content pattern is to represent the relation between standards and the processes, operations, activities and services that enforce them, the domains they cater to and the scope of that specific process, operation, activity, service within the context of the domain. |
| Domains: | |
| Competency Questions: |
|
| Solution description: | SEP provides a mechanism to ontologically declare the conformance of a
process with one or more standards. The pattern is flexible and compositional. It can be exploited to include few or more guidelines from multiple standards and can be easily combined with other patterns. |
| Reusable OWL Building Block: | 1 (589) |
| Consequences: | The pattern can be applied to use cases in all those domains where a standard is enforced to regulate processes. The main advantage of this pattern is that it provides the capability to link processes, operations, activities and services to their governing standards in a generic and compositional manner. In some scenarios it is possible that a process or an operation does not enforce all prescribed guidelines but enforces atleast some. The pattern accounts for that through the definition of the process enforcing the standard. |
| Scenarios: | As an exemplifier for SEP, we present a use case from the domain of algal biomass production which depicts theapplication of SEP to an ontology that models algal biomassproduction. The Minimum Descriptive Language (MDL) standard proposed by the Algal Biomass Association is enforced by theproduction operation. MDL recommends a set of descriptive metrics touniformly characterise the analysis of large scale algaloperations. In this use case, the ontology defines the concepts andrelationships for the operation and incorporates SEP by enforcing aguideline for measuring Carbon input to the operation. |
| Known Uses: | |
| Web References: | |
| Other References: | |
| Examples (OWL files): | |
| Extracted From: | |
| Reengineered From: | |
| Has Components: | |
| Specialization Of: | |
| Related CPs: |
The Standard Enforcer Pattern Content OP locally defines the following ontology elements:
DomainScope (owl:Class) An entity that identifies the domain level scope of the standard
DomainScope page Guideline (owl:Class) An entity that defines the guideline that is part of a standard
Guideline page Process (owl:Class) An entity that defines a workflow, operation, activity or a service
Process page ProcessEnforcingStandard (owl:Class) A process/operation/activity or serrvice that enforces one or more standard.
ProcessEnforcingStandard page Standard (owl:Class) An entity that identifies a specification established through domain expert consensus that prescribes a set of rules and guidelines for a given context within the domain.
Standard pageThis ontology models the standards enforcer pattern (SEP). The main advantage of this pattern is that it provides the capability to link processes operation and activities to their governing standards in a generic way. The pattern can be applied to all those use cases where a standard is enforced.
No scenario is added to this Content OP.
This revision (revision ID 11124) takes in account the reviews: none
Other info at evaluation tab
'Ontology Design Patterns'
