|
Difference between
version 87
and
version 86:
| At line 90 added 1 line. |
| + In this simple example, we (1) associate the label {{Crops}} to the data set resource, (2) associate five labels to corresponding ontology concepts, (3) state via the first annotation that each {{Crops}} tuple is a {{Measurement}}, (4) that each {{bm}} attribute value is a {{Biomass}, (5) that each {{spp}} attribute value is a {{Species}}, and so on. |
| Removed line 94 |
| - In addition, the label also represents the collection of |
| Removed line 96 |
| - denotes the set of corresponding objects satisfying the structural constraints of the resource. For example, if {{T}} is a label for a dataset, the expression {{T}} implicitly denotes the set of tuple objects in the corresponding dataset. Similarly, if {{T}} is a label for an actor, the expression{{T}} implicitly denotes an instance of that actor. |
| Removed lines 98-104 |
| - |
| - |
| - * How to give the annotation of a resource as a dl-style expression, preferably in the same language |
| - * Discuss/explain what a resource dentoes, e.g., is it a name that denotes a set of instances (e.g., a dataset/table name denotes a set of instances, where an instance is a row in the table). What about for actors? |
| - * Discuss/explain that the "structure" language is generic and can represent many data models (ptolemy types, relational, even xml). |
| - * Describe the language step-by step, without a grammar :) |
| - |
Back to KRSMS Semantic Annotation Language,
or to the Page History.
|
