<?xml version="1.0" encoding="utf-8" ?>
<!-- Updated 6/11/2005 11:20:05 PM -->
<drm:DataReferenceModel xml:base="http://any-uri" xmlns:drm="http://egov.gov/fea" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://egov.gov/fea
Draft_FEA_DRM_XML_Schema_v.0.1.xsd">
<!-- Root node of the DRM XML instance document.-->

	<!-- Container for all metadata related to one particular instance of a DRM submission.-->
	<drm:SubmissionMetadata>
		<!-- Government agency, bureau, office, or department that submits this DRM instance.-->
		<drm:SubmittingAgency>Any string value</drm:SubmittingAgency>
		<!-- Date that this DRM instance was submitted.  May include time as well as date.-->
		<drm:SubmissionDate>2005-01-01</drm:SubmissionDate>
		<!-- Any string an agency chooses to differentiate submission version that represent the same set of data elements. Note that the elements SubmissionDate or Identifier could be used to capture version instead.-->
		<drm:SubmissionVersion>Any string value</drm:SubmissionVersion>
		<!-- A name given to the resource. This element is taken from the Dublin Core metadata standard v1.1.-->
		<dc:Title>Any string value</dc:Title>
		<!-- 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, such as a URI. This element is taken from the Dublin Core metadata standard v1.1.-->
		<dc:Identifier>http://any-uri</dc:Identifier>
		<!-- An account of the content of the resource. Examples include: An abstract, table of contents, reference to a graphical representation of content or a free-text account of the content. This element is taken from the Dublin Core metadata standard v1.1.-->
		<dc:Description>Any string value</dc:Description>
		<!-- 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. This element is taken from the Dublin Core metadata standard v1.1.-->
		<dc:Subject>Any string value</dc:Subject>
		<!-- A URI pointing to the person or organization to contact for more information regarding the data source.  This usually includes a name, phone number, email address, and other contact information.  The resource/record should ideally be a structured machine-readable resource (e.g., XML document), but can be a HTML/web page providing the appropriate documentation.-->
		<drm:PointOfContact>http://any-uri</drm:PointOfContact>
	</drm:SubmissionMetadata>
	<!-- This element implements the "data description" portion of the DRM meta-model.  It provides a standard means for agencies to describe their data and data sources clearly, concisely, and unambiguously.-->
	<drm:DataDescription>
		<!-- This element contains definitions for structured, semi-structured, and unstructured data.-->
		<drm:Data>
			<!-- Data described via the E-R (Entity-Relationship) or class model.-->
			<drm:StructuredData>
				<!-- A collection of entities.-->
				<drm:Entities>
					<!-- A named template used to describe a population of items with common characteristics. Like the set of persons, places or things.-->
					<drm:Entity rdf:id="http://any-uri" drm:name="Any string value">
						<!-- A collection of ResourceRefs.  A ResourceRef links an object with a related resource.-->
						<drm:ResourceRefs>
							<!-- This element points back to a related resource.  It is used primarily to elaborate on a relationship between an Entity (or ExternalEntityRef) and a resource that aggregates instances of that entity.  For example, a spreadsheet (Resource) that lists employee (Entity) information.  It can also be used to link together two resources. It contains two attributes:  type and rdf:idref. Type is generally "partOf".  rdf:idref points back to the Resource's unique identifier.-->
							<drm:ResourceRef drm:type="instanceOf" rdf:idref="Any string value" />
						</drm:ResourceRefs>
						<!-- A list of data source references.-->
						<drm:DataSourceRefs>
							<!-- A pointer to the unique ID of the associated data source, either in the DRM instance (rdf:id) or in an external DRM instance (DRM_Instance_URI#rdf:id).-->
							<drm:DataSourceRef rdf:idref="Any string value" drm:authoritativeSource="true" />
						</drm:DataSourceRefs>
						<!-- A collection of characteristics that describe the entity (e.g., "first_name", "last_name", etc.).-->
						<drm:Attributes>
							<!-- A property belonging to an entity (e.g., "first_name", "last_name", etc.).-->
							<drm:Attribute drm:name="Any string value" drm:datatype="Any string value" drm:keyType="foreign key">
								<!-- A list of data source references.-->
								<drm:DataSourceRefs>
									<!-- A pointer to the unique ID of the associated data source, either in the DRM instance (rdf:id) or in an external DRM instance (DRM_Instance_URI#rdf:id).-->
									<drm:DataSourceRef rdf:idref="Any string value" drm:authoritativeSource="true" />
								</drm:DataSourceRefs>
								<!-- A description of the associated term/object.-->
								<drm:Definition>Any string value</drm:Definition>
								<!-- A collection of NodeRefs. NodeRefs are pointers from an object to a taxonomy node.-->
								<drm:NodeRefs>
									<!-- A link to a taxonomy node. The unique ID of the target taxonomy node is documented in the rdf:idref attribute.  The type attribute specifies the nature of the relationship, e.g. "partOf", "instanceOf", or "subclassOf". This element can be used by the following elements to link to a taxonomy node:

1.  Entity
2. Resource
3.  DataSource
4.  ExchangePackage
5.  Another taxonomy node
6.  External references to any of the above.
7.  Attribute:  When used with an attribute, a NodeRef typically points to a taxonomy node containing a Terms collection providing a "controlled vocabulary" to constrain values populating instances of the attribute.

For web pages that need to point to a DRM taxonomy node in an inline fashion, standard HTML META tags can be used.  For example:

&lt;meta name="drm:NodeRef" content="http://cosine.cim3.net/file/work/DRM/data_dictionary/examples/DRM_Instance_Example_OJP_IT.xml#182 /&gt;-->
									<drm:NodeRef drm:type="instanceOf" rdf:idref="Any string value" />
								</drm:NodeRefs>
							</drm:Attribute>
						</drm:Attributes>
						<!-- A collection of relationships (associations) between entities.-->
						<drm:Relationships>
							<!-- An association between two entities.-->
							<drm:Relationship drm:name="Any string value" drm:key="Any string value" drm:cardinality="0">
								<!-- In a relationship between two entities, this element is used to describe the target entity.-->
								<drm:RelationshipTarget rdf:idref="Any string value" drm:key="Any string value" drm:cardinality="0" />
							</drm:Relationship>
						</drm:Relationships>
						<!-- A description of the associated term/object.-->
						<drm:Definition>Any string value</drm:Definition>
						<!-- A collection of NodeRefs. NodeRefs are pointers from an object to a taxonomy node.-->
						<drm:NodeRefs>
							<!-- A link to a taxonomy node. The unique ID of the target taxonomy node is documented in the rdf:idref attribute.  The type attribute specifies the nature of the relationship, e.g. "partOf", "instanceOf", or "subclassOf". This element can be used by the following elements to link to a taxonomy node:

1.  Entity
2. Resource
3.  DataSource
4.  ExchangePackage
5.  Another taxonomy node
6.  External references to any of the above.
7.  Attribute:  When used with an attribute, a NodeRef typically points to a taxonomy node containing a Terms collection providing a "controlled vocabulary" to constrain values populating instances of the attribute.

For web pages that need to point to a DRM taxonomy node in an inline fashion, standard HTML META tags can be used.  For example:

&lt;meta name="drm:NodeRef" content="http://cosine.cim3.net/file/work/DRM/data_dictionary/examples/DRM_Instance_Example_OJP_IT.xml#182 /&gt;-->
							<drm:NodeRef drm:type="instanceOf" rdf:idref="Any string value" />
						</drm:NodeRefs>
					</drm:Entity>
				</drm:Entities>
				<!-- A collection of ExternalEntitiesRefs.-->
				<drm:ExternalEntitiesRefs>
					<!-- Points to an entity (or collection of entities, e.g. a logical data model) defined externally using XMI, OWL, XSD, or other suitable standard. "Suitable" includes: 

1. An open, widely implemented standard, available free-of-charge and unencumbered by royalty or patent claims, or a standard implemented by a government agency
2. A well-documented, durable standard (i.e., under version/change control, backward compatibility, etc.)
3. Provides semantics for modeling, at a minimum, entities, attributes, types, and relationships.
4. Provides semantics for assigning an identifier per element that is guaranteed unique within the particular schema.-->
					<drm:ExternalEntitiesRef drm:href="http://any-uri" rdf:id="http://any-uri" drm:representationFormat="Any string value">
						<!-- A collection of ResourceRefs.  A ResourceRef links an object with a related resource.-->
						<drm:ResourceRefs>
							<!-- This element points back to a related resource.  It is used primarily to elaborate on a relationship between an Entity (or ExternalEntityRef) and a resource that aggregates instances of that entity.  For example, a spreadsheet (Resource) that lists employee (Entity) information.  It can also be used to link together two resources. It contains two attributes:  type and rdf:idref. Type is generally "partOf".  rdf:idref points back to the Resource's unique identifier.-->
							<drm:ResourceRef drm:type="instanceOf" rdf:idref="Any string value" />
						</drm:ResourceRefs>
						<!-- A list of data source references.-->
						<drm:DataSourceRefs>
							<!-- A pointer to the unique ID of the associated data source, either in the DRM instance (rdf:id) or in an external DRM instance (DRM_Instance_URI#rdf:id).-->
							<drm:DataSourceRef rdf:idref="Any string value" drm:authoritativeSource="true" />
						</drm:DataSourceRefs>
						<!-- A collection of NodeRefs. NodeRefs are pointers from an object to a taxonomy node.-->
						<drm:NodeRefs>
							<!-- A link to a taxonomy node. The unique ID of the target taxonomy node is documented in the rdf:idref attribute.  The type attribute specifies the nature of the relationship, e.g. "partOf", "instanceOf", or "subclassOf". This element can be used by the following elements to link to a taxonomy node:

1.  Entity
2. Resource
3.  DataSource
4.  ExchangePackage
5.  Another taxonomy node
6.  External references to any of the above.
7.  Attribute:  When used with an attribute, a NodeRef typically points to a taxonomy node containing a Terms collection providing a "controlled vocabulary" to constrain values populating instances of the attribute.

For web pages that need to point to a DRM taxonomy node in an inline fashion, standard HTML META tags can be used.  For example:

&lt;meta name="drm:NodeRef" content="http://cosine.cim3.net/file/work/DRM/data_dictionary/examples/DRM_Instance_Example_OJP_IT.xml#182 /&gt;-->
							<drm:NodeRef drm:type="instanceOf" rdf:idref="Any string value" />
						</drm:NodeRefs>
					</drm:ExternalEntitiesRef>
				</drm:ExternalEntitiesRefs>
			</drm:StructuredData>
			<!-- Data that are not described according to an E-R model, but is rather of a more free-form format, such as multimedia files or unstructured text.-->
			<drm:UnstructuredData>
				<!-- A collection of ExternalResourcesRefs.  These objects are pointers to external files that aggregate unstructured or semistructured resources (e.g., RSS feeds).-->
				<drm:ExternalResourcesRefs>
					<!-- Points to a URI of a model that aggregates metadata about unstructured or semi-structured resources. Normally points to a RSS, DDMS, or Atom file.-->
					<drm:ExternalResourcesRef drm:href="http://any-uri" rdf:id="http://any-uri" drm:representationFormat="Any string value">
						<!-- A collection of ResourceRefs.  A ResourceRef links an object with a related resource.-->
						<drm:ResourceRefs>
							<!-- This element points back to a related resource.  It is used primarily to elaborate on a relationship between an Entity (or ExternalEntityRef) and a resource that aggregates instances of that entity.  For example, a spreadsheet (Resource) that lists employee (Entity) information.  It can also be used to link together two resources. It contains two attributes:  type and rdf:idref. Type is generally "partOf".  rdf:idref points back to the Resource's unique identifier.-->
							<drm:ResourceRef drm:type="instanceOf" rdf:idref="Any string value" />
						</drm:ResourceRefs>
					</drm:ExternalResourcesRef>
				</drm:ExternalResourcesRefs>
				<!-- A collection of resources.-->
				<drm:Resources>
					<!-- Encapsulates a single "page view" of unstructured or semi-structured data, referenceable via a URI. This element aggregates numerous sub-elements, mostly metadata tags imported from the Dublin Core 1.1 set.

In some cases, Dublin Core metadata will be embedded in the actual resource itself.  In this case, there is no need to repeat the metadata in the DRM instance.  The Resource element can point to the actual resource itself, populating the rdf:id attribute with the resource's URI.-->
					<drm:Resource rdf:id="http://any-uri">
						<!-- A name given to the resource. This element is taken from the Dublin Core metadata standard v1.1.-->
						<dc:Title>Any string value</dc:Title>
						<!-- 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, such as a URI. This element is taken from the Dublin Core metadata standard v1.1.-->
						<dc:Identifier>http://any-uri</dc:Identifier>
						<!-- A date of an event in the lifecycle of the resource. Will typically 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. This element is taken from the Dublin Core metadata standard v1.1.-->
						<dc:Date>2005-01-01</dc:Date>
						<!-- An entity primarily responsible for making the content of the resource. Examples include a person, an organization, or a service. Typically, the name of a Creator should be used to indicate the entity. This element is taken from the Dublin Core metadata standard v1.1.-->
						<dc:Creator>Any string value</dc:Creator>
						<!-- 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 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 [MIME] defining computer media formats). This element is taken from the Dublin Core metadata standard v1.1.-->
						<dc:Format>Any string value</dc:Format>
						<!-- An account of the content of the resource. Examples include: An abstract, table of contents, reference to a graphical representation of content or a free-text account of the content. This element is taken from the Dublin Core metadata standard v1.1.-->
						<dc:Description>Any string value</dc:Description>
						<!-- 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. This element is taken from the Dublin Core metadata standard v1.1.-->
						<dc:Source>http://any-uri</dc:Source>
						<!-- 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. This element is taken from the Dublin Core metadata standard v1.1.-->
						<dc:Subject>Any string value</dc:Subject>
						<!-- 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. This element is taken from the Dublin Core metadata standard v1.1.-->
						<dc:Type>Collection</dc:Type>
						<!-- 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.-->
						<dc:Publisher>Any string value</dc:Publisher>
						<!-- 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.-->
						<dc:Contributor>Any string value</dc:Contributor>
						<!-- A language of the intellectual content of the resource. Recommended best practice is to use RFC 3066 [RFC3066] which, in conjunction with ISO639 [ISO639]), 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.-->
						<dc:Language>eng</dc:Language>
						<!-- 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.-->
						<dc:Relation>Any string value</dc:Relation>
						<!-- 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.-->
						<dc:Coverage>Any string value</dc:Coverage>
						<!-- 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.-->
						<dc:Rights>Any string value</dc:Rights>
					</drm:Resource>
				</drm:Resources>
			</drm:UnstructuredData>
			<!-- Data that have characteristics of both structured and unstructured data.-->
			<drm:SemiStructuredData>
				<!-- A collection of entities.-->
				<drm:Entities>
					<!-- A named template used to describe a population of items with common characteristics. Like the set of persons, places or things.-->
					<drm:Entity rdf:id="http://any-uri" drm:name="Any string value">
						<!-- A collection of characteristics that describe the entity (e.g., "first_name", "last_name", etc.).-->
						<drm:Attributes>
							<!-- A property belonging to an entity (e.g., "first_name", "last_name", etc.).-->
							<drm:Attribute drm:name="Any string value" drm:datatype="Any string value" drm:keyType="foreign key">
								<!-- A description of the associated term/object.-->
								<drm:Definition>Any string value</drm:Definition>
							</drm:Attribute>
						</drm:Attributes>
						<!-- A collection of relationships (associations) between entities.-->
						<drm:Relationships>
							<!-- An association between two entities.-->
							<drm:Relationship drm:name="Any string value" drm:key="Any string value" drm:cardinality="0">
								<!-- In a relationship between two entities, this element is used to describe the target entity.-->
								<drm:RelationshipTarget rdf:idref="Any string value" drm:key="Any string value" drm:cardinality="0" />
							</drm:Relationship>
						</drm:Relationships>
						<!-- A description of the associated term/object.-->
						<drm:Definition>Any string value</drm:Definition>
					</drm:Entity>
				</drm:Entities>
				<!-- A collection of ExternalEntitiesRefs.-->
				<drm:ExternalEntitiesRefs>
					<!-- Points to an entity (or collection of entities, e.g. a logical data model) defined externally using XMI, OWL, XSD, or other suitable standard. "Suitable" includes: 

1. An open, widely implemented standard, available free-of-charge and unencumbered by royalty or patent claims, or a standard implemented by a government agency
2. A well-documented, durable standard (i.e., under version/change control, backward compatibility, etc.)
3. Provides semantics for modeling, at a minimum, entities, attributes, types, and relationships.
4. Provides semantics for assigning an identifier per element that is guaranteed unique within the particular schema.-->
					<drm:ExternalEntitiesRef drm:href="http://any-uri" rdf:id="http://any-uri" drm:representationFormat="Any string value">
					</drm:ExternalEntitiesRef>
				</drm:ExternalEntitiesRefs>
				<!-- A collection of ExternalResourcesRefs.  These objects are pointers to external files that aggregate unstructured or semistructured resources (e.g., RSS feeds).-->
				<drm:ExternalResourcesRefs>
					<!-- Points to a URI of a model that aggregates metadata about unstructured or semi-structured resources. Normally points to a RSS, DDMS, or Atom file.-->
					<drm:ExternalResourcesRef drm:href="http://any-uri" rdf:id="http://any-uri" drm:representationFormat="Any string value">
					</drm:ExternalResourcesRef>
				</drm:ExternalResourcesRefs>
				<!-- A collection of resources.-->
				<drm:Resources>
					<!-- Encapsulates a single "page view" of unstructured or semi-structured data, referenceable via a URI. This element aggregates numerous sub-elements, mostly metadata tags imported from the Dublin Core 1.1 set.

In some cases, Dublin Core metadata will be embedded in the actual resource itself.  In this case, there is no need to repeat the metadata in the DRM instance.  The Resource element can point to the actual resource itself, populating the rdf:id attribute with the resource's URI.-->
					<drm:Resource rdf:id="http://any-uri">
						<!-- A name given to the resource. This element is taken from the Dublin Core metadata standard v1.1.-->
						<dc:Title>Any string value</dc:Title>
						<!-- 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, such as a URI. This element is taken from the Dublin Core metadata standard v1.1.-->
						<dc:Identifier>http://any-uri</dc:Identifier>
						<!-- A date of an event in the lifecycle of the resource. Will typically 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. This element is taken from the Dublin Core metadata standard v1.1.-->
						<dc:Date>2005-01-01</dc:Date>
						<!-- An entity primarily responsible for making the content of the resource. Examples include a person, an organization, or a service. Typically, the name of a Creator should be used to indicate the entity. This element is taken from the Dublin Core metadata standard v1.1.-->
						<dc:Creator>Any string value</dc:Creator>
						<!-- 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 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 [MIME] defining computer media formats). This element is taken from the Dublin Core metadata standard v1.1.-->
						<dc:Format>Any string value</dc:Format>
						<!-- An account of the content of the resource. Examples include: An abstract, table of contents, reference to a graphical representation of content or a free-text account of the content. This element is taken from the Dublin Core metadata standard v1.1.-->
						<dc:Description>Any string value</dc:Description>
						<!-- 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. This element is taken from the Dublin Core metadata standard v1.1.-->
						<dc:Source>http://any-uri</dc:Source>
						<!-- 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. This element is taken from the Dublin Core metadata standard v1.1.-->
						<dc:Subject>Any string value</dc:Subject>
						<!-- 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. This element is taken from the Dublin Core metadata standard v1.1.-->
						<dc:Type>Collection</dc:Type>
						<!-- 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.-->
						<dc:Publisher>Any string value</dc:Publisher>
						<!-- 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.-->
						<dc:Contributor>Any string value</dc:Contributor>
						<!-- A language of the intellectual content of the resource. Recommended best practice is to use RFC 3066 [RFC3066] which, in conjunction with ISO639 [ISO639]), 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.-->
						<dc:Language>eng</dc:Language>
						<!-- 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.-->
						<dc:Relation>Any string value</dc:Relation>
						<!-- 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.-->
						<dc:Coverage>Any string value</dc:Coverage>
						<!-- 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.-->
						<dc:Rights>Any string value</dc:Rights>
					</drm:Resource>
				</drm:Resources>
			</drm:SemiStructuredData>
		</drm:Data>
		<!-- A collection of data sources.-->
		<drm:DataSources>
			<!-- An aggregated, managed container. A database, system, application, or other electronic entity that produces and/or houses data.-->
			<drm:DataSource drm:href="http://any-uri" rdf:id="http://any-uri" drm:name="Any string value">
				<!-- The agency providing primary stewardship for the data asset.-->
				<drm:OwningAgency>Any string value</drm:OwningAgency>
				<!-- A URI pointing to a resource or record identifying the person providing primary stewardship for the data asset. The resource/record should ideally be a structured machine-readable resource (e.g., XML document), but can be a HTML/web page providing the appropriate documentation.-->
				<drm:Steward>http://any-uri</drm:Steward>
				<!-- A boolean flag indicating whether or not a particular data source supports or provides Geospatial data.-->
				<drm:GeospatialEnabled>true</drm:GeospatialEnabled>
				<!-- Denotes whether or not the datasource in question contains Privacy Act information.  This includes an individual's name, SSN, and/or personal identifier, and at least one other element of personal information about the individual (such as date of birth).-->
				<drm:SystemOfRecord>true</drm:SystemOfRecord>
				<!-- The type of data source (e.g. website, database, document repository, etc.).-->
				<drm:DataSourceType>Any string value</drm:DataSourceType>
				<!-- A URI pointing to the person or organization to contact for more information regarding the data source.  This usually includes a name, phone number, email address, and other contact information.  The resource/record should ideally be a structured machine-readable resource (e.g., XML document), but can be a HTML/web page providing the appropriate documentation.-->
				<drm:PointOfContact>http://any-uri</drm:PointOfContact>
				<!-- FIPS 199 potential impact levels.-->
				<drm:FIPS199PotentialImpactLevels>
					<!-- Valid values can be "L, M, H" (for low, moderate, high).-->
					<drm:AvailabilityLevel>high</drm:AvailabilityLevel>
					<!-- Valid values can be "L, M, H" (for low, moderate, high).-->
					<drm:IntegrityLevel>high</drm:IntegrityLevel>
					<!-- Valid values can be "L, M, H" (for low, moderate, high).-->
					<drm:ConfidentialityLevel>high</drm:ConfidentialityLevel>
				</drm:FIPS199PotentialImpactLevels>
			</drm:DataSource>
		</drm:DataSources>
	</drm:DataDescription>
	<!-- The element contains the data sharing portion of the FEA DRM meta-model.  It includes syntax for modeling exchange packages and access points. It provides a standard means for describing interagency data exchanges and data sharing capabilities.-->
	<drm:DataSharing>
		<!-- A collection of exchange packages.-->
		<drm:ExchangePackages>
			<!-- A description of a specific information exchange between organizations.-->
			<drm:ExchangePackage rdf:id="http://any-uri">
				<!-- A URI representing a sender of a message.  Depending on the value of @senderType below, this URI can represent either an information record (e.g. contact info) or a service endpoint (e.g., a web service URL or email address).-->
				<drm:Sender drm:href="http://any-uri" drm:senderType="agency" />
				<!-- A URI representing a recipient of a message.  Depending on the value of @recipientType below, this URI can represent either an information record (e.g. contact info) or a service endpoint (e.g., a web service URL or email address).-->
				<drm:Recipient drm:href="http://any-uri" drm:recipientType="agency" />
				<!-- Frequencies per unit this exchange is estimated to occur.-->
				<drm:ExchangeFrequency drm:frequency="999" drm:unit="day" />
				<!-- The security classification of the exchange package. Valid elements include: "(U)nclassified", "(F)OUO", "(S)ecret", "TS (Top Secret)".-->
				<drm:Classification>FOUO</drm:Classification>
				<!-- Type of exchange, such as: Query/response, publish/subscribe, etc. Legal values include (To Be Published).-->
				<drm:TransactionType>Publish/Subscribe</drm:TransactionType>
				<!-- Status of exchange - e.g. in progress or complete. Legal values include (To Be Published).-->
				<drm:Status>complete</drm:Status>
				<!-- A collection of entity references.-->
				<drm:EntityRefs>
					<!-- Associates the ExchangePackage with one or more entities. These may be entities defined in the "StructuredData" section above, external entities (such as an XML schema with which the message payload is to conform), or both. If external, the "standardRef" attribute may reference a standard defined in the "DataStandards" section below that the external entity conforms to, such as W3C Schema.-->
					<drm:EntityRef rdf:idref="Any string value" />
				</drm:EntityRefs>
			</drm:ExchangePackage>
			<!-- Points to data sharing service interfaces created using an approved standard.  For a standard to be approved, it must be:
 
