Showing:

Annotations
Attributes
Diagrams
Instances
Properties
Source
Used by
Imported schema DDMS-v3_0.xsd
Namespace http://metadata.dod.mil/mdr/ns/DDMS/3.0/
Annotations
This schema is an implementation of the Department of Defense Discovery Metadata Specification version 3.0. By the DDMS Focus Group: Robert Allegar - Booz Allen Hamilton Arsic Antoinette - Mitre Corp. Wil Bailey - DLA Daniel Barclay - FGM, Inc. Brian Brotsos - SAIC Clive Carpi - SAIC Mike Daconta - McDonald Bradley Stan Davis - DISA Michael Fontaine - OSD/NII Glenda Hayes - Mitre Corp. Kirk Maskalenko - FGM, Inc. Mary Ann Melosh - SAIC Eric Peterson - McDonald Bradley Jim Pipher - DISA Joseph J. Pantella, FGM, Inc. Glenn Pruitt - FGM, Inc. Tony Reggio - Pennsylvania State University Kyle Rice - McDonald Bradley Clay Robinson - OSD/NII Rebecca Smith - DIA Brian Sullivan - NGA (NIMA) Eric Yuan - Booz Allen Hamilton JJP
Change Log: 07/13/2004 (J. Pantella) -- Added a global classification attribute per CR #1 of July 1, 2004 DDMS modification. 07/13/2004 (J. Pantella) -- Modified title and subtitle elements to use the classification attribute per CR #1 of July 1, 2004 DDMS modification. 07/13/2004 (J. Pantella) -- Modified SubjectType category and keywords per CR #2 of July 1, 2004 DDMS modification. NOTE: At least one of either Keyword or Category must appear, after one instance of either appears, additional categories must appear before additional keywords. 07/13/2004 (J. Pantella) -- Modified CompoundSourceIdentifierType to support the schema qualifier and schema HREF attributes on the source element per CR#4 of July 1, 2004 DDMS modification. 07/14/2004 (J. Pantella) -- Fixed bug that prevented street address information from being included in the Place and Facility elements. 07/26/2004 (J. Pantella) -- Modified the qualifier attribute of the CompoundCategoryIdentifierType used in the category element to be of type xs:anyURI. 08/04/2004 (J. Pantella) -- Modified Place and Facility to support the state element. 08/04/2004 (J. Pantella) -- Removed AddressType because it was not used. 08/06/2004 (J. Pantella) -- Required xs:any element to have a minoccurs of 0. 08/11/2004 (J. Pantella) -- Modified contributor, producer, creator and pointOfContact to be of respective types. Eliminated the substitution group solution previously employed. 08/16/2004 (J. Pantella) -- Modified CompoundResourceIdentifierType and QualifiedExtentValueType qualifier attributes to be of xs:anyURI per Tiger Team. 08/17/2004 (J. Pantella) -- Modified the target namespace to reflect the needs identified in the Registry meetings (G. Hayes in attendance). 08/23/2004 (J. Pantella) -- Added comments to annotate changes made by the Tiger Team. 11/23/2004 (J. Pantella) -- Modified title, subtitle, description, publisher, contributor, creator and security elements to reuse the ICISM:SecurityAttributesGroup. 11/23/2004 (J. Pantella) -- Removed prior implementation of security and classification attributes. 11/23/2004 (J. Pantella) -- Modified the temporalCoverage sub-elements to provide mechanism to specify Unknown or Not Applicable value defaulting to Unknown persuant to the approval of CR#11. 12/12/2004 (J. Pantella) -- Modified subjectType to eliminate redundancy causing tool issues. 12/16/2004 (J. Pantella) -- Commented out all residual elements and types related to the previous, substitution group based, modeling of the creator, publisher, and contributor. 1/2/2005 (J. Pantella) -- Modified namespace and comments to remove anticipated name change. 1/19/2005 (J. Pantella) -- Modified title and subtitle to support mulitple appearances. 6/22/2005 (J.Pantella) -- Modified geospatialCoverage element to support a richer geospatial description compliant with ISO 19115, pursuant to the approval of CR #13, the geospatialCoverage elment within a Resource is not strictly mandatory per the specification. 7/20/2005 (J.Pantella) -- Changed geospatialCoverage/Place to geospatialCoverage/GeospatialExtent per comments from NGA et al. at IC MWG meeting of July 8, 2005. 6/05/2007 (J. Pantella) -- Modified the SubjectType to comply with the approved resolution of CR 2006-1. See also http://metadata.dod.mil/mdr/irs/DDMS/cm/CR/2006/DDMS-CR-2006-1. 6/05/2007 (J. Pantella) -- Modified the DDMS XML Schema file structure to reflect the approved changes per CR 2007-1. See also http://metadata.dod.mil/mdr/irs/DDMS/cm/CR/2007/DDMS-CR-2007-1. 1/3/2007 (J. Pantella) -- Modified version attribute to reflect that this is version 1.4.2. 1/3/2007 (J. Pantella) -- Corrected spelling error in the top level documentation element of the XML Schema. 7/15/2008 (J. Pantella) -- Modified creator, publisher, contributor, and pointOfContact to fall under a mandatory choice. The desired effect is that one or more creator, publisher, contributor, or pointOfContact elements may appear in a DDMS instance, but there must be at least one. Change is pursuant to CR 2008-3. See also http://metadata.dod.mil/mdr/irs/DDMS/cm/CR/2008/DDMS-CR-2008-3. 7/15/2008 (J. Pantella) -- Modified ddms:Resource to support a relatedResources element allowing a DDMS instance document to assert relationships between the described resource and other related resources. 1/4/2010 (P. Lunceford) -- Created DDMS 3.0. Implemented CR 2009-08 (make maxOccurs on any to be unbounded), and CR 2009-12 (adding Security markings to the header and requiring a ddmsRecordDate).
Properties
attribute form default: qualified
element form default: qualified
version: 3.0
Schema location DDMS-v3_0.xsd
Element Resource
Namespace http://metadata.dod.mil/mdr/ns/DDMS/3.0/
Diagram
Diagram IC-ISM_xsd.tmp#id237 IC-ISM_xsd.tmp#id243 DDMS-Globals_xsd.tmp#id57 DDMS-Globals_xsd.tmp#id61 DDMS-Globals_xsd.tmp#id63 DDMS-Globals_xsd.tmp#id65 DDMS-Globals_xsd.tmp#id67 DDMS-Globals_xsd.tmp#id72 DDMS-Globals_xsd.tmp#id79 DDMS-Globals_xsd.tmp#id84 DDMS-Globals_xsd.tmp#id92 DDMS-Globals_xsd.tmp#id96 DDMS-Globals_xsd.tmp#id120 DDMS-Globals_xsd.tmp#id121 DDMS-Globals_xsd.tmp#id122 DDMS-Globals_xsd.tmp#id123 DDMS-Globals_xsd.tmp#id135 DDMS-Globals_xsd.tmp#id147 DDMS-Globals_xsd.tmp#id151 DDMS-GeospatialCoverage_xsd.tmp#id160 DDMS-Globals_xsd.tmp#id223 DDMS-Globals_xsd.tmp#id235 DDMS-v3_0_xsd.tmp#id56
Type ResourceType
Properties
content: complex
Used by
Model identifier+ , title+ , subtitle* , description , language+ , dates{0,1} , rights{0,1} , source* , type* , (creator+ | publisher+ | contributor+ | pointOfContact+) , format{0,1} , subjectCoverage , virtualCoverage* , temporalCoverage* , geospatialCoverage* , relatedResources* , security , ANY element from ANY namespace OTHER than 'http://metadata.dod.mil/mdr/ns/DDMS/3.0/'
Children contributor, creator, dates, description, format, geospatialCoverage, identifier, language, pointOfContact, publisher, relatedResources, rights, security, source, subjectCoverage, subtitle, temporalCoverage, title, type, virtualCoverage
Instance
 
