|
Difference between
version 29
and
version 28:
| Line 15 was replaced by line 15 |
| - <sms:Label name="..." object="..."/> |
| + <sms:Label name="..." resource="..."/> |
| Line 30 was replaced by line 30 |
| - Labels within semantic-type descriptions provide a mechanism to name certain resource and ontology items (objects). The {{Label}} element assigns the {{name}} attribute value as the name, or tag, for the value in the {{object}} attribute value. A label name is used within an annotation, and serves as a shorthand representation for the object in question. Each {{Label}} tag is required to have exactly one {{name}} and {{object}} attribute. A {{SemanticType}} element may have zero or more {{Label}} sub-elements, and no two {{Label}} tags within a semantic type may have the same value for the {{name}} attribute. |
| + Labels within semantic-type descriptions provide a mechanism to name certain resources and ontology terms. The {{Label}} element assigns the {{name}} attribute value as the name, or "tag" for the associated resource given by the {{resource}} attribute value (this attribute value is an identifier for a resource). A label name is used within an annotation to describe a resource. Each {{Label}} tag is required to have exactly one {{name}} and {{object}} attribute. A {{SemanticType}} element must have at least one {{Label}} sub-element. Further, no two {{Label}} elements within a semantic type may have the same value for the {{name}} attribute. |
| Removed line 34 |
| - Encodings define the "glue" or "links" between the resource(s) and the semantic type(s) and are optional. An encoding takes the form: |
| Lines 36-38 were replaced by lines 35-38 |
| - {{ |
| - <sms:Link> ... </sms:Link> |
| - }} |
| + * 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 :) |
| Removed lines 40-44 |
| - The content of the {{Link}} element uses a specific textual language that we define briefly here. |
| - |
| - |
| - |
| - |
Back to KRSMS Semantic Annotation Language,
or to the Page History.
|
