mlhim-specs-dev team mailing list archive
-
mlhim-specs-dev team
-
Mailing list archive
-
Message #00163
[Branch ~mlhim-specs-dev/mlhim-specs/main] Rev 126: Working on Element documentation strings. Completed common.xsd Bug #771266
------------------------------------------------------------
revno: 126
committer: Timothy W. Cook <timothywayne.cook@xxxxxxxxx>
branch nick: mlhim-specs
timestamp: Sat 2011-04-30 07:19:51 -0500
message:
Working on Element documentation strings. Completed common.xsd Bug #771266
modified:
schemas/common.xsd
schemas/support.xsd
--
lp:mlhim-specs
https://code.launchpad.net/~mlhim-specs-dev/mlhim-specs/main
Your team MLHIM Specifications Developers is subscribed to branch lp:mlhim-specs.
To unsubscribe from this branch go to https://code.launchpad.net/~mlhim-specs-dev/mlhim-specs/main/+edit-subscription
=== modified file 'schemas/common.xsd'
--- schemas/common.xsd 2011-04-30 02:18:58 +0000
+++ schemas/common.xsd 2011-04-30 12:19:51 +0000
@@ -302,66 +302,66 @@
</xs:element>
<xs:element name="coverage" maxOccurs="1" minOccurs="0" type="xs:string">
- <xs:annotation><xs:documentation></xs:documentation></xs:annotation>
+ <xs:annotation><xs:documentation>The spatial or temporal topic of the resource, the spatial applicability of the resource, or the jurisdiction under which the resource is relevant. http://dublincore.org/documents/dcmi-terms/#terms-coverage </xs:documentation></xs:annotation>
</xs:element>
<xs:element name="license" maxOccurs="1" minOccurs="0" type="xs:string">
- <xs:annotation><xs:documentation></xs:documentation></xs:annotation>
+ <xs:annotation><xs:documentation>A legal document giving official permission to do something with the resource. http://dublincore.org/documents/dcmi-terms/#terms-license </xs:documentation></xs:annotation>
</xs:element>
<xs:element name="creator" maxOccurs="1" minOccurs="0" type="xs:string">
- <xs:annotation><xs:documentation></xs:documentation></xs:annotation>
+ <xs:annotation><xs:documentation>An entity primarily responsible for making the resource. Comment: Examples of a Creator include a person, an organization, or a service. http://dublincore.org/documents/dcmi-terms/#terms-creator </xs:documentation></xs:annotation>
</xs:element>
<xs:element name="created" maxOccurs="1" minOccurs="0" type="xs:string">
- <xs:annotation><xs:documentation></xs:documentation></xs:annotation>
+ <xs:annotation><xs:documentation>Date of creation of the resource. http://dublincore.org/documents/dcmi-terms/#terms-created </xs:documentation></xs:annotation>
</xs:element>
<xs:element name="dateCopyrighted" maxOccurs="1" minOccurs="0" type="xs:string">
- <xs:annotation><xs:documentation></xs:documentation></xs:annotation>
+ <xs:annotation><xs:documentation>Date of copyright. http://dublincore.org/documents/dcmi-terms/#terms-dateCopyrighted </xs:documentation></xs:annotation>
</xs:element>
<xs:element name="identifier" maxOccurs="1" minOccurs="0" type="xs:string">
- <xs:annotation><xs:documentation></xs:documentation></xs:annotation>
+ <xs:annotation><xs:documentation>An unambiguous reference to the resource within a given context. Comment: Recommended best practice is to identify the resource by means of a string conforming to a formal identification system. Example: A CCD should be identified by a UUID version #4 as described in IETF RFC 4122. http://tools.ietf.org/html/rfc4122.html </xs:documentation></xs:annotation>
</xs:element>
<xs:element name="issued" maxOccurs="1" minOccurs="0" type="xs:string">
- <xs:annotation><xs:documentation></xs:documentation></xs:annotation>
+ <xs:annotation><xs:documentation>Date of formal issuance (e.g., publication) of the resource. </xs:documentation></xs:annotation>
</xs:element>
<xs:element name="relation" maxOccurs="1" minOccurs="0" type="xs:string">
- <xs:annotation><xs:documentation></xs:documentation></xs:annotation>
+ <xs:annotation><xs:documentation>A related resource. Comment: Recommended best practice is to identify the related resource by means of a string conforming to a formal identification system. In the case of CCDs the relationship text should come from the UMLS semantic network. </xs:documentation></xs:annotation>
</xs:element>
<xs:element name="replaces" maxOccurs="1" minOccurs="0" type="xs:string">
- <xs:annotation><xs:documentation></xs:documentation></xs:annotation>
+ <xs:annotation><xs:documentation>A related resource that is supplanted, displaced, or superseded by the described resource. In the case of CCDs this is the 'identifier' of the replaced CCD. </xs:documentation></xs:annotation>
</xs:element>
<xs:element name="rights" maxOccurs="1" minOccurs="0" type="xs:string">
- <xs:annotation><xs:documentation></xs:documentation></xs:annotation>
+ <xs:annotation><xs:documentation>Information about rights held in and over the resource. Comment: Typically, rights information includes a statement about various property rights associated with the resource, including intellectual property rights.</xs:documentation></xs:annotation>
</xs:element>
<xs:element name="rightsHolder" maxOccurs="1" minOccurs="0" type="xs:string">
- <xs:annotation><xs:documentation></xs:documentation></xs:annotation>
+ <xs:annotation><xs:documentation>A person or organization owning or managing rights over the resource. </xs:documentation></xs:annotation>
</xs:element>
<xs:element name="source" maxOccurs="1" minOccurs="0" type="xs:string">
- <xs:annotation><xs:documentation></xs:documentation></xs:annotation>
+ <xs:annotation><xs:documentation>A related resource from which the described resource is derived. Comment: The described resource may be derived from the related resource in whole or in part. Recommended best practice is to identify the related resource by means of a string conforming to a formal identification system. </xs:documentation></xs:annotation>
</xs:element>
<xs:element name="subject" maxOccurs="1" minOccurs="0" type="xs:string">
- <xs:annotation><xs:documentation></xs:documentation></xs:annotation>
+ <xs:annotation><xs:documentation>The topic of the resource. Comment: Typically, the subject will be represented using keywords, key phrases, or classification codes. Recommended best practice is to use a controlled vocabulary. To describe the spatial or temporal topic of the resource, use the Coverage element. With CCDs this is a list of MeSH terms. </xs:documentation></xs:annotation>
</xs:element>
<xs:element name="title" maxOccurs="1" minOccurs="0" type="xs:string">
- <xs:annotation><xs:documentation></xs:documentation></xs:annotation>
+ <xs:annotation><xs:documentation>A descriptive name given to the resource. In CCDs possibly derived from the UMLS semantic network</xs:documentation></xs:annotation>
</xs:element>
</xs:sequence>
=== modified file 'schemas/support.xsd'
--- schemas/support.xsd 2011-04-30 02:18:58 +0000
+++ schemas/support.xsd 2011-04-30 12:19:51 +0000
@@ -42,7 +42,7 @@
<xs:complexType name="NA">
<xs:annotation>
<xs:documentation>
- No proper value is applicable in this context e.g., last menstrual period fora male.
+ No proper value is applicable in this context e.g.,the number of cigarrettes smoked per day by a non-smoker subject.
</xs:documentation>
</xs:annotation>
<xs:complexContent>