Root node of the DRM XML instance document. RELATIONSHIPS: None The standard and/or protocol providing access control for a Query Point. RELATIONSHIPS: None A characteristic of an Entity whose value may be used to help distinguish one instance of an Entity from other instances of the same Entity. RELATIONSHIPS: - An Attribute is constrained by a Data Type; A container for Attribute elements. RELATIONSHIPS: None FIPS 199 "availability" impact level. RELATIONSHIPS: None FIPS 199 "confidentiality" impact level. RELATIONSHIPS: None An entity (person or organization) that consumes data that is supplied by a Supplier. RELATIONSHIPS: None A managed container for data. Examples include a relational database, Web site, document repository, directory or data service. RELATIONSHIPS: - A Data Asset provides a management context for one or more Digital Data Resources; A reference to a DataAsset element contained within the same DRM instance. RELATIONSHIPS: None A container for DataAssetRef elements. RELATIONSHIPS: None A container for DataAsset elements. RELATIONSHIPS: None The Data Context standardization area of the DRM. The Data Context standardization area facilitates discovery of data through an approach to the categorization of data according to taxonomies, and provide linkages to the other FEA reference models. RELATIONSHIPS: None The Data Description standardization area of the DRM. The Data Description standardization area provides a means to richly describe data, thereby supporting its discovery and sharing. RELATIONSHIPS: None The Data Sharing standardization area of the DRM. The Data Sharing standardization area describes the sharing and exchange of data, where sharing may consist of ad-hoc requests (such as a one-time query of a particular data asset), scheduled queries, and/or exchanges characterized by fixed, re-occurring transactions between parties. Data sharing is enabled by capabilities provided by both the Data Context and Data Description standardization areas. RELATIONSHIPS: None A person or organization responsibile for managing a specific set of data resources. RELATIONSHIPS: - A Data Steward manages a Data Asset; A constraint on the type of data that an instance of an Attribute may hold (e.g. "date", "string", "float" or "integer"). RELATIONSHIPS: None Name of department with which a Data Steward is associated. RELATIONSHIPS: None General description element used in various places. RELATIONSHIPS: None A container for StructuredDataResourceRef, UnstructuredDataResourceRef, and SemiStructuredDataResourceRef elements (which are collectively considered to be Digital Data Resource references). NOTE: This element is used for Data Assets, but not for Topics - even though the DRM 2.0 abstract model lists a relationship between a Topic and Digital Data Resources. The reason for this is that the relationship from Data Digital Resources to Topics is represented in each of the Digital Data Resource container elements (i.e. StucturedDataResources, SemiStucturedDataResources, and UnstucturedDataResources), in a "TopicRefs" element. This was done because it makes more sense to list Topics by which an artifact is categorized where the artifact itself is described, rather than vice-versa. RELATIONSHIPS: None A container for DigitalDataResource elements. RELATIONSHIPS: None A discrete and unique electronic aggregation of data produced with the intent of conveying information. Specifically for the DRM, a Document is a file containing Unstructured and/or Semi-Structured Data Resources. RELATIONSHIPS: - A Document may contain one or more Unstructured Data Resources; - A Document may contain one or more Semi-structured Data Resources; - A Document refers to one or more Entities; A container for Document elements. RELATIONSHIPS: None Employee ID for a Data Steward. RELATIONSHIPS: None The network endpoint for a Query Point. RELATIONSHIPS: None A container for Entity elements. RELATIONSHIPS: None A reference to an Entity element contained within the same DRM instance. RELATIONSHIPS: None A container for EntityRef elements. RELATIONSHIPS: None An association between two Entities. RELATIONSHIPS: None A container for EntityRelationship elements. RELATIONSHIPS: None The frequency at which an exchange is estimated to occur. RELATIONSHIPS: None A container for ExchangePackage elements. RELATIONSHIPS: None A container for externally referenced Entity elements. RELATIONSHIPS: None A container for externally referenced ExchangePackage elements. RELATIONSHIPS: None A container for externally referenced Taxonomy elements. RELATIONSHIPS: None A container for externally referenced UnstructuredDataResource elements. RELATIONSHIPS: None According to FIPS 199, potential impact levels on agency operations, assets, or individuals should there be a breach in security due to the loss of confidentiality, integrity, or availability. RELATIONSHIPS: None A boolean flag indicating whether or not a Data Asset supports or provides Geospatial data. RELATIONSHIPS: None Date that a Data Steward became associated with a Data Asset. RELATIONSHIPS: None A container for "inline" Entity elements (i.e. those that appear in the DRM instance as opposed to being externally referenced). RELATIONSHIPS: None A container for "inline" ExchangePackage elements (i.e. those that appear in the DRM instance as opposed to being externally referenced). RELATIONSHIPS: None A container for "inline" Taxonomy elements (i.e. those that appear in the DRM instance as opposed to being externally referenced). RELATIONSHIPS: None A container for "inline" UnstructuredDataResource elements (i.e. those that appear in the DRM instance as opposed to being externally referenced). RELATIONSHIPS: None FIPS 199 "integrity" impact level. RELATIONSHIPS: None The number of seconds needed to pass a message to an access point. Usually measured from the initiation of a request to the receipt of the response. RELATIONSHIPS: None General URI element used in various places to specify the Web address of an externally referenced artifact (such as an external taxonomy). RELATIONSHIPS: None The minimal level of encryption needed to pass data to and from an access point. RELATIONSHIPS: None The agency providing primary stewardship for a Data Asset. RELATIONSHIPS: None The Web address of an electronic definition that defines the requirements for the payload (data) that is exchanged between a Supplier and a Consumer. Examples include XML Schema and EDI transaction sets. RELATIONSHIPS: None The manner by which a payload (message) is transported from sender to receiver. It is typically, but not necessarily, a computer networking protocol. NOTE: In the future, this may be represented as an enumerated list. RELATIONSHIPS: None A URI pointing to the person or organization to contact for more information regarding a 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. RELATIONSHIPS: None A URI pointing to an electronic representation (e.g. XML document, Web page) of contact information for the primary contact for a Supplier or Consumer. RELATIONSHIPS: None Specifies Quality of Service (QoS)-related information for a Query Point. RELATIONSHIPS: None A standard query language that can be used to access the data within a Data Asset. RELATIONSHIPS: None A container for QueryLanguage elements. RELATIONSHIPS: None An endpoint that provides an interface for accessing and querying a Data Asset. A concrete representation of a Query Point is a specific URL at which a query Web Service may be invoked. RELATIONSHIPS: - A Query Point returns a result set specified in an Exchange Package; - A Query Point accesses one or more Data Assets; A reference to a QueryPoint element contained within the same DRM instance. RELATIONSHIPS: None A container for QueryPointRef elements. RELATIONSHIPS: None A container for QueryPoint elements. RELATIONSHIPS: None Specifies security-related information for a Query Point. RELATIONSHIPS: None Specifies reliable messaging-related requirements for a Query Point. NOTE: In the future, this will may contain multiple sub-elements, each of which relates to a single capability (such as duplicate message elimination). RELATIONSHIPS: None A URI indicating a data standard to which an externally referenced artifact (such as a Taxonomy) complies. RELATIONSHIPS: None An electronic resource containing data that has characteristics of both structured and unstructured data, such as an e-mail (with structured data such as sender and subject, and unstructured text). RELATIONSHIPS: - A Semi-Structured Data Resource is a type of Digital Data Resource; - A Semi-Structured Data Resource (because it is a Digital Data Resource) is categorized by one or more Topics; A reference to a SemiStructuredDataResource element contained within the same DRM instance. RELATIONSHIPS: None A container for SemiStructuredDataResourceRef elements. RELATIONSHIPS: None A container for SemiStructuredDataResource elements. RELATIONSHIPS: None The status of an Exchange Package (e.g. complete or in-progress) where "complete" indicates that the Exchange Package is set up in production, and "In-progress" indicats that the Exchange Package is not yet in production but is in the process of being prepared for production. RELATIONSHIPS: None An electronic resource containing data that is described via the E-R (Entity-Relationship) or class model, such as logical data models and XML documents. Structured data is organized in well-defined semantic “chunks” called entities. RELATIONSHIPS: - A Structured Data Resource is a type of Digital Data Resource; - A Structured Data Resource (because it is a Digital Data Resource) is categorized by one or more Topics; A reference to a StructuredDataResource element contained within the same DRM instance. RELATIONSHIPS: None A container for StructuredDataResourceRef elements. RELATIONSHIPS: None A container for StructuredDataResource elements. RELATIONSHIPS: None The date that a DRM instance was submitted. May include time as well. RELATIONSHIPS: None A container for all information related to a DRM submission. RELATIONSHIPS: None Any submitter-determined string that uniquely (according to the submitter) differentiates a DRM submission from previous DRM submissions by the submitter. RELATIONSHIPS: None The Government agency, bureau, office, or department that submits a DRM instance. RELATIONSHIPS: None An entity (person or organization) that supplies data to a Consumer. Note that a Supplier may or may not be the original producer of the data. For this reason, the name “Producer” was not used. RELATIONSHIPS: - A Supplier produces an Exchange Package; A container for Supplier and Consumer elements. RELATIONSHIPS: None Denotes whether or not a data source 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). RELATIONSHIPS: None A container for Taxonomy elements. RELATIONSHIPS: None A keyword and/or keyphrase associated with a taxonomy Topic. RELATIONSHIPS: None A container for Term elements. RELATIONSHIPS: None A category within a Taxonomy; often synonymous with "node". A Topic is the central concept for applying context to data. RELATIONSHIPS: - A Topic is related to one or more other Topics (inline Taxonomies only); - A Topic categorizes one or more Digital Data Resources; A reference to a Topic element contained within the same DRM instance. RELATIONSHIPS: None A container for TopicRef elements. RELATIONSHIPS: None An association between two Topics. RELATIONSHIPS: None A container for TopicRelationship elements. RELATIONSHIPS: None A container for Topic elements. RELATIONSHIPS: None An indication of the message pattern that is used for transactions defined by an Exchange Package (e.g. Query/Response, Publish/Subscribe, etc.). NOTE: Additional values for the enumerated list associated with this element may be added in the future. RELATIONSHIPS: None Type of Data Asset – e.g. database, Web site, registry, directory, data service, etc. NOTE: In the future, this may be represented as an enumerated list. RELATIONSHIPS: None A reference to an UnstructuredDataResource element contained within the same DRM instance. RELATIONSHIPS: None A container for UnstructuredDataResourceRef elements. RELATIONSHIPS: None A container for UnstructuredDataResource elements. RELATIONSHIPS: None The type of entity that the Consumer represents (e.g. Agency, system, individual, etc.). RELATIONSHIPS: None A reference to an Entity element contained within the same DRM instance. NOTE: This attribute is used to depict relationships among Entities, while the "EntityRef" element is used to depict relationships between other concepts (e.g. Documents) and Entities. This attribute was created for reduced verbosity in depicting relationships among Entities. RELATIONSHIPS: None General identifier attribute used in various places. RELATIONSHIPS: None A reference to an identifier within the same DRM instance. RELATIONSHIPS: None General name attribute used in various places. RELATIONSHIPS: None The type of entity that the Supplier represents (e.g. Agency, system, individual, etc.). RELATIONSHIPS: None A reference to a Topic element contained within the same DRM instance. NOTE: This attribute is used to depict relationships among Topics while the "TopicRef" element is used to depict relationships between other concepts (e.g. Entities) and Topics. This attribute was created for reduced verbosity in depicting relationships among Topics. RELATIONSHIPS: None The regularity of an exchange represented by an Exchange Package (e.g. Daily, Weekly, etc.). Indicates the units that correspond to the value for the Exchange Frequency (e.g. 2 times daily, once a month, etc.). RELATIONSHIPS: None An abstraction for a person, place, object, event, or concept described (or characterized) by common Attributes. RELATIONSHIPS: - An Entity is related to one or more other Entities; A description of a specific recurring data exchange between a Supplier and a Consumer. RELATIONSHIPS: - An Exchange Package refers to one or more Entities; - An Exchange Package is disseminated to a Consumer; - An Exchange Package queries one or more Query Points; A collection of controlled vocabulary terms (Topics) organized into a hierarchical structure. RELATIONSHIPS: None An electronic resource containing data that is of a more free-form format, such as multimedia files, images, sound files, or unstructured text. Unstructured data does not necessarily follow any format or hierarchal sequence, nor does it follow any relational rules. RELATIONSHIPS: - An Unstructured Data Resource is a type of Digital Data Resource; - An Unstructured Data Resource (because it is a Digital Data Resource) is categorized by one or more Topics; An abstraction for a person, place, object, event, or concept described (or characterized) by common Attributes. RELATIONSHIPS: - An Entity contains one or more Attributes (inline Entities only); - An Entity is related to one or more other Entities; A description of a specific recurring data exchange between a Supplier and a Consumer. RELATIONSHIPS: - An Exchange Package refers to one or more Entities; - An Exchange Package is disseminated to a Consumer; - An Exchange Package queries one or more Query Points; - An Exchange Package refers to a Payload Definition (inline Exchange Package only); A collection of controlled vocabulary terms (Topics) organized into a hierarchical structure. RELATIONSHIPS: - A Taxonomy contains one or more Topics (inline Taxonomies only); An electronic resource containing data that is of a more free-form format, such as multimedia files, images, sound files, or unstructured text. Unstructured data does not necessarily follow any format or hierarchal sequence, nor does it follow any relational rules. RELATIONSHIPS: - An Unstructured Data Resource is a type of Digital Data Resource; - An Unstructured Data Resource (because it is a Digital Data Resource) is categorized by one or more Topics;