geonode-pycsw 3.0.0b2__py3-none-any.whl

pycsw/core/schemas/ogc/csw/2.0.2/CSW-publication.xsd

@@ -0,0 +1,242 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<xsd:schema id="csw-publication"
+   targetNamespace="http://www.opengis.net/cat/csw/2.0.2"
+   xmlns:csw="http://www.opengis.net/cat/csw/2.0.2"
+   xmlns:ogc="http://www.opengis.net/ogc"
+   xmlns:xsd="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified"
+   version="2.0.2 2010-01-22">
+   <xsd:annotation>
+      <xsd:appinfo>
+         <dc:identifier xmlns:dc="http://purl.org/dc/elements/1.1/">http://schemas.opengis.net/csw/2.0.2/CSW-publication.xsd</dc:identifier>
+      </xsd:appinfo>
+      <xsd:documentation xml:lang="en">
+         This schema defines the request and response messages for the 
+         CSW-Publication operations specified in clause 10 of OGC-07-066.
+         
+         CSW is an OGC Standard.
+         Copyright (c) 2004, 2010 Open Geospatial Consortium, Inc. All Rights Reserved.
+         To obtain additional rights of use, visit http://www.opengeospatial.org/legal/ .
+      </xsd:documentation>
+   </xsd:annotation>
+   <xsd:include schemaLocation="CSW-discovery.xsd"/>
+   <xsd:element name="Transaction" type="csw:TransactionType" id="Transaction"/>
+   <xsd:complexType name="TransactionType" id="TransactionType">
+      <xsd:annotation>
+         <xsd:documentation xml:lang="en">
+            Users may insert, update, or delete catalogue entries. If the 
+            verboseResponse attribute has the value "true", then one or more 
+            csw:InsertResult elements must be included in the response.
+         </xsd:documentation>
+      </xsd:annotation>
+      <xsd:complexContent>
+         <xsd:extension base="csw:RequestBaseType">
+            <xsd:sequence>
+               <xsd:choice minOccurs="1" maxOccurs="unbounded">
+                  <xsd:element name="Insert" type="csw:InsertType"/>
+                  <xsd:element name="Update" type="csw:UpdateType"/>
+                  <xsd:element name="Delete" type="csw:DeleteType"/>
+               </xsd:choice>
+            </xsd:sequence>
+            <xsd:attribute name="verboseResponse" type="xsd:boolean"
+               use="optional" default="false"/>
+            <xsd:attribute name="requestId" type="xsd:anyURI" use="optional"/>
+         </xsd:extension>
+      </xsd:complexContent>
+   </xsd:complexType>
+   <xsd:complexType name="InsertType" id="InsertType">
+      <xsd:annotation>
+         <xsd:documentation xml:lang="en">
+            Submits one or more records to the catalogue. The representation
+            is defined by the application profile. The handle attribute
+            may be included to specify a local identifier for the action 
+            (it must be unique within the context of the transaction).
+         </xsd:documentation>
+      </xsd:annotation>
+      <xsd:sequence>
+         <xsd:any processContents="strict" namespace="##other"
+            maxOccurs="unbounded"/>
+      </xsd:sequence>
+      <xsd:attribute name="typeName" type="xsd:anyURI" use="optional"/>
+      <xsd:attribute name="handle" type="xsd:ID" use="optional"/>
+   </xsd:complexType>
+   <xsd:complexType name="UpdateType" id="UpdateType">
+      <xsd:annotation>
+         <xsd:documentation xml:lang="en">
+            Update statements may replace an entire record or only update part 
+            of a record:
+            1) To replace an existing record, include a new instance of the 
+               record;
+            2) To update selected properties of an existing record, include
+               a set of RecordProperty elements. The scope of the update
+               statement  is determined by the Constraint element.
+               The 'handle' is a local identifier for the action.
+         </xsd:documentation>
+      </xsd:annotation>
+      <xsd:sequence>
+         <xsd:choice>
+            <xsd:any processContents="strict" namespace="##other"/>
+            <xsd:sequence>
+               <xsd:element ref="csw:RecordProperty" maxOccurs="unbounded"/>
+               <xsd:element ref="csw:Constraint"/>
+            </xsd:sequence>
+         </xsd:choice>
+      </xsd:sequence>
+      <xsd:attribute name="handle" type="xsd:ID" use="optional"/>
+   </xsd:complexType>
+   <xsd:complexType name="DeleteType" id="DeleteType">
+      <xsd:annotation>
+         <xsd:documentation xml:lang="en">
+            Deletes one or more catalogue items that satisfy some set of 
+            conditions.
+         </xsd:documentation>
+      </xsd:annotation>
+      <xsd:sequence>
+         <xsd:element ref="csw:Constraint" minOccurs="1" maxOccurs="1"/>
+      </xsd:sequence>
+      <xsd:attribute name="typeName" type="xsd:anyURI" use="optional"/>
+      <xsd:attribute name="handle" type="xsd:ID" use="optional"/>
+   </xsd:complexType>
+   <xsd:element name="RecordProperty" type="csw:RecordPropertyType">
+      <xsd:annotation>
+         <xsd:documentation>
+            The RecordProperty element is used to specify the new
+            value of a record property in an update statement.
+         </xsd:documentation>
+      </xsd:annotation>
+   </xsd:element>
+   <xsd:complexType name="RecordPropertyType">
+      <xsd:sequence>
+         <xsd:element name="Name" type="xsd:string">
+            <xsd:annotation>
+               <xsd:documentation>
+                  The Name element contains the name of a property
+                  to be updated.  The name may be a path expression.
+               </xsd:documentation>
+            </xsd:annotation>
+         </xsd:element>
+         <xsd:element name="Value" type="xsd:anyType" minOccurs="0">
+            <xsd:annotation>
+               <xsd:documentation>
+                  The Value element contains the replacement value for the
+                  named property.
+               </xsd:documentation>
+            </xsd:annotation>
+         </xsd:element>
+      </xsd:sequence>
+   </xsd:complexType>
+   <xsd:element name="TransactionResponse" type="csw:TransactionResponseType"
+      id="TransactionResponse"/>
+   <xsd:complexType name="TransactionResponseType">
+      <xsd:annotation>
+         <xsd:documentation xml:lang="en">
+            The response for a transaction request that was successfully
+            completed. If the transaction failed for any reason, a service 
+            exception report indicating a TransactionFailure is returned
+            instead.
+         </xsd:documentation>
+      </xsd:annotation>
+      <xsd:sequence>
+         <xsd:element name="TransactionSummary"
+            type="csw:TransactionSummaryType"/>
+         <xsd:element name="InsertResult" type="csw:InsertResultType"
+            minOccurs="0" maxOccurs="unbounded"/>
+      </xsd:sequence>
+      <xsd:attribute name="version" type="xsd:string" use="optional"/>
+   </xsd:complexType>
+   <xsd:complexType name="TransactionSummaryType" id="TransactionSummaryType">
+      <xsd:annotation>
+         <xsd:documentation xml:lang="en">
+         Reports the total number of catalogue items modified by a transaction 
+         request (i.e, inserted, updated, deleted). If the client did not 
+         specify a requestId, the server may assign one (a URI value).
+         </xsd:documentation>
+      </xsd:annotation>
+      <xsd:sequence>
+         <xsd:element name="totalInserted" type="xsd:nonNegativeInteger"
+            minOccurs="0"/>
+         <xsd:element name="totalUpdated" type="xsd:nonNegativeInteger"
+            minOccurs="0"/>
+         <xsd:element name="totalDeleted" type="xsd:nonNegativeInteger"
+            minOccurs="0"/>
+      </xsd:sequence>
+      <xsd:attribute name="requestId" type="xsd:anyURI" use="optional"/>
+   </xsd:complexType>
+   <xsd:complexType name="InsertResultType" id="InsertResultType">
+      <xsd:annotation>
+         <xsd:documentation xml:lang="en">
+            Returns a "brief" view of any newly created catalogue records.
+            The handle attribute may reference a particular statement in
+            the corresponding transaction request.
+         </xsd:documentation>
+      </xsd:annotation>
+      <xsd:sequence>
+         <xsd:element ref="csw:BriefRecord" maxOccurs="unbounded"/>
+      </xsd:sequence>
+      <xsd:attribute name="handleRef" type="xsd:anyURI" use="optional"/>
+   </xsd:complexType>
+   <xsd:element name="Harvest" type="csw:HarvestType" id="Harvest"/>
+   <xsd:complexType name="HarvestType">
+      <xsd:annotation>
+         <xsd:documentation xml:lang="en">
+         Requests that the catalogue attempt to harvest a resource from some 
+         network location identified by the source URL.
+
+         Source          - a URL from which the resource is retrieved
+         ResourceType    - normally a URI that specifies the type of the resource
+                           (DCMES v1.1) being harvested if it is known.
+         ResourceFormat  - a media type indicating the format of the 
+                           resource being harvested.  The default is 
+                           "application/xml".
+         ResponseHandler - a reference to some endpoint to which the 
+                           response shall be forwarded when the
+                           harvest operation has been completed
+         HarvestInterval - an interval expressed using the ISO 8601 syntax; 
+                           it specifies the interval between harvest 
+                           attempts (e.g., P6M indicates an interval of 
+                           six months).
+         </xsd:documentation>
+      </xsd:annotation>
+      <xsd:complexContent>
+         <xsd:extension base="csw:RequestBaseType">
+            <xsd:sequence>
+               <xsd:element name="Source" type="xsd:anyURI"/>
+               <xsd:element name="ResourceType" type="xsd:string"/>
+               <xsd:element name="ResourceFormat" type="xsd:string"
+                  minOccurs="0" default="application/xml"/>
+               <xsd:element name="HarvestInterval" type="xsd:duration"
+                  minOccurs="0"/>
+               <xsd:element name="ResponseHandler" type="xsd:anyURI"
+                  minOccurs="0" maxOccurs="unbounded"/>
+            </xsd:sequence>
+         </xsd:extension>
+      </xsd:complexContent>
+   </xsd:complexType>
+   <xsd:element name="HarvestResponse" type="csw:HarvestResponseType"
+      id="HarvestResponse">
+      <xsd:annotation>
+         <xsd:documentation xml:lang="en">
+         The content of the response varies depending on the presence of the 
+         ResponseHandler element. If present, then the catalogue should 
+         verify the request and respond immediately with an csw:Acknowledgement 
+         element in the response. The catalogue must then attempt to harvest 
+         the resource at some later time and send the response message to the 
+         location specified by the value of the ResponseHandler element using 
+         the indicated protocol (e.g. ftp, mailto, http).
+         
+         If the ResponseHandler element is absent, then the catalogue 
+         must attempt to harvest the resource immediately and include a 
+         TransactionResponse element in the response.
+        
+         In any case, if the harvest attempt is successful the response 
+         shall include summary representations of the newly created 
+         catalogue item(s).
+         </xsd:documentation>
+      </xsd:annotation>
+   </xsd:element>
+   <xsd:complexType name="HarvestResponseType" id="HarvestResponseType">
+      <xsd:choice>
+         <xsd:element ref="csw:Acknowledgement"/>
+         <xsd:element ref="csw:TransactionResponse"/>
+      </xsd:choice>
+   </xsd:complexType>
+</xsd:schema>