<Resource compliesWith="" createDate="" DESVersion="" resourceElement="true" SchemaguideSecurityAttributesGroup="">
  <identifier qualifier="" value="">{1,unbounded}</identifier>
  <title SchemaguideSecurityAttributesGroup="">{1,unbounded}</title>
  <subtitle SchemaguideSecurityAttributesGroup="">{0,unbounded}</subtitle>
  <description SchemaguideSecurityAttributesGroup="">{1,1}</description>
  <language qualifier="" value="">{1,unbounded}</language>
  <dates created="" infoCutOff="" posted="" validTil="">{0,1}</dates>
  <rights copyright="false" intellectualProperty="false" privacyAct="false">{0,1}</rights>
  <source qualifier="" SchemaguideSecurityAttributesOptionGroup="" schemaHref="" schemaQualifier="" value="">{0,unbounded}</source>
  <type qualifier="" value="">{0,unbounded}</type>
  <format>{0,1}</format>
  <subjectCoverage SchemaguideSecurityAttributesOptionGroup="">{1,1}</subjectCoverage>
  <virtualCoverage address="" protocol="" SchemaguideSecurityAttributesOptionGroup="">{0,unbounded}</virtualCoverage>
  <temporalCoverage SchemaguideSecurityAttributesOptionGroup="">{0,unbounded}</temporalCoverage>
  <geospatialCoverage SchemaguideSecurityAttributesOptionGroup="">{0,unbounded}</geospatialCoverage>
  <relatedResources direction="outbound" relationship="" SchemaguideSecurityAttributesOptionGroup="">{0,unbounded}</relatedResources>
  <security excludeFromRollup="true" SchemaguideSecurityAttributesGroup="">{1,1}</security>
