Submissions:Standard Enforcer Pattern - Revision history

ValentinaPresutti: Review has been created. Annotation 'assigned' has been removed.

2012-08-30T08:29:49Z

Review has been created. Annotation 'assigned' has been removed.

KarlHammar: Review has been assigned.

2012-08-14T08:19:37Z

Review has been assigned.

KarlHammar: Review has been assigned.

2012-08-14T08:19:19Z

Review has been assigned.

KarlHammar: Review has been assigned.

2012-08-14T08:19:00Z

Review has been assigned.

MonikaSolanki: Submission to WOP:2012

2012-08-13T14:51:32Z

Submission to WOP:2012

MonikaSolanki at 14:35, 13 August 2012

2012-08-13T14:35:12Z

MonikaSolanki at 14:33, 13 August 2012

2012-08-13T14:33:07Z

MonikaSolanki at 14:31, 13 August 2012

2012-08-13T14:31:59Z

MonikaSolanki at 14:26, 13 August 2012

2012-08-13T14:26:39Z

MonikaSolanki at 14:23, 13 August 2012

2012-08-13T14:23:52Z

@@ Line 76: / Line 76: @@
 |Event=WOP:2012
 }}
-[[Category:Review assigned]]
-[[Category:Review assigned]]
 [[Category:Review assigned]]

@@ Line 76: / Line 76: @@
 |Event=WOP:2012
 }}
 [[Category:Review assigned]]
 [[Category:Review assigned]]

@@ Line 76: / Line 76: @@
 |Event=WOP:2012
 }}
 [[Category:Review assigned]]

← Older revision		Revision as of 08:19, 14 August 2012
Line 76:		Line 76:
	\|Event=WOP:2012		\|Event=WOP:2012
	}}		}}
		+	[[Category:Review assigned]]

← Older revision		Revision as of 14:51, 13 August 2012
Line 73:		Line 73:
	{{Modeling issues about me}}		{{Modeling issues about me}}
	{{My references}}		{{My references}}
		+	{{Submission to event
		+	\|Event=WOP:2012
		+	}}

@@ Line 22: / Line 22: @@
 |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.
-|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.
+|Scenario=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.
 }}
 {{Element list header}}

@@ Line 8: / Line 8: @@
 |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 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.
 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.
 |CompetencyQuestion=1. Which are the standards enforced by this process?,
 . Which processes enforce these standards ?,

@@ Line 15: / Line 15: @@
 |CompetencyQuestion=1. Which are the standards enforced by this process?,
 . Which processes enforce these standards ?,
-. What is/are the domain level scope(s) of the
+. What is/are the domain level scope(s) of the standard?,
-  standard?,
+. Within the context of the domain what is the scope of the process to which the standard is applicable?,
 . Within the context of the domain what is the scope of the
-  process to which the standard is applicable?,
 . What are the prescribed guidelines for a standard?,
-. Which prescribed guideline(s) of a standard does a specific
+. 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
@@ Line 28: / Line 25: @@
 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 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.
 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
 |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.
 }}