Science Environment for Ecological Knowledge
Ecoinformatics site parent site of Partnership for Biodiversity Informatics site parent site of SEEK - Home
Science Environment for Ecological Knowledge









 

 

 



KRSMS Semantic Annotation Language

Difference between version 170 and version 169:

Line 119 was replaced by line 119
- !!!!3.1 Individuals
+ !!3.1 Individuals
Line 197 was replaced by line 197
- !!!!3.2 Object Properties
+ !!3.2 Object Properties
Lines 213-214 were replaced by line 213
- __n__ unique values of {{x}} in {{R}} <a
- href="#6">[6]</a>.
+ __n__ unique values of {{x}} in {{R}}[6].
Line 318 was replaced by line 317
- !!!3.3 Datatype Properties
+ !!3.3 Datatype Properties
Line 370 was replaced by line 369
- This pattern can be read as "For each unique x value of R, create
+ This pattern can be read as "For each unique x value of R, create
Line 381 was replaced by line 380
- Resource variables can be used outside of the current iteration
+ Resource variables can be used outside of the current iteration
Line 397 was replaced by line 396
- This pattern can be read as "For each unique x value of R, create
+ This pattern can be read as "For each unique x value of R, create
Line 421 was replaced by line 420
- corresponds to the following first-order rule, assuming
+ corresponds to the following first-order rule, assuming
Lines 430-431 were replaced by line 429
-
- In an instantiation pattern, {{value}} expressions must
+ In an instantiation pattern, {{value}} expressions must
Line 458 was replaced by line 456
- Thus, the condition on the property does not affect whether the
+ Thus, the condition on the property does not affect whether the
Line 465 was replaced by line 463
- Like with conditions on {{individual}} statements, no
+ Like with conditions on {{individual}} statements, no
Line 475 was replaced by line 473
- !!!3.3 Complex Instantiation Patterns
+ !!3.3 Complex Instantiation Patterns
Line 486 was replaced by line 484
- __Pattern Labels.__ Each individual instantiation pattern can
+ __Pattern Labels.__ Each individual instantiation pattern can
Line 494 was replaced by line 492
- The first-order rule for this pattern is:
+ The first-order rule for this pattern is:
Line 500 was replaced by line 498
- The use of labels in this way does not change the interpretation
+ The use of labels in this way does not change the interpretation
Lines 505-507 were replaced by lines 503-504
- __Referencing Patterns.__ Properties can reference patterns
- using pattern labels in {{value}} expressions <a
- href="#9">[9]</a>. To distinguish pattern references from constants
+ __Referencing Patterns.__ Properties can reference patterns
+ using pattern labels in {{value}} expressions[9]. To distinguish pattern references from constants
Line 518 was replaced by line 515
- This pattern can be read as "For each unique x, y (tuple) value
+ This pattern can be read as "For each unique x, y (tuple) value
Line 528 was replaced by line 525
- As with resource variables, pattern references are interpreted
+ As with resource variables, pattern references are interpreted
Line 537 was replaced by line 534
- The iteration context of a property is not required to be a
+ The iteration context of a property is not required to be a
Line 547 was replaced by line 544
- each unique {{y}}, {{z}} pair for {{R}}
+ each unique {{y}}, {{z}} pair for {{R}}
Line 553 was replaced by line 550
- Also, the iteration context of a property only applies to the
+ Also, the iteration context of a property only applies to the
Line 568 was replaced by line 565
- The corresponding first-order rules for these patterns are:
+ The corresponding first-order rules for these patterns are:
Line 578 was replaced by line 575
- Thus, although property values containing pattern references are
+ Thus, although property values containing pattern references are
Line 591 was replaced by line 588
- The triples created from pattern {{o1}} are:
+ The triples created from pattern {{o1}} are:
Line 598 was replaced by line 595
- The triples created from pattern {{o4}} are:
+ The triples created from pattern {{o4}} are:
Line 606 was replaced by line 603
- And the triples created from pattern {{o5}} are:
+ And the triples created from pattern {{o5}} are:
Line 615 was replaced by line 612
- Notice that both individuals of pattern {{o5}} are
+ Notice that both individuals of pattern {{o5}} are
Line 623 was replaced by line 620
- To use the iteration context of {{o5}} for
+ To use the iteration context of {{o5}} for
Line 636 was replaced by line 633
- The corresponding first-order rule for this pattern is:
+ The corresponding first-order rule for this pattern is:
Line 645 was replaced by line 642
- Note that in this case, however, we generate only one
+ Note that in this case, however, we generate only one
Line 651 was replaced by line 648
- __Property Iteration and Labels__. It is also possible to apply
+ __Property Iteration and Labels__. It is also possible to apply
Line 665 was replaced by line 662
- results in the first-order rule:
+ results in the first-order rule:
Line 675 was replaced by line 672
- As shown, labels may also be applied to intermediate individuals
+ As shown, labels may also be applied to intermediate individuals
Removed line 683
-
Lines 686-697 were replaced by line 682
- __<a name="annotation">Semantic Annotation<a/>:__ A mapping
- from a resource to an instance(s) of an ontology(ies). Semantic
- annotations in our framework have identifiers as well as associated
- metadata (who created the annotation, and so on).
-
- __<a name="resource">Resource</a>:__ A structured information
- source with a defined schema. Can be a dataset or a service, such as
- a workflow, actor, or web-service.
-
- __<a name="ontology">Ontology</a>:__ Here, by ontology we mean
- an OWL-based representation of a set of concepts, properties, and
- constraints (axioms).
+ ;Semantic Annotation: A mapping from a resource to an instance(s) of an ontology(ies). Semantic annotations in our framework have identifiers as well as associated metadata (who created the annotation, and so on).
Lines 699-725 were replaced by lines 684-709
- __<a name="template">Semantic Annotation Template</a>:__ A set
- of instantiation patterns within a particular semantic annotation.
-
- __<a name="pattern">Instantiation Pattern</a>:__ An XML-based
- specification of a mapping from portions of a resource to instances
- of an ontology.
-
- __<a name="prefix">Prefix Label</a>:__ A label used to
- represent an ontology location.
-
- __<a name="variable">Resource Variable</a>:__ An attribute of a
- resource, which in an annotation template takes the form 'R.x' (or
- more generally a path expression 'R.x1.x2...xn' for nested
- relations).
-
- __<a name="context">Iteration Context</a>:__ The set of
- resource variables, or current variable bindings (as the pattern is
- being executed), for a property or condition in an instantiation
- pattern. The iteration context is determined by the enclosing
- {{foreach}} expression of the item in question.
-
- __<a name="label">Pattern Label</a>:__ A label assigned to a
- template instantiation pattern.
-
- __<a name="reference">Pattern Reference</a>:__ A reference to a
- template instantiation pattern (using a pattern label) from within
- an object property in another (or possibly the same) pattern.
+ ;Resource: A structured information source with a defined schema. Can be a dataset or a service, such as a workflow, actor, or web-service.
+
+ ;Ontology: Here, by ontology we mean an OWL-based representation of a set of concepts, properties, and constraints (axioms).
+
+ ;Semantic Annotation Template: A set of instantiation patterns within a particular semantic annotation.
+
+ ;Instantiation Pattern: An XML-based specification of a mapping from portions of a resource to instances of an ontology.
+
+ ;Prefix Label: A label used to represent an ontology location.
+
+ ;Resource Variable: An attribute of a resource, which in an annotation template takes the form 'R.x' (or more generally a path expression 'R.x1.x2...xn' for nested relations).
+
+ ;Iteration Context: The set of resource variables, or current variable bindings (as the pattern is being executed), for a property or condition in an instantiation pattern. The iteration context is determined by the enclosing {{foreach}} expression of the item in question.
+
+ ;Pattern Label: A label assigned to a template instantiation pattern.
+
+ ;Pattern Reference: A reference to a template instantiation pattern (using a pattern label) from within an object property in another (or possibly the same) pattern.
+
+
+ !!!Footnotes
+
+ [#1] In OWL, instances of classes are called 'individuals.'
+
+ [#2] Alternatively, we could use anonymous identifiers for generated OWL individuals. However, using explicit as opposed to anonymous identifiers has a number of advantages, e.g., identifiers can be used for "provenance" (that is, using conventions for identifier names one could go from the created OWL individuals back to the resource item used to generte the resource), and also make it easier to formalize the interpretation of patterns in first-order logic.
+
+ [#3] The examples of resources in this document are assumed to be relational data sets. However, the approach described here can be used with a variety of resource structures, including nested relational data (e.g., like in XML).
At line 726 added 1 line.
+ [#4] By default, variables in {{foreach}} expressions that are null in the resource do not generate corresponding ontology class instances.
At line 727 added 1 line.
+ [#5] We use the notation {{(Axy)}} for universal quantification over variables {{x}} and {{y}}; {{(Exy)}} for existential quantification over variables {{x}} and {{y}}; and {{->}} for implication.
Lines 729-763 were replaced by line 715
- <a name="footnotes"></a> <h2>Footnotes</h2>
-
- <a name="1">[1]</a> In OWL, instances of classes are called
- 'individuals.'
-
- <a name="2">[2]</a> Alternatively, we could use anonymous
- identifiers for generated OWL individuals. However, using explicit
- as opposed to anonymous identifiers has a number of advantages,
- e.g., identifiers can be used for "provenance" (that is, using
- conventions for identifier names one could go from the created OWL
- individuals back to the resource item used to generte the resource),
- and also make it easier to formalize the interpretation of patterns
- in first-order logic.
-
- <a name="2">[3]</a> The examples of resources in this document are
- assumed to be relational data sets. However, the approach described
- here can be used with a variety of resource structures, including
- nested relational data (e.g., like in XML).
-
- <a name="3">[4]</a> By default, variables in {{foreach}}
- expressions that are null in the resource do not generate
- corresponding ontology class instances.
-
- <a name="5">[5]</a> We use the notation {{(Axy)}} for
- universal quantification over variables {{x}} and
- {{y}}; {{(Exy)}} for existential quantification
- over variables {{x}} and {{y}}; and
- {{->}} for implication.
-
- <a name="6">[6]</a> Note that the use of {{property}}
- expressions in this way is useful for cases in which the property is
- either (i) not defined (or optional) in the ontology for the
- associated class, or (ii) is a required property, but the
- {{valuetype}} expression gives a subclass of the property's
- defined range.
+ [#6] Note that the use of {{property}} expressions in this way is useful for cases in which the property is either (i) not defined (or optional) in the ontology for the associated class, or (ii) is a required property, but the {{valuetype}} expression gives a subclass of the property's defined range.

Back to KRSMS Semantic Annotation Language, or to the Page History.