<?xml version="1.0" encoding="utf-8" ?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
  xmlns:dc="http://purl.org/dc/elements/1.1/"
  xmlns:xml="http://www.w3.org/XML/1998/namespace"
  xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
  targetNamespace="http://purl.org/dc/elements/1.1/"
  elementFormDefault="qualified">
  <xs:import namespace="http://www.w3.org/XML/1998/namespace" schemaLocation="xml.xsd"/>
  <xs:import namespace="http://www.w3.org/1999/02/22-rdf-syntax-ns#" schemaLocation="rss10rdf.xsd"/>
  <xs:annotation>
    <xs:documentation>
      RDF Dublin Core module
    </xs:documentation>
  </xs:annotation>
<!--
Element: Title

  Name:        Title
  Identifier:  Title
  Definition:  A name given to the resource.
  Comment:     Typically, a Title will be a name by which the resource is
               formally known.

Element: Creator

  Name:        Creator
  Identifier:  Creator
  Definition:  An entity primarily responsible for making the content of
               the resource.
  Comment:     Examples of a Creator include a person, an organisation,
               or a service.
               Typically, the name of a Creator should be used to
               indicate the entity.

Element: Subject

  Name:        Subject and Keywords
  Identifier:  Subject
  Definition:  The topic of the content of the resource.
  Comment:     Typically, a 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.

Element: Description

  Name:        Description
  Identifier:  Description
  Definition:  An account of the content of the resource.
  Comment:     Description may include but is not limited to: an abstract,
               table of contents, reference to a graphical representation
               of content or a free-text account of the content.

Element: Publisher

  Name:        Publisher
  Identifier:  Publisher
  Definition:  An entity responsible for making the resource available
  Comment:     Examples of a Publisher include a person, an organisation,
               or a service.
               Typically, the name of a Publisher should be used to
               indicate the entity.

Element: Contributor

  Name:        Contributor
  Identifier:  Contributor
  Definition:  An entity responsible for making contributions to the
               content of the resource.
  Comment:     Examples of a Contributor include a person, an organisation,
               or a service.
               Typically, the name of a Contributor should be used to
               indicate the entity.

Element: Date

  Name:        Date
  Identifier:  Date
  Definition:  A date associated with an event in the life cycle of the
               resource.
  Comment:     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 [W3CDTF] and follows the YYYY-MM-DD format.
Element: Type

  Name:        Resource Type 
  Identifier:  Type
  Definition:  The nature or genre of the content of the resource.
  Comment:     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 working draft list of Dublin Core Types 
               [DCT1]). To describe the physical or digital manifestation
               of the resource, use the FORMAT element.

Element: Format

  Name:        Format
  Identifier:  Format
  Definition:  The physical or digital manifestation of the resource.
  Comment:     Typically, Format may include the media-type or dimensions of
               the resource. Format may be used to determine 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 [MIME] defining computer media formats).

Element: Identifier

  Name:        Resource Identifier
  Identifier:  Identifier
  Definition:  An unambiguous reference to the resource within a given context.
  Comment:     Recommended best practice is to identify the resource by means
               of a string or number conforming to a formal identification
               system. 
               Example formal identification systems include the Uniform
               Resource Identifier (URI) (including the Uniform Resource
               Locator (URL)), the Digital Object Identifier (DOI) and the
               International Standard Book Number (ISBN).

Element: Source

  Name:        Source
  Identifier:  Source
  Definition:  A Reference to a resource from which the present resource
               is derived.
  Comment:     The present resource may be derived from the Source resource
               in whole or in part.  Recommended best practice is to reference 
               the resource by means of a string or number conforming to a 
               formal identification system.

Element: Language

  Name:        Language
  Identifier:  Language
  Definition:  A language of the intellectual content of the resource.
  Comment:     Recommended best practice for the values of the Language
               element is defined by RFC 1766 [RFC1766] which includes
               a two-letter Language Code (taken from the ISO 639
               standard [ISO639]), followed optionally, by a two-letter
               Country Code (taken from the ISO 3166 standard [ISO3166]). 
               For example, 'en' for English, 'fr' for French, or
               'en-uk' for English used in the United Kingdom.

Element: Relation

  Name:        Relation
  Identifier:  Relation
  Definition:  A reference to a related resource.
  Comment:     Recommended best practice is to reference the resource by means
               of a string or number conforming to a formal identification
               system.

Element: Coverage

  Name:        Coverage
  Identifier:  Coverage
  Definition:  The extent or scope of the content of the resource.
  Comment:     Coverage will typically 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 that, where appropriate, named places or time
               periods be used in preference to numeric identifiers such as
               sets of coordinates or date ranges.