1.  An open, widely implemented standard, available free-of-charge and unencumbered by royalty or patent claims, or a standard implemented by a government agency
2.  A well-documented, durable standard (i.e., under version/change control, well-documented, backward compatibility, etc.)
3.  Provides semantics for modeling, at a minimum, service inputs and outputs/payloads, service protocol, and service endpoints.
4.  Provides semantics for assigning an identifier per element that is guaranteed unique within the particular model.
 
Candidate standards for implementing data exchange services include WSDL.-->
			<drm:ExternalExchangePackageRef drm:href="http://any-uri" rdf:id="http://any-uri" drm:representationFormat="Any string value">
			</drm:ExternalExchangePackageRef>
		</drm:ExchangePackages>
		<!-- A description of the requirements for electronic access to a data source and its data.-->
		<drm:DataAccessPoints>
			<!-- An endpoint (network or otherwise) providing an interface for querying a data source.-->
			<drm:AccessPoint rdf:id="http://any-uri">
				<!-- The security classification of the exchange package. Valid elements include: "(U)nclassified", "(F)OUO", "(S)ecret", "TS (Top Secret)".-->
				<drm:Classification>FOUO</drm:Classification>
				<!-- Type of exchange, such as: Query/response, publish/subscribe, etc. Legal values include (To Be Published).-->
				<drm:TransactionType>Publish/Subscribe</drm:TransactionType>
				<!-- Status of exchange - e.g. in progress or complete. Legal values include (To Be Published).-->
				<drm:Status>complete</drm:Status>
				<!-- The network endpoint for this access point.-->
				<drm:Endpoint>Any string value</drm:Endpoint>
				<!-- The standard query mechanism that will be used to access the data within this data source - e.g. SQL-92, CQL (Z39.50), XQuery, Boolean Operators, WSDL, HTTP GET, etc. Legal values include (To Be Published).-->
				<drm:QueryLanguage>CQL</drm:QueryLanguage>
				<!-- The format of the payload returned by the access point in response to a query.-->
				<drm:ResultFormat drm:exchangePackageRef="Any string value" />
				<!-- A container categorizing security-related information.-->
				<drm:Security>
					<!-- The standard and/or protocol providing access control for this query point (e.g. Basic HTTP authentication, Kerberos, etc.). Legal values include (To Be Published).-->
					<drm:AccessControlProtocol>HTTP-Basic</drm:AccessControlProtocol>
					<!-- The minimal level of encryption needed to pass data to and from this particular access point. Legal values include (To Be Published).-->
					<drm:Encryption>FIPS 185 (EES)</drm:Encryption>
				</drm:Security>
				<!-- Quality-of-service (QoS)-related information.-->
				<drm:QualityOfService>
					<!-- The number of seconds needed to pass a message to an access point.  Usually measured from the initiation of the request to the receipt of the response.-->
					<drm:Latency>999</drm:Latency>
					<!-- Information relating to reliable messaging capabilities.-->
					<drm:ReliableMessaging>Any string value</drm:ReliableMessaging>
				</drm:QualityOfService>
			</drm:AccessPoint>
		</drm:DataAccessPoints>
	</drm:DataSharing>
	<!-- A container for elements that implement the data context portion of the DRM meta-model.-->
	<drm:DataContext>
		<!-- A collection of taxonomies.-->
		<drm:Taxonomies>
			<!-- An information model (typically hierarchical) that defines the scope of a knowledge domain.-->
			<drm:Taxonomy rdf:id="http://any-uri">
				<!-- A collection of taxonomy nodes.-->
				<drm:Nodes>
					<!-- A node in a taxonomy.-->
					<drm:Node rdf:id="http://any-uri" drm:nodeType="class">
						<!-- The taxonomy node's label.-->
						<drm:NodeName>Any string value</drm:NodeName>
						<!-- A description of the associated term/object.-->
						<drm:Definition>Any string value</drm:Definition>
						<!-- A collection of keywords and/or keyphrases associated with this taxonomy node.-->
						<drm:Terms>
							<!-- A keyword and/or keyphrase associated with this taxonomy node.-->
							<drm:Term>Any string value</drm:Term>
						</drm:Terms>
						<!-- A list of node children.-->
						<drm:NodeChildren>
							<!-- A node in a taxonomy.-->
							<drm:Node rdf:id="http://any-uri" drm:nodeType="class">
								<!-- The taxonomy node's label.-->
								<drm:NodeName>Any string value</drm:NodeName>
								<!-- A description of the associated term/object.-->
								<drm:Definition>Any string value</drm:Definition>
								<!-- A collection of keywords and/or keyphrases associated with this taxonomy node.-->
								<drm:Terms>
									<!-- A keyword and/or keyphrase associated with this taxonomy node.-->
									<drm:Term>Any string value</drm:Term>
								</drm:Terms>
								<!-- A list of node children.-->
								<drm:NodeChildren>
									<!-- A node in a taxonomy.-->
									<drm:Node rdf:id="http://any-uri" drm:nodeType="class">
										<!-- The taxonomy node's label.-->
										<drm:NodeName>Any string value</drm:NodeName>
										<!-- A description of the associated term/object.-->
										<drm:Definition>Any string value</drm:Definition>
										<!-- A collection of keywords and/or keyphrases associated with this taxonomy node.-->
										<drm:Terms>
											<!-- A keyword and/or keyphrase associated with this taxonomy node.-->
											<drm:Term>Any string value</drm:Term>
										</drm:Terms>
									</drm:Node>
								</drm:NodeChildren>
							</drm:Node>
						</drm:NodeChildren>
					</drm:Node>
				</drm:Nodes>
			</drm:Taxonomy>
			<!-- A collection of ExternalTaxonomyRefs-->
			<drm:ExternalTaxonomyRefs>
				<!-- Points to subject taxonomies created using an approved standard.  For a standard to be approved, it must be:
 