</Resource>
Attributes
QName Type Fixed Default Use Annotation
ANY attribute from ANY namespace OTHER than 'http://metadata.dod.mil/mdr/ns/DDMS/3.0/'
DESVersion xsd:int required
The version number of the DES. Should there be multiple specified in an instance document the one at the root node is the one that will apply to the entire document.
SchemaguideSecurityAttributesGroup xsd:NMTOKEN optional
This attribute is only a placeholder so that all the ISM attributes are not shown in the schemaGuide for every element. If you refer to the documentation of the attribute group it will say what attributes should be here.
compliesWith CVEnumISMCompliesWith optional
This attribute is used at the resource level. An indicator of what optional ISM rule sets the documents complies with. This allows sytems to know that the document claims compliance with these rule sets and they should be enforced. PERMISSIBLE VALUES The permissible values for this simple type are defined in the Controlled Value Enumeration: CVEnumISMcompliesWith.xml
createDate xsd:date required
This attribute is used to designate what date the document was produced on. This is the date that will be used by various constraint rules to determine if the document meets all the business rules. It must be on the element where resourceElement is true.
resourceElement xsd:boolean true required
This attribute is used to designate which element has the ISM attributes representing the classification for the entire resource. Every document must have at least one element with this indicator as true. It should be rare that a document has more than one. Mainly this would occur in some sort of aggregator schema. In that unusual case the first one encountered in XML document order is the one used for all constraint rules.
Source
 
<xs:element name="Resource" type="ResourceType">
  <xs:annotation>
    <xs:appinfo>
      <mdr:definition>The Resource element is the root element for a DDMS 3.0 compliant record.</mdr:definition>
      <mdr:comment/>
    </xs:appinfo>
  </xs:annotation>
</xs:element>
Schema location DDMS-v3_0.xsd
Complex Type ResourceType
Namespace http://metadata.dod.mil/mdr/ns/DDMS/3.0/
Diagram
Diagram IC-ISM_xsd.tmp#id237 IC-ISM_xsd.tmp#id243 DDMS-Globals_xsd.tmp#id57 DDMS-Globals_xsd.tmp#id61 DDMS-Globals_xsd.tmp#id63 DDMS-Globals_xsd.tmp#id65 DDMS-Globals_xsd.tmp#id67 DDMS-Globals_xsd.tmp#id72 DDMS-Globals_xsd.tmp#id79 DDMS-Globals_xsd.tmp#id84 DDMS-Globals_xsd.tmp#id92 DDMS-Globals_xsd.tmp#id96 DDMS-Globals_xsd.tmp#id120 DDMS-Globals_xsd.tmp#id121 DDMS-Globals_xsd.tmp#id122 DDMS-Globals_xsd.tmp#id123 DDMS-Globals_xsd.tmp#id135 DDMS-Globals_xsd.tmp#id147 DDMS-Globals_xsd.tmp#id151 DDMS-GeospatialCoverage_xsd.tmp#id160 DDMS-Globals_xsd.tmp#id223 DDMS-Globals_xsd.tmp#id235
Used by
Element Resource
Model identifier+ , title+ , subtitle* , description , language+ , dates{0,1} , rights{0,1} , source* , type* , (creator+ | publisher+ | contributor+ | pointOfContact+) , format{0,1} , subjectCoverage , virtualCoverage* , temporalCoverage* , geospatialCoverage* , relatedResources* , security , ANY element from ANY namespace OTHER than 'http://metadata.dod.mil/mdr/ns/DDMS/3.0/'
Children contributor, creator, dates, description, format, geospatialCoverage, identifier, language, pointOfContact, publisher, relatedResources, rights, security, source, subjectCoverage, subtitle, temporalCoverage, title, type, virtualCoverage
Attributes
QName Type Fixed Default Use Annotation
ANY attribute from ANY namespace OTHER than 'http://metadata.dod.mil/mdr/ns/DDMS/3.0/'
DESVersion xsd:int required
The version number of the DES. Should there be multiple specified in an instance document the one at the root node is the one that will apply to the entire document.
SchemaguideSecurityAttributesGroup xsd:NMTOKEN optional
This attribute is only a placeholder so that all the ISM attributes are not shown in the schemaGuide for every element. If you refer to the documentation of the attribute group it will say what attributes should be here.
compliesWith CVEnumISMCompliesWith optional
This attribute is used at the resource level. An indicator of what optional ISM rule sets the documents complies with. This allows sytems to know that the document claims compliance with these rule sets and they should be enforced. PERMISSIBLE VALUES The permissible values for this simple type are defined in the Controlled Value Enumeration: CVEnumISMcompliesWith.xml
createDate xsd:date required
This attribute is used to designate what date the document was produced on. This is the date that will be used by various constraint rules to determine if the document meets all the business rules. It must be on the element where resourceElement is true.
resourceElement xsd:boolean true required
This attribute is used to designate which element has the ISM attributes representing the classification for the entire resource. Every document must have at least one element with this indicator as true. It should be rare that a document has more than one. Mainly this would occur in some sort of aggregator schema. In that unusual case the first one encountered in XML document order is the one used for all constraint rules.
Source
 