Element: Rights

  Name:       Rights Management   
  Identifier: Rights
  Definition: Information about rights held in and over the resource.
  Comment:    Typically, a Rights element 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 can be made
              about the status of these and other rights with respect to
              the resource.
 
 -->

  <xs:element name="dublinCoreExtension">
    <xs:complexType>
      <xs:sequence>
        <xs:element ref="dc:title" />
        <xs:element ref="dc:creator"/>
        <xs:element ref="dc:subject" maxOccurs="unbounded"/>
        <xs:element ref="dc:description" />
        <xs:element ref="dc:publisher" />
        <xs:element ref="dc:contributor" maxOccurs="unbounded" />
        <xs:element ref="dc:date" />
        <xs:element ref="dc:type" />
        <xs:element ref="dc:format" />
        <xs:element ref="dc:identifier" />
        <xs:element ref="dc:source" />
        <xs:element ref="dc:language" />
        <xs:element ref="dc:relation" />
        <xs:element ref="dc:coverage" />
        <xs:element ref="dc:rights" />
      </xs:sequence>
    </xs:complexType>
  </xs:element>

  <xs:complexType name="dcType" >
    <xs:simpleContent>
      <xs:extension base="xs:string" >
        <xs:attributeGroup ref="dc:dcAttr" />
      </xs:extension>
    </xs:simpleContent>
  </xs:complexType>

  <xs:attributeGroup name="dcAttr">
    <xs:attribute ref="xml:lang" />
    <xs:attribute ref="rdf:about" />
  </xs:attributeGroup>
  <xs:element name="title" type="dc:dcType">
    <xs:annotation>
      <xs:documentation>A name given to the resource. Typically, a Title will be a name by which the resource is
               formally known.</xs:documentation>
    </xs:annotation>
    
  </xs:element>
  <xs:element name="creator"  type="dc:dcType">
    <xs:annotation>
      <xs:documentation>An entity primarily responsible for making the content of
               the resource. Examples of a Creator include a person, an organisation,
               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:dcType">
    <xs:annotation>
      <xs:documentation> The topic of the content of the resource.
          Typically, a 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:dcType">
    <xs:annotation>
      <xs:documentation>An account of the content of the resource.
          Description may include but is not limited to: an abstract,
               table of contents, reference to a graphical representation
               of content or a free-text account of the content.</xs:documentation>
    </xs:annotation>

  </xs:element>
  
  <xs:element name="publisher"  type="dc:dcType">
    <xs:annotation>
      <xs:documentation>  Definition:  An entity responsible for making the resource available
      Examples of a Publisher include a person, an organisation, 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:dcType">
    <xs:annotation>
      <xs:documentation>An entity responsible for making contributions to the
               content of the resource. Examples of a Contributor include a person, an organisation,
               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:dcType">
    <xs:annotation>
      <xs:documentation>A date associated with an event in the life cycle 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 [W3CDTF] and follows the YYYY-MM-DD format.</xs:documentation>
    </xs:annotation>
      
  </xs:element>
  <xs:element name="type"  type="dc:dcType">
    <xs:annotation>
      <xs:documentation>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 working draft list of Dublin Core Types 
               [DCT1]). 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:dcType">
    <xs:annotation>
      <xs:documentation>
      The physical or digital manifestation of the resource.
      Typically, Format may include the media-type or dimensions of
               the resource. Format may be used to determine 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 [MIME] defining computer media formats).</xs:documentation>
    </xs:annotation>
      
  </xs:element>
  <xs:element name="identifier"  type="dc:dcType">
    <xs:annotation>
      <xs:documentation>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. 
               Example formal identification systems include 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:dcType">
    <xs:annotation>
      <xs:documentation>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 reference 
               the 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:dcType">
    <xs:annotation>
      <xs:documentation>
      A language of the intellectual content of the resource.
      Recommended best practice for the values of the Language
               element is defined by RFC 1766 [RFC1766] which includes
               a two-letter Language Code (taken from the ISO 639
               standard [ISO639]), followed optionally, by a two-letter
               Country Code (taken from the ISO 3166 standard [ISO3166]). 
               For example, 'en' for English, 'fr' for French, or
               'en-uk' for English used in the United Kingdom.</xs:documentation>
    </xs:annotation>

  </xs:element>
  <xs:element name="relation"  type="dc:dcType">
    <xs:annotation>
      <xs:documentation>A reference to a related resource. Recommended best practice is to reference the 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:dcType">
    <xs:annotation>
      <xs:documentation>The extent or scope of the content of the resource.
      Coverage will typically 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 that, where appropriate, named places or time
               periods be used 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:dcType">
    <xs:annotation>
      <xs:documentation>
      Information about rights held in and over the resource.
      Typically, a Rights element 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 can be made
              about the status of these and other rights with respect to
              the resource.</xs:documentation>
    </xs:annotation>

  </xs:element>
  

</xs:schema>