1.  An open, widely implemented standard, available free-of-charge and unencumbered by royalty or patent claims, or a standard implemented by a government agency
2.  A well-documented, durable standard (i.e., under version/change control, well-documented, backward compatibility, etc.)
3.  Provides semantics for modeling, at a minimum, taxonomy/thesaurus nodes/terms and relationships between taxonomy nodes/terms (generic, whole-part, equivalence, associative).
4.  Provides semantics for assigning an identifier per element that is guaranteed unique within the particular model.
 
Candidate standards for implementing data exchange services include:
 
1. XTM (XML topic maps)
2. NASA taxonomy Format (http://nasataxonomy.jpl.nasa.gov/xml.htm)
3. MeSH taxonomy Format (http://www.nlm.nih.gov/mesh/xmlmesh.html)
4. UDDI tModel (http://uddi.org/taxonomies/UDDI_Registry_tModels.htm)
5. XBRL taxonomy (http://www.xbrl.org/Taxonomies/)
6. Simple Knowledge Organisation System (SKOS) (http://www.w3.org/2004/02/skos/)-->
				<drm:ExternalTaxonomyRef drm:href="http://any-uri" rdf:id="http://any-uri" drm:representationFormat="Any string value">
				</drm:ExternalTaxonomyRef>
			</drm:ExternalTaxonomyRefs>
		</drm:Taxonomies>
		<!-- A container for elements that map taxonomy nodes in a DRM instance to FEA reference model elements.-->
		<drm:FEAMapping>
			<!-- Documents a specific link from an element in this DRM instance (usually a taxonomy node) to a unique element in a particular FEA reference model as defined in the FEA-RMO ontology, which is found at http://colab.cim3.net/file/work/SICoP/project/fea-rmo/fea-rmo.html.-->
			<drm:FEAReferenceModelMap drm:from="Any string value" drm:to="Any string value" drm:referenceModel="BRM" />
		</drm:FEAMapping>
		<!-- DataStandard: A list of standards.-->
		<drm:DataStandards>
			<!-- A standard that applies to this DRM submission. If a well-known, widely-implemented standard, this can be the URI to the authoritative documentation for this standard.  Otherwise, it should be the URI pointing to a XSLT stylesheet that transforms a document conforming to the standard in question to the equivalent DRM XML syntax.-->
			<drm:Standard drm:href="http://any-uri" rdf:id="http://any-uri" />
		</drm:DataStandards>
	</drm:DataContext>
</drm:DataReferenceModel>