pycsw/core/schemas/ogc/csw/2.0.2/rec-dcmes.xsd

@@ -0,0 +1,199 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<xs:schema id="dcmes" targetNamespace="http://purl.org/dc/elements/1.1/"
+   xmlns:xs="http://www.w3.org/2001/XMLSchema"
+   xmlns:dc="http://purl.org/dc/elements/1.1/" elementFormDefault="qualified"
+   attributeFormDefault="unqualified" version="2.0.2">
+   <xs:annotation>
+      <xs:documentation xml:lang="en"
+         source="http://dublincore.org/documents/dces/">This schema declares XML elements for the 15 Dublin Core elements in 
+    the "http://purl.org/dc/elements/1.1/" namespace.</xs:documentation>
+   </xs:annotation>
+   <xs:complexType name="SimpleLiteral">
+      <xs:annotation>
+         <xs:documentation xml:lang="en">This is the default type for all of the DC elements. It defines a 
+      complexType SimpleLiteral which permits mixed content but disallows 
+      child elements by use of minOcccurs/maxOccurs. However, this complexType 
+      does permit the derivation of other types which would permit child 
+      elements. The scheme attribute may be used as a qualifier to reference 
+      an encoding scheme that describes the value domain for a given property.</xs:documentation>
+      </xs:annotation>
+      <xs:complexContent mixed="true">
+         <xs:restriction base="xs:anyType">
+            <xs:sequence>
+               <xs:any processContents="lax" minOccurs="0" maxOccurs="0"/>
+            </xs:sequence>
+            <xs:attribute name="scheme" type="xs:anyURI" use="optional"/>
+         </xs:restriction>
+      </xs:complexContent>
+   </xs:complexType>
+   <xs:element name="DC-element" type="dc:SimpleLiteral" abstract="true"/>
+   <xs:element name="title" type="dc:SimpleLiteral"
+      substitutionGroup="dc:DC-element">
+      <xs:annotation>
+         <xs:documentation xml:lang="en">A name given to the resource. Typically, Title will be a name by 
+      which the resource is formally known.</xs:documentation>
+      </xs:annotation>
+   </xs:element>
+   <xs:element name="creator" type="dc:SimpleLiteral"
+      substitutionGroup="dc:DC-element">
+      <xs:annotation>
+         <xs:documentation xml:lang="en">An entity primarily responsible for making the content of the resource.
+      Examples of Creator include a person, an organization, or a service. 
+      Typically, the name of a Creator should be used to indicate the entity.</xs:documentation>
+      </xs:annotation>
+   </xs:element>
+   <xs:element name="subject" type="dc:SimpleLiteral"
+      substitutionGroup="dc:DC-element">
+      <xs:annotation>
+         <xs:documentation xml:lang="en">A topic of the content of the resource. Typically, Subject will be 
+      expressed as keywords, key phrases, or classification codes that 
+      describe a topic of the resource. Recommended best practice is to 
+      select a value from a controlled vocabulary or formal classification 
+      scheme.</xs:documentation>
+      </xs:annotation>
+   </xs:element>
+   <xs:element name="description" type="dc:SimpleLiteral"
+      substitutionGroup="dc:DC-element">
+      <xs:annotation>
+         <xs:documentation xml:lang="en">An account of the content of the resource. Examples of Description 
+      include, but are not limited to, an abstract, table of contents, 
+      reference to a graphical representation of content, or free-text 
+      account of the content.</xs:documentation>
+      </xs:annotation>
+   </xs:element>
+   <xs:element name="publisher" type="dc:SimpleLiteral"
+      substitutionGroup="dc:DC-element">
+      <xs:annotation>
+         <xs:documentation xml:lang="en">An entity responsible for making the resource available. Examples of 
+      Publisher include a person, an organization, or a service. Typically, 
+      the name of a Publisher should be used to indicate the entity.</xs:documentation>
+      </xs:annotation>
+   </xs:element>
+   <xs:element name="contributor" type="dc:SimpleLiteral"
+      substitutionGroup="dc:DC-element">
+      <xs:annotation>
+         <xs:documentation xml:lang="en">An entity responsible for making contributions to the content of 
+      the resource. Examples of Contributor include a person, an organization, 
+      or a service. Typically, the name of a Contributor should be used to 
+      indicate the entity.</xs:documentation>
+      </xs:annotation>
+   </xs:element>
+   <xs:element name="date" type="dc:SimpleLiteral"
+      substitutionGroup="dc:DC-element">
+      <xs:annotation>
+         <xs:documentation xml:lang="en">A date of an event in the lifecycle of the resource. Typically, Date 
+      will be associated with the creation or availability of the resource. 
+      Recommended best practice for encoding the date value is defined in a 
+      profile of ISO 8601 and includes (among others) dates of the 
+      form YYYY-MM-DD.</xs:documentation>
+      </xs:annotation>
+   </xs:element>
+   <xs:element name="type" type="dc:SimpleLiteral"
+      substitutionGroup="dc:DC-element">
+      <xs:annotation>
+         <xs:documentation xml:lang="en">The nature or genre of the content of the resource. Type includes 
+      terms describing general categories, functions, genres, or aggregation 
+      levels for content. Recommended best practice is to select a value 
+      from a controlled vocabulary (for example, the DCMI Type Vocabulary). 
+      To describe the physical or digital manifestation of the resource, 
+      use the Format element.</xs:documentation>
+      </xs:annotation>
+   </xs:element>
+   <xs:element name="format" type="dc:SimpleLiteral"
+      substitutionGroup="dc:DC-element">
+      <xs:annotation>
+         <xs:documentation xml:lang="en">The physical or digital manifestation of the resource. Typically, 
+      Format will include the media-type or dimensions of the resource. 
+      Format may be used to identify the software, hardware, or other 
+      equipment needed to display or operate the resource. Examples of 
+      dimensions include size and duration. Recommended best practice is to 
+      select a value from a controlled vocabulary (for example, the list 
+      of Internet Media Types defining computer media formats).</xs:documentation>
+      </xs:annotation>
+   </xs:element>
+   <xs:element name="identifier" type="dc:SimpleLiteral"
+      substitutionGroup="dc:DC-element">
+      <xs:annotation>
+         <xs:documentation xml:lang="en">An unambiguous reference to the resource within a given context. 
+      Recommended best practice is to identify the resource by means of a 
+      string or number conforming to a formal identification system. Formal 
+      identification systems include but are not limited to the Uniform 
+      Resource Identifier (URI) (including the Uniform Resource Locator 
+      (URL)), the Digital Object Identifier (DOI), and the International 
+      Standard Book Number (ISBN).</xs:documentation>
+      </xs:annotation>
+   </xs:element>
+   <xs:element name="source" type="dc:SimpleLiteral"
+      substitutionGroup="dc:DC-element">
+      <xs:annotation>
+         <xs:documentation xml:lang="en">A Reference to a resource from which the present resource is derived.
+      The present resource may be derived from the Source resource in whole 
+      or in part. Recommended best practice is to identify the referenced 
+      resource by means of a string or number conforming to a formal 
+      identification system.</xs:documentation>
+      </xs:annotation>
+   </xs:element>
+   <xs:element name="language" type="dc:SimpleLiteral"
+      substitutionGroup="dc:DC-element">
+      <xs:annotation>
+         <xs:documentation xml:lang="en">A language of the intellectual content of the resource. Recommended 
+      best practice is to use RFC 3066, which, in conjunction with ISO 639, 
+      defines two- and three-letter primary language tags with optional 
+      subtags. Examples include "en" or "eng" for English, "akk" for
+      Akkadian, and "en-GB" for English used in the United Kingdom.</xs:documentation>
+      </xs:annotation>
+   </xs:element>
+   <xs:element name="relation" type="dc:SimpleLiteral"
+      substitutionGroup="dc:DC-element">
+      <xs:annotation>
+         <xs:documentation xml:lang="en">A reference to a related resource. Recommended best practice is to 
+      identify the referenced resource by means of a string or number 
+      conforming to a formal identification system.</xs:documentation>
+      </xs:annotation>
+   </xs:element>
+   <xs:element name="coverage" type="dc:SimpleLiteral"
+      substitutionGroup="dc:DC-element">
+      <xs:annotation>
+         <xs:documentation xml:lang="en">The extent or scope of the content of the resource. Typically, 
+      Coverage will include spatial location (a place name or geographic 
+      coordinates), temporal period (a period label, date, or date range), 
+      or jurisdiction (such as a named administrative entity). Recommended 
+      best practice is to select a value from a controlled vocabulary 
+      (for example, the Thesaurus of Geographic Names [TGN]) and to use, 
+      where appropriate, named places or time periods in preference to 
+      numeric identifiers such as sets of coordinates or date ranges.</xs:documentation>
+      </xs:annotation>
+   </xs:element>
+   <xs:element name="rights" type="dc:SimpleLiteral"
+      substitutionGroup="dc:DC-element">
+      <xs:annotation>
+         <xs:documentation xml:lang="en">Information about rights held in and over the resource. Typically, 
+      Rights will contain a rights management statement for the resource, 
+      or reference a service providing such information. Rights information 
+      often encompasses Intellectual Property Rights (IPR), Copyright, and 
+      various Property Rights. If the Rights element is absent, no 
+      assumptions may be made about any rights held in or over the resource.</xs:documentation>
+      </xs:annotation>
+   </xs:element>
+   <xs:group name="DC-element-set">
+      <xs:annotation>
+         <xs:documentation xml:lang="en">This group is included as a convenience for schema authors who need 
+      to refer to all the elements in the "http://purl.org/dc/elements/1.1/" 
+      namespace.</xs:documentation>
+      </xs:annotation>
+      <xs:sequence>
+         <xs:choice minOccurs="0" maxOccurs="unbounded">
+            <xs:element ref="dc:DC-element"/>
+         </xs:choice>
+      </xs:sequence>
+   </xs:group>
+   <xs:complexType name="elementContainer">
+      <xs:annotation>
+         <xs:documentation xml:lang="en">This type definition is included as a convenience for schema authors 
+      who need a container element for all of the DC elements.</xs:documentation>
+      </xs:annotation>
+      <xs:choice>
+         <xs:group ref="dc:DC-element-set"/>
+      </xs:choice>
+   </xs:complexType>
+</xs:schema>

