|
Difference between
version 36
and
version 35:
| Line 27 was replaced by line 27 |
| - A semantic type is required to have a unique identifier, given using the {{ID}} attribute. The identifier should (preferably) be represented as an LSID, and the semantic type as LSID data. |
| + A semantic type is required to have a unique identifier, given using the {{ID}} attribute. The identifier should (preferably) be represented as an LSID, and the semantic type managed as an LSID data object. |
| Line 31 was replaced by line 31 |
| - 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. |
| + Labels within semantic-type descriptions provide a mechanism to name the resources and ontology terms used in the annotations. 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 the associated identifier for a resource). Each {{Label}} tag is required to have exactly one {{name}} and {{resource}} attribute. A {{SemanticType}} element must have at least one {{Label}} sub-element identifying a resource and one {{Label}} element identifying an ontology term. Further, no two {{Label}} elements within a semantic type may have the same value for the {{name}} attribute. |
| At line 34 added 1 line. |
| + An annotation asserts that a resource object has a particular semantic meaning. |
Back to KRSMS Semantic Annotation Language,
or to the Page History.
|
