Submissions:Template Instance - Revision history

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

2012-08-28T16:53:04Z

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

KarlHammar: Review has been assigned.

2012-08-14T08:25:31Z

Review has been assigned.

KarlHammar: Review has been assigned.

2012-08-14T08:25:00Z

Review has been assigned.

KarlHammar: Review has been assigned.

2012-08-14T08:24:45Z

Review has been assigned.

CsongorNyulas: Improvements to Description formatting; Fixed link to reusable OWL building block; Added download links to Example OWL files; Fixed links to ICD-11 and ICTM

2012-08-14T00:51:45Z

Improvements to Description formatting; Fixed link to reusable OWL building block; Added download links to Example OWL files; Fixed links to ICD-11 and ICTM

CsongorNyulas: New page: {{Content_OP_Proposal_toolbar}} {{Graphical representation header}} {{Graphical representation |ImageName=TemplatePatternBeforeAndAfter.png }} {{Content OP Proposal Template |SubmittedBy=C...

2012-08-11T10:15:46Z

New page: {{Content_OP_Proposal_toolbar}} {{Graphical representation header}} {{Graphical representation |ImageName=TemplatePatternBeforeAndAfter.png }} {{Content OP Proposal Template |SubmittedBy=C...

New page

{{Content_OP_Proposal_toolbar}}
{{Graphical representation header}}
{{Graphical representation
|ImageName=TemplatePatternBeforeAndAfter.png
}}
{{Content OP Proposal Template
|SubmittedBy=CsongorNyulas,
|Name=Template Instance
|Intent=The Template Instance pattern proposes a way of reducing the number of reified instances and the related property assertion axioms in an ontology, especially for the cases in which the reified relations are identical for multiple entities.
|Domain=General,
|ContentODPDescription=The pattern proposes to use the same “template” instance as the value of a reified property for multiple subjects (rather than having multiple copies of the same reified instance). We give an example in Figure 1 to make it easier to understand. The individuals x1, x2 and x3 have a reified property p that have as values the reified individuals, y1, y2 and y3, respectively. In OWL, we would have object property assertions: (x1 p y1), (x2 p y2), (x3 p y3). The properties for the reified individuals, y1, y2 and y3 are all identical: (y_ p1 foo), (y_ p2 1.0) and (y_ p3 z).

The pattern proposes to create a template instance, y_tmpl that has the property values the common values:
(y_tmpl p1 foo), (y_tmpl p2 1.0), (y_tmpl p3 z)

The template instance would be used as the value for the reified property for x1, x2 and x3:
(x1 p y_tmpl), (x2 p y_tmpl), (x3 p y_tmpl)

In addition, we will also add one annotation property, isTemplate:true, on y_tmpl to mark that it as a template instance.
The intention is that the template instance is immutable, i.e., the property values of the template instance cannot be changed.

In the case that a user would like to change a property value of the reified relation, a clone of the template instance would be created and the change would occur on the clone. An ontology editor would use the isTemplate annotation property to check that a certain instance cannot be modified, and it should rather create a clone.

Figure 1 gives an example of this situation. Say that at a given time t0, there was an additional x4 individual that had the template instance as the value for p.

At t0: (x4 p y_tmpl)
(y_tmpl p1 foo), (y_tmpl p2 1.0), (y_tmpl p3 z)

Later, at time t1, the user decides to change the value p1 from “foo” to “bar”. The ontology editor (or the user, if there is no support in the tool), will see the isTemplate annotation property on y_tmpl as set on true, and it will create a clone of it, y_tmpl_modif, by cloning also all the object and data property axioms. Then, it will change the value of p1 on y_tmpl_modif. So, the result will be:

At t1: (x4 p y_tmpl_modif)
(y_tmpl_modif p1 bar), (y_tmpl_modif p2 1.0), (y_tmpl_modif p3 z)

As a result of using the template instance pattern, we could reduce the number of data and object property axioms in the ontology. This “deflation” of the ontology is especially significant, if there are many repetitive values in the ontology, with very few changes, and if the number of properties of the reified instance is large.
|ReusableOWLBuildingBlock=http://www.ontologydesignpatterns.org/cp/owl/Template_instance_odp.owl
|KnownUse=ICD11, ICTM
|RelatedCP=Literal Reification,
}}
{{Element list header}}
{{Additional information header}}

{{Scenarios about me}}
{{Reviews about me}}
{{Modeling issues about me}}
{{My references}}
{{Submission to event
|Event=WOP:2012
}}

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

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

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

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

@@ Line 5: / Line 5: @@
 }}
 {{Content OP Proposal Template
 |SubmittedBy=CsongorNyulas,
 |Name=Template Instance
 |Intent=The Template Instance pattern proposes a way of reducing the number of reified instances and the related property assertion axioms in an ontology, especially for the cases in which the reified relations are identical for multiple entities.
 |Domain=General,
-|ContentODPDescription=The pattern proposes to use the same “template” instance as the value of a reified property for multiple subjects (rather than having multiple copies of the same reified instance). We give an example in Figure 1 to make it easier to understand. The individuals x1, x2 and x3 have a reified property p that have as values the reified individuals, y1, y2 and y3, respectively. In OWL, we would have object  property assertions: (x1 p y1), (x2 p y2), (x3 p y3). The properties for the reified individuals, y1, y2 and y3 are all identical: (y_ p1  foo), (y_ p2 1.0) and (y_ p3 z).
+|ContentODPDescription=The pattern proposes to use the same “template” instance as the value of a reified property for multiple subjects (rather than having multiple copies of the same reified instance). The diagram presents an example of the usage of the pattern, for an easier understanding. The individuals <code style="font-size:larger;">x1</code>, <code style="font-size:larger;">x2</code> and <code style="font-size:larger;">x3</code> have a reified property <code style="font-size:larger;">p</code> that have as values the reified individuals, <code style="font-size:larger;">y1</code>, <code style="font-size:larger;">y2</code> and <code style="font-size:larger;">y3</code>, respectively. In OWL, we would have object  property assertions: <code style="font-size:larger;">(x1 p y1)</code>, <code style="font-size:larger;">(x2 p y2)</code>, <code style="font-size:larger;">(x3 p y3)</code>. The properties for the reified individuals, <code style="font-size:larger;">y1</code>, <code style="font-size:larger;">y2</code> and <code style="font-size:larger;">y3</code> are all identical: <code style="font-size:larger;">(y_ p1  foo)</code>, <code style="font-size:larger;">(y_ p2 1.0)</code> and <code style="font-size:larger;">(y_ p3 z)</code>.
-The pattern proposes to create a template instance, y_tmpl that has the property values the common values:
+The pattern proposes to create a template instance, <code style="font-size:larger;">y_tmpl</code> having the common values as its property values:
-(y_tmpl p1 foo), (y_tmpl p2 1.0), (y_tmpl p3 z)
+<code style="font-size:larger;">(y_tmpl p1 foo), (y_tmpl p2 1.0), (y_tmpl p3 z)</code>
-The template instance would be used as the value for the reified property for x1, x2 and x3:
+The template instance would be used as the value for the reified property for <code style="font-size:larger;">x1</code>, <code style="font-size:larger;">x2</code> and <code style="font-size:larger;">x3</code>:
-(x1 p y_tmpl), (x2 p y_tmpl), (x3 p y_tmpl)
+<code style="font-size:larger;">(x1 p y_tmpl), (x2 p y_tmpl), (x3 p y_tmpl)</code>
-In addition, we will also add one annotation property, isTemplate:true, on y_tmpl to mark that it as a template instance.
+In addition, we will also add one annotation property, <code style="font-size:larger;">isTemplate:true</code>, on <code style="font-size:larger;">y_tmpl</code> to mark that it as a template instance.
 The intention is that the template instance is immutable, i.e., the property values of the template instance cannot be changed.
-In the case that a user would like to change a property value of the reified relation, a clone of the template instance would be created and the change would occur on the clone. An ontology editor would use the isTemplate annotation property to check that a certain instance cannot be modified, and it should rather create a clone.
+<br />
-Figure 1 gives an example of this situation. Say that at a given time t0, there was an additional x4 individual that had the template instance as the value for p.
+The right side of the diagram gives an example of this situation. Say that at a given time t<sub>0</sub>, there was an additional x4 individual that had the template instance as the value for p.
-At t0: (x4 p y_tmpl)
+At t<sub>0</sub>: <code style="font-size:larger;">(x4 p y_tmpl)<br />
-(y_tmpl p1 foo), (y_tmpl p2 1.0), (y_tmpl p3 z)
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(y_tmpl p1 foo), (y_tmpl p2 1.0), (y_tmpl p3 z)</code>
-Later, at time t1, the user decides to change the value p1 from “foo” to “bar”. The ontology editor (or the user, if there is no support in the tool), will see the isTemplate annotation property on y_tmpl as set on true, and it will create a clone of it, y_tmpl_modif, by cloning also all the object and data property axioms. Then, it will change the value of p1 on y_tmpl_modif. So, the result will be:
+Later, at time t<sub>1</sub>, the user decides to change the value <code style="font-size:larger;">p1</code> on x4 from “foo” to “bar”. The ontology editor (or the user, if there is no support in the tool), will see the <var>isTemplate</var> annotation property on <code style="font-size:larger;">y_tmpl</code> as set on true, and it will create a clone of it, <code style="font-size:larger;">y_tmpl_modif</code>, by cloning also all the object and data property axioms. Then, it will change the value of <code style="font-size:larger;">p1</code> on <code style="font-size:larger;">y_tmpl_modif</code>. So, the result will be:
-At t1: (x4 p y_tmpl_modif)
+At t<sub>1</sub>: <code style="font-size:larger;">(x4 p y_tmpl_modif)<br />
-(y_tmpl_modif p1 bar), (y_tmpl_modif p2 1.0), (y_tmpl_modif p3 z)
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(y_tmpl_modif p1 bar), (y_tmpl_modif p2 1.0), (y_tmpl_modif p3 z)</code>
-As a result of using the template instance pattern, we could reduce the number of data and object property axioms in the ontology. This “deflation” of the ontology is especially significant, if there are many repetitive values in the ontology, with very few changes, and if the number of properties of the reified instance is large.
+<br />
-|ReusableOWLBuildingBlock=http://www.ontologydesignpatterns.org/cp/owl/Template_instance_odp.owl
+As a result of using the Template Instance pattern, one could reduce the number of data and object property axioms in the ontology. This “deflation” of the ontology is especially significant, if there are many repetitive values in the ontology, with very few changes, and if the number of properties of the reified instances is large.
-|KnownUse=ICD11, ICTM
+|ReusableOWLBuildingBlock=http://smi-protege.stanford.edu/collab-protege/templInstPattern/template_instance_odp.owl
-|RelatedCP=Literal Reification,
+|KnownUse=http://www.who.int/classifications/icd/revision/en/index.html, https://sites.google.com/site/whoictm/
 }}
 {{Element list header}}