pycsw/core/schemas/ogc/csw/2.0.2/rec-dcterms.xsd

@@ -0,0 +1,94 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<xs:schema id="dcmi-terms" targetNamespace="http://purl.org/dc/terms/"
+   xmlns:xs="http://www.w3.org/2001/XMLSchema"
+   xmlns:dct="http://purl.org/dc/terms/"
+   xmlns:dc="http://purl.org/dc/elements/1.1/" elementFormDefault="qualified"
+   attributeFormDefault="unqualified" version="2.0.2 2010-01-22">
+   <xs:annotation>
+      <xs:documentation xml:lang="en"
+         source="http://dublincore.org/documents/dcmi-terms/">This schema declares additional DCMI elements and element refinements 
+    in the "http://purl.org/dc/terms/" namespace.</xs:documentation>
+   </xs:annotation>
+   <xs:import namespace="http://purl.org/dc/elements/1.1/" schemaLocation="rec-dcmes.xsd"/>
+   <xs:element name="abstract" type="dc:SimpleLiteral"
+      substitutionGroup="dc:description"/>
+   <xs:element name="accessRights" type="dc:SimpleLiteral"
+      substitutionGroup="dc:rights"/>
+   <xs:element name="alternative" type="dc:SimpleLiteral"
+      substitutionGroup="dc:title"/>
+   <xs:element name="audience" type="dc:SimpleLiteral"
+      substitutionGroup="dc:DC-element"/>
+   <xs:element name="available" type="dc:SimpleLiteral"
+      substitutionGroup="dc:date"/>
+   <xs:element name="bibliographicCitation" type="dc:SimpleLiteral"
+      substitutionGroup="dc:identifier"/>
+   <xs:element name="conformsTo" type="dc:SimpleLiteral"
+      substitutionGroup="dc:relation"/>
+   <xs:element name="created" type="dc:SimpleLiteral"
+      substitutionGroup="dc:date"/>
+   <xs:element name="dateAccepted" type="dc:SimpleLiteral"
+      substitutionGroup="dc:date"/>
+   <xs:element name="dateCopyrighted" type="dc:SimpleLiteral"
+      substitutionGroup="dc:date"/>
+   <xs:element name="dateSubmitted" type="dc:SimpleLiteral"
+      substitutionGroup="dc:date"/>
+   <xs:element name="educationLevel" type="dc:SimpleLiteral"
+      substitutionGroup="dct:audience"/>
+   <xs:element name="extent" type="dc:SimpleLiteral"
+      substitutionGroup="dc:format"/>
+   <xs:element name="hasFormat" type="dc:SimpleLiteral"
+      substitutionGroup="dc:relation"/>
+   <xs:element name="hasPart" type="dc:SimpleLiteral"
+      substitutionGroup="dc:relation"/>
+   <xs:element name="hasVersion" type="dc:SimpleLiteral"
+      substitutionGroup="dc:relation"/>
+   <xs:element name="isFormatOf" type="dc:SimpleLiteral"
+      substitutionGroup="dc:relation"/>
+   <xs:element name="isPartOf" type="dc:SimpleLiteral"
+      substitutionGroup="dc:relation"/>
+   <xs:element name="isReferencedBy" type="dc:SimpleLiteral"
+      substitutionGroup="dc:relation"/>
+   <xs:element name="isReplacedBy" type="dc:SimpleLiteral"
+      substitutionGroup="dc:relation"/>
+   <xs:element name="isRequiredBy" type="dc:SimpleLiteral"
+      substitutionGroup="dc:relation"/>
+   <xs:element name="issued" type="dc:SimpleLiteral" substitutionGroup="dc:date"/>
+   <xs:element name="isVersionOf" type="dc:SimpleLiteral"
+      substitutionGroup="dc:relation"/>
+   <xs:element name="license" type="dc:SimpleLiteral"
+      substitutionGroup="dc:rights"/>
+   <xs:element name="mediator" type="dc:SimpleLiteral"
+      substitutionGroup="dct:audience"/>
+   <xs:element name="medium" type="dc:SimpleLiteral"
+      substitutionGroup="dc:format"/>
+   <xs:element name="modified" type="dc:SimpleLiteral"
+      substitutionGroup="dc:date"/>
+   <xs:element name="provenance" type="dc:SimpleLiteral"
+      substitutionGroup="dc:DC-element"/>
+   <xs:element name="references" type="dc:SimpleLiteral"
+      substitutionGroup="dc:relation"/>
+   <xs:element name="replaces" type="dc:SimpleLiteral"
+      substitutionGroup="dc:relation"/>
+   <xs:element name="requires" type="dc:SimpleLiteral"
+      substitutionGroup="dc:relation"/>
+   <xs:element name="rightsHolder" type="dc:SimpleLiteral"
+      substitutionGroup="dc:DC-element"/>
+   <xs:element name="spatial" type="dc:SimpleLiteral"
+      substitutionGroup="dc:coverage"/>
+   <xs:element name="tableOfContents" type="dc:SimpleLiteral"
+      substitutionGroup="dc:description"/>
+   <xs:element name="temporal" type="dc:SimpleLiteral"
+      substitutionGroup="dc:coverage"/>
+   <xs:element name="valid" type="dc:SimpleLiteral" substitutionGroup="dc:date"/>
+   <xs:group name="DCMI-terms">
+      <xs:annotation>
+         <xs:documentation xml:lang="en">This group is included as a convenience for schema authors who need 
+      to refer to the complete set of DCMI metadata terms.</xs:documentation>
+      </xs:annotation>
+      <xs:sequence>
+         <xs:choice minOccurs="0" maxOccurs="unbounded">
+            <xs:element ref="dc:DC-element"/>
+         </xs:choice>
+      </xs:sequence>
+   </xs:group>
+</xs:schema>