Submissions:Standard Enforcer Pattern

From Odp

(Difference between revisions)
Jump to: navigation, search
(Imported from OWL file.)
Line 2: Line 2:
{{Graphical representation header}}
{{Graphical representation header}}
{{Graphical representation
{{Graphical representation
-
|ImageName=
+
|ImageName=Standard-enforcer-pattern.png
}}
}}
{{Content OP Proposal Template
{{Content OP Proposal Template
 +
|SubmittedBy=MonikaSolanki
 +
|Name=Standard Enforcer Pattern
 +
|ContentODPAlsoKnownAs=SEP
|Intent=The remit of the SEP content pattern is to represent the relation
|Intent=The remit of the SEP content pattern is to represent the relation
between standards and the processes, operations, activities and
between standards and the processes, operations, activities and
Line 10: Line 13:
that specific process, operation, activity, service within the context
that specific process, operation, activity, service within the context
of the domain.
of the domain.
-
|CompetencyQuestion=1. Which are the standards enforced
+
|CompetencyQuestion=1. Which are the standards enforced by this process?,
-
  by this process?
+
2. Which processes enforce these standards ?,  
-
2. Which processes enforce these standards ?   
+
3. What is/are the domain level scope(s) of the  
3. What is/are the domain level scope(s) of the  
-
   standard?   
+
   standard?,  
4. Within the context of the domain what is the scope of the
4. Within the context of the domain what is the scope of the
-
   process, activity, operation and service to which the standard is
+
   process to which the standard is applicable?,
-
  applicable?
+
5. What are the prescribed guidelines for a standard?,
-
5. What are the prescribed guidelines for a standard?
+
6. Which prescribed guideline(s) of a standard does a specific
6. Which prescribed guideline(s) of a standard does a specific
-
   process conform to?  
+
   process conform to?
 +
|ContentODPDescription=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.
 +
|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
|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
standard is enforced to regulate processes.  The main advantage of
Line 28: Line 35:
that a process or an operation does not enforce all prescribed
that a process or an operation does not enforce all prescribed
guidelines but enforces atleast some. The pattern accounts for th
guidelines but enforces atleast some. The pattern accounts for th
-
|Scenario=As an exemplifier for SEP, we present a use case from the domain of
+
|Scenario=As an exemplifier for SEP, we present a use case from the domain ofalgal 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.
-
algal biomass production which depicts the
+
-
application of SEP to an ontology that models algal biomass
+
-
production. The Minimum Descriptive Language (MDL) standard proposed by the Algal Biomass Association
+
-
is enforced by the
+
-
production operation.  MDL recommends a set of descriptive metrics to
+
-
uniformly characterise the analysis of large scale algal
+
-
operations. In this use case, the ontology defines the concepts and
+
-
relationships for the operation and incorporates SEP by enforcing a
+
-
guideline for measuring Carbon input to the operation.
+
-
|SubmittedBy=MonikaSolanki
+
-
|ReusableOWLBuildingBlock=http://windermere.aston.ac.uk/~monika/ontologies/Standards-Enforcer-Pattern.owl
+
-
|Name=Standard Enforcer Pattern
+
}}
}}
{{Element list header}}
{{Element list header}}
Line 82: Line 77:
|HasElement=Standard
|HasElement=Standard
}}
}}
-
 
{{Additional information header}}
{{Additional information header}}
-
 
-
{{Scenarios about me}}
 
-
{{Reviews about me}}{{Modeling issues about me}}{{My references}}
 
This ontology models the standards enforcer pattern (SEP). The main advantage of this pattern is that it provides the capability
This 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
to link processes operation and activities to their governing
standards in a generic way. The pattern can be applied to all those
standards in a generic way. The pattern can be applied to all those
use cases where a standard is  enforced.
use cases where a standard is  enforced.
 +
{{Scenarios about me}}
 +
{{Reviews about me}}
 +
{{Modeling issues about me}}
 +
{{My references}}

Revision as of 14:23, 13 August 2012


This pattern has been certified.

Related submission, with evaluation history, can be found here

If you are a member of quality committee please visit the

evaluation section

If you are author of this proposal or you want to contribute to this pattern's review, you can:

In general, it could be useful to visit the evaluation section to have information about the evaluation process of this proposal

Current revision ID: 11119

Graphical representation

Diagram

Image:Standard-enforcer-pattern.png

General description

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:
  • 1. Which are the standards enforced by this process?
  • 2. Which processes enforce these standards ?
  • 3. What is/are the domain level scope(s) of the 
 standard?
  • 4. Within the context of the domain what is the scope of the 
 process to which the standard is applicable?
  • 5. What are the prescribed guidelines for a standard?
  • 6. Which prescribed guideline(s) of a standard does a specific 
 process conform to?
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: http://windermere.aston.ac.uk/~monika/ontologies/Standards-Enforcer-Pattern.owl (1016)
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 th

Scenarios: As an exemplifier for SEP, we present a use case from the domain ofalgal 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:


Elements

The Standard Enforcer Pattern Content OP locally defines the following ontology elements:

ObjectProperty enforcesGuideline (owl:ObjectProperty)
enforcesGuideline page
ObjectProperty enforcesStandard (owl:ObjectProperty)
enforcesStandard page
ObjectProperty guidelinePrescribedIn (owl:ObjectProperty)
guidelinePrescribedIn page
ObjectProperty hasDomainScope (owl:ObjectProperty)
hasDomainScope page
ObjectProperty hasProcessScope (owl:ObjectProperty)
hasProcessScope page
ObjectProperty isEnforcedBy (owl:ObjectProperty)
isEnforcedBy page
ObjectProperty prescribesGuideline (owl:ObjectProperty)
prescribesGuideline page
Class DomainScope (owl:Class) An entity that identifies the domain level scope of the standard
DomainScope page
Class Guideline (owl:Class) An entity that defines the guideline that is part of a standard
Guideline page
Class Process (owl:Class) An entity that defines a workflow, operation, activity or a service
Process page
Class ProcessEnforcingStandard (owl:Class) A process/operation/activity or serrvice that enforces one or more standard.
ProcessEnforcingStandard page
Class ProcessScope (owl:Class) An entity that defines the scope of a process
ProcessScope page
Class 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 page

Additional information

This 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.

Scenarios

Scenarios about Standard Enforcer Pattern

No scenario is added to this Content OP.

Reviews

Reviews about Standard Enforcer Pattern
Review article Posted on About revision (current is 11119)
GerdGroener about Standard Enforcer Pattern 245617030 August 2012 1114911,149
IonelVirgilPop about Standard Enforcer Pattern 245616424 August 2012 1114911,149
BorisVillazón-Terrazas about Standard Enforcer Pattern 245617030 August 2012 1121011,210

This revision (revision ID 11119) takes in account the reviews: none

Other info at evaluation tab


Modeling issues

Modeling issues about Standard Enforcer Pattern

There is no Modeling issue related to this proposal.


References

Add a reference


Retrieved from "http://ontologydesignpatterns.org/wiki/Submissions:Standard_Enforcer_Pattern"
Personal tools
Quality Committee
Content OP publishers