Skip to content
Permalink
Browse files

Changed `propertyURI` and label to optional.

Added documentation to indicate that, when propertyURI is not provided,
then the property defaults to dc:subject for resources and entities, and
to oboe:MeasurementType for attributes.
  • Loading branch information
mbjones committed Feb 24, 2018
1 parent de214f3 commit 733a650e43d4d31ca6ed04d71e1326687209a79b
Showing with 23 additions and 6 deletions.
  1. +5 −2 xsd/eml-attribute.xsd
  2. +6 −1 xsd/eml-entity.xsd
  3. +6 −1 xsd/eml-resource.xsd
  4. +6 −2 xsd/eml-semantics.xsd
@@ -775,9 +775,12 @@
of the statement is the eml:attribute that contains the
annotation. The propertyLabel and valueLabel can be used
to display the statement to users. Each URI is
typically resolvable to a controlled vocabulary that provides
resolvable to a controlled vocabulary that provides
a definition, relationships to other terms, and multiple
labels for displaying the statement.
labels for displaying the statement. The propertyURI and propertyLabel
fields are optional. When they are omitted for an attribute defniition,
then users should assume thatthe property being asserted is
<code>oboe:MeasurementType</code>.
</doc:description>
</xs:appinfo>
</xs:annotation>
@@ -295,9 +295,14 @@
entity. Each annotation consists of a propertyURI and valueURI,
which define a property and a value that apply to the entity.
The propertyLabel and valueLabel can be used to display the
value to users. Each URI is typically resolvable to a
value to users. Each URI is resolvable to a
controlled vocabulary that provides a definition, relationships
to other terms, and multiple labels for displaying the statement.
The propertyURI and propertyLabel fields are optional. When
they are omitted for an entity defniition,
then users should assume that the property being asserted is
from the Dublin Core Element Set vocabulary and represents the
<code>dc:subject</code> for the entity.
</doc:description>
</xs:appinfo>
</xs:annotation>
@@ -406,9 +406,14 @@
resource. The subject of the statement is implicitly the
eml:resource that contains the annotation. The propertyLabel
and valueLabel can be used to display the statement to users.
Each URI is typically resolvable to a controlled vocabulary
Each URI is resolvable to a controlled vocabulary
that provides a definition, relationships to other terms, and
multiple labels for displaying the statement.
The propertyURI and propertyLabel fields are optional. When
they are omitted for a resource,
then users should assume that the property being asserted is
from the Dublin Core Element Set vocabulary and represents the
<code>dc:subject</code> for the entity.
</doc:description>
</xs:appinfo>
</xs:annotation>
@@ -71,7 +71,7 @@
</xs:appinfo>
</xs:annotation>
<xs:sequence>
<xs:element name="propertyURI" type="xs:anyURI" minOccurs="1" maxOccurs="1">
<xs:element name="propertyURI" type="xs:anyURI" minOccurs="0" maxOccurs="1">
<xs:annotation>
<xs:appinfo>
<doc:tooltip>Property URI</doc:tooltip>
@@ -80,13 +80,17 @@
<doc:description>The URI for a property that is drawn from a controlled
vocabulary, and that links the subject of this annotation
(which is implied by its parent elements) to the annotation value.
The propertyURI represents a semantically well-defined concept
that one wants to apply to an element within EML. The propertyURI
and its associated label are optional. If omitted, then the interpretation
of the associated valueURI depends on where the annotation occurs.
</doc:description>
<doc:example>http://ecoinformatics.org/oboe/oboe.1.2/oboe-characteristics.owl#ofCharacteristic</doc:example>
<doc:example>http://ecoinformatics.org/oboe/oboe.1.2/oboe-standards.owl#usesStandard</doc:example>
</xs:appinfo>
</xs:annotation>
</xs:element>
<xs:element name="propertyLabel" minOccurs="1" maxOccurs="1">
<xs:element name="propertyLabel" minOccurs="0" maxOccurs="1">
<xs:annotation>
<xs:appinfo>
<doc:tooltip>Property Label</doc:tooltip>

0 comments on commit 733a650

Please sign in to comment.
You can’t perform that action at this time.