Submissions:Standard Enforcer Pattern Revision as of 13:18, 13 August 2012 by MonikaSolanki (Talk | contribs) (Imported from OWL file.) (diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Warning!

This is an old revision. Go to current revision

This pattern has been certified.

Related submission, with evaluation history, can be found here

Last modified date is: 2012-08-13

Graphical representation

Diagram (this article has no graphical representation)

General description

Name:	Standard Enforcer Pattern
Submitted by:	MonikaSolanki
Also Known As:
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 activity operation and service 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:
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 th
Scenarios:	As an exemplifier for SEP, we present a use case from the domain of 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.
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:

enforcesGuideline (owl:ObjectProperty)

enforcesGuideline page

enforcesStandard (owl:ObjectProperty)

enforcesStandard page

guidelinePrescribedIn (owl:ObjectProperty)

guidelinePrescribedIn page

hasDomainScope (owl:ObjectProperty)

hasDomainScope page

hasProcessScope (owl:ObjectProperty)

hasProcessScope page

isEnforcedBy (owl:ObjectProperty)

isEnforcedBy page

prescribesGuideline (owl:ObjectProperty)

prescribesGuideline page

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

ProcessScope (owl:Class) An entity that defines the scope of a process

ProcessScope 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 page

Scenarios

Scenarios about Standard Enforcer Pattern

No scenario is added to this Content OP.

Reviews

Reviews about Standard Enforcer Pattern

There is no review about this proposal.

Some subquery has no valid condition.

This revision (revision ID 11105) 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.

Some subquery has no valid condition.

References

Add a reference

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.