Root node of the DRM XML instance document. Container for all metadata related to one particular instance of a DRM submission. 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 assets clearly, concisely, and unambiguously. This element contains definitions for structured, semi-structured, and unstructured data. Data described via the E-R (Entity-Relationship) or class model. A collection of entities. A named template used to describe a population of items with common characteristics. Like the set of persons, places or things. A collection of ResourceRefs. A ResourceRef links an object with a related resource. 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. A list of data asset references. A collection of characteristics that describe the entity (e.g., "first_name", "last_name", etc.). A property belonging to an entity (e.g., "first_name", "last_name", etc.). A collection of relationships (associations) between entities. An association between two entities. In a relationship between two entities, this element is used to describe the target entity. A pointer to the unique ID of the associated data asset, either in the DRM instance (rdf:id) or in an external DRM instance (DRM_Instance_URI#rdf:id). A collection of 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. 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. A collection of ExternalResourcesRefs. These objects are pointers to external files that aggregate unstructured or semistructured resources (e.g., RSS feeds). 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. A collection of 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 reused 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. Data that have characteristics of both structured and unstructured data. A collection of data assets. An aggregated, managed container. A database, system, application, or other electronic entity that produces and/or houses data. FIPS 199 potential impact levels. 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. A collection of exchange packages. A description of a specific information exchange between organizations. 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). 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). This element points to an XML artifact that defines/implements the actual message type exchanged between the sender and receiver. This will typically be in the form of a W3C XML Schema (XSD) file. In other scenarios, this might point to a WSDL (Web Services Description Language) file, or a file describing another type of messaging standard, such as EXDL (Emergency Data Exchange Language). Frequencies per unit this exchange is estimated to occur. A collection of entity references. Associates the ExchangePackage with one or more entities defined in the "StructuredData" section of a DRM instance. 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. A description of the requirements for electronic access to a data asset and its data. An endpoint (network or otherwise) providing an interface for querying a data asset. The format of the payload returned by the access point in response to a query. A container categorizing security-related information. Quality-of-service (QoS)-related information. A container for elements that implement the data context portion of the DRM meta-model. A collection of taxonomies. An information model (typically hierarchical) that defines the scope of a knowledge domain. A collection of 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/) A collection of taxonomy nodes. A node in a taxonomy. A collection of NodeRefs. NodeRefs are pointers from an object to a taxonomy node. 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: <meta name="drm:NodeRef" content="http://cosine.cim3.net/file/work/DRM/data_dictionary/examples/DRM_Instance_Example_OJP_IT.xml#182 /> A collection of keywords and/or keyphrases associated with this taxonomy node. A list of node children. A container for elements that map taxonomy nodes in a DRM instance to FEA reference model elements. 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. DataStandard: A list of standards. 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. Government agency, bureau, office, or department that submits this DRM instance. Date that this DRM instance was submitted. May include time as well as date. 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. The agency providing primary stewardship for the data asset. 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. A boolean flag indicating whether or not a particular data asset supports or provides Geospatial data. 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). The type of data asset (e.g. website, database, document repository, etc.). A URI pointing to the person or organization to contact for more information regarding the data asset. 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. Valid values can be "L, M, H" (for low, moderate, high). Valid values can be "L, M, H" (for low, moderate, high). Valid values can be "L, M, H" (for low, moderate, high). The manner by which the payload (message) is moved from sender to receiver. It is typically, but not necessarily, a computer networking protocol. Type of exchange, such as: Query/response, publish/subscribe, etc. Legal values include (To Be Published). Status of exchange - e.g. in progress or complete. Legal values include (To Be Published). The network endpoint for this access point. The standard query mechanism that will be used to access the data within this data asset - e.g. SQL-92, CQL (Z39.50), XQuery, Boolean Operators, WSDL, HTTP GET, etc. Legal values include (To Be Published). 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). The minimal level of encryption needed to pass data to and from this particular access point. Legal values include (To Be Published). 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. Information relating to reliable messaging capabilities. The taxonomy node's label. A description of the associated term/object. A keyword and/or keyphrase associated with this taxonomy node. The address (absolute or relative) at which an object is reachable. An element's descriptive name An attribute's data type. This must be a valid XSD data type. Describes the type of relationship in a NodeRef or ResourceRef element. Legal values include: "instanceOf", "subclassOf", "partOf", "equivalentTo", and "relatedTo". A pointer to the rdf:id of the taxonomy node (or other DRM element) associated with the FEA RM element specified in the "to" attribute. The "to" value in the each link below represents an FEA reference model category URL from the FEA-RMO ontology, which is found at http://colab.cim3.net/file/work/SICoP/project/fea-rmo/fea-rmo.html The number of times in a given time period that a specific exchange occurs. Time period is specified in the unit attribute. The time period for information exchanges. Indicates whether or not the parent datasourceRef is the authoritative source for the entity in question. Boolean element, true or false. This attribute points to the particular exchange package that defines the result format (response payload) for the access point in question. Points to the data standard ID defining the format of the external entity reference. This attribute references the key field for a given Entity when elaborating a relationship between two entities The cardinality of a given relationship. One of the following values: zero, one, unbounded, 1 or more, n (any whole number), n-n (any specific range of whole numbers), and 0-1 (zero to one). The type of entity that the Sender element value represents, with valid choices of: "Agency", "System", or "Individual" (or "A", "S", "I"). The type of entity that the Recipient element value represents, with valid choices of: "Agency", "System", or "Individual" (or "A", "S", "I"). Defines a given node's type. Legal values include "collection", "class", and "instance." The FEA reference model to which this node is being linked. Legal values include PRM, BRM, SRM, and TRM. Defines what type of key (if any) this attribute is. Legal values include "PK" (primary key), "FK" (foreign key), "any key", or "none".