<xs:complexType name="ResourceType">
  <xs:annotation>
    <xs:appinfo>
      <mdr:definition>The type definition for the ddms:Resource element.</mdr:definition>
      <mdr:comment>Defines the structure of a DDMS record.</mdr:comment>
    </xs:appinfo>
  </xs:annotation>
  <xs:sequence>
    <xs:element ref="identifier" maxOccurs="unbounded"/>
    <xs:element ref="title" maxOccurs="unbounded"/>
    <xs:element ref="subtitle" minOccurs="0" maxOccurs="unbounded"/>
    <!-- IC-IRM change to require description -->
    <xs:element ref="description" minOccurs="1" maxOccurs="1"/>
    <!-- IC-IRM change to require language -->
    <xs:element ref="language" minOccurs="1" maxOccurs="unbounded"/>
    <xs:element ref="dates" minOccurs="0"/>
    <xs:element ref="rights" minOccurs="0"/>
    <xs:element ref="source" minOccurs="0" maxOccurs="unbounded"/>
    <xs:element ref="type" minOccurs="0" maxOccurs="unbounded"/>
    <xs:choice maxOccurs="unbounded">
      <xs:element ref="creator" maxOccurs="unbounded"/>
      <xs:element ref="publisher" maxOccurs="unbounded"/>
      <xs:element ref="contributor" maxOccurs="unbounded"/>
      <xs:element ref="pointOfContact" maxOccurs="unbounded"/>
    </xs:choice>
    <xs:element ref="format" minOccurs="0"/>
    <xs:element ref="subjectCoverage"/>
    <xs:element ref="virtualCoverage" minOccurs="0" maxOccurs="unbounded"/>
    <xs:element ref="temporalCoverage" minOccurs="0" maxOccurs="unbounded"/>
    <xs:element ref="geospatialCoverage" minOccurs="0" maxOccurs="unbounded"/>
    <xs:element ref="relatedResources" minOccurs="0" maxOccurs="unbounded"/>
    <xs:element ref="security"/>
    <xs:any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded">
      <xs:annotation>
        <xs:documentation>This xs:any is the extensibility point for DDMS.  The intent is that a COI-defined wrapper element may be placed after the ddms:security element.  The wrapper element will contain any infomrmation that the COI wishes to include in DDMS instance documents.  Information intended to supplement or extend existing ddms elements must also leverage this mechanism.</xs:documentation>
      </xs:annotation>
    </xs:any>
  </xs:sequence>
  <!-- IC-IRM Modifed removed security group since ISM V4 includes it in ResourceNodeAttributeGroup -->
  <xs:attributeGroup ref="ICISM:ResourceNodeAttributeGroup"/>
  <xs:attributeGroup ref="ICISM:ISMRootNodeAttributeGroup"/>
  <xs:anyAttribute namespace="##other" processContents="lax"/>
</xs:complexType>
Schema location DDMS-v3_0.xsd