Organization
CDR: Deliver
Chief Information Officer
IC CIO Enterprise Integration & Architecture
CDR: Deliver
Overview
The REST Deliver Service, as defined by the Intelligence Community/Department of Defense (IC/DoD) CDR Specification Framework, serves as a “push” mechanism to send information resources. The Deliver Service relies on mechanisms that are already well established in the internet infrastructure:
- HTTP Handling Method (Post):
- HTML: http://en.wikipedia.org/wiki/HTML and
- HTTP/HTTPS: http://www.w3.org/Protocols/
- HTTP Status Codes (maintained by Internet Assigned Numbers Authority – IANA): Hypertext Transfer Protocol (HTTP) Status Code Registry – http://www.iana.org/assignments/http-status-code
- MIME Types (maintained by IANA): MIME types http://www.ietf.org/rfc/rfc2045.txt
- Deliver content provided by the entity invoking the service to a default or specified recipient(s)
- Deliver content obtained as the result of a previous query to default or specified recipient(s)
- Deliver based upon additionally specified criteria (e.g. time, event)
This specification supports Intelligence Community Directive 501(ICD 501), Discovery, Dissemination or Retrieval of Information within the Intelligence Community, which establishes policies for (1) discovery, and (2) dissemination or retrieval of intelligence and intelligence-related information collected, or analysis produced by the Intelligence Community.
Compliance with this specification is measured against all aspects of the technical and documentary artifacts contained within the specification release package. This specification is maintained by the IC Chief Information Officer via the Services Coordination Activity (SCA) and Content Discovery and Retrieval Integrated Product Team (CDR IPT).
Value Proposition
This specification is designed to fulfill a number of requirements in support of the transformational efforts of the Intelligence Community and Department of Defense Enterprise(IC/DoD). Features of this specification are to:
- Enable a content resource to be delivered to a specified location which may or may not be the requesting component.
- Provide additional processing of the content to make it suitable for delivery to its destination and delivery path to be used.
- On behalf of the consumer, retrieve the requested content and then deliver to the specified location.
CDR: Brokered Search
Chief Information Officer
IC CIO Enterprise Integration & Architecture
CDR: Brokered Search
Overview
This IC/DoD enterprise encoding specification defines requirements and provides guidelines for the realization of the Content Discovery and Retrieval (CDR) Brokered Search Component as a web service using both the SOAP messaging protocol and the RESTful OpenSearch [OS] standard (intended to provide minimal requirements for implementing an OpenSearch search broker), hereafter termed a Brokered Search service. The Brokered Search Component serves as the primary mechanism to 1) facilitate the distribution of queries to applicable/relevant Search Components and content collections. These Search Components expose and 2) aggregate the results returned individually into a single uniform results set. The content of this specification provides enough information for Broker Search Component providers and implementers to create CDR-compliant Brokered Search Components, the specification describes a Brokered Search Component’s behavior, interface, and other aspects in detail.
The Brokered Search Component uses the basic functionality described by the Search Component for a single search. Additional inputs and outputs are defined as needed to support the four activities that underpin Brokered Search capabilities: brokered search coordination, source identification, search component invocation, and federation results processing. A Search component’s results are resource metadata rather than actual content resources. In the context of Search, resource metadata generally refers to a subset of a resource’s available metadata, not the entire underlying record. The Search Component returns metadata about a resource, which may sometimes describe the underlying resource (e.g., an image), while other times representing a sub-set of the data that makes up a resource (e.g., a collection of attributes). In some cases, the metadata returned from an instantiation of the Search function and the Retrieve function, which returns a resource itself, may happen to be the same, though this is considered an edge condition. Some of the information contained within each Search result may provide the information necessary for a consumer to retrieve or otherwise use a resource.
This specification supports Intelligence Community Directive 501(ICD 501), Discovery, Dissemination or Retrieval of Information within the Intelligence Community, which establishes policies for (1) discovery, and (2) dissemination or retrieval of intelligence and intelligence-related information collected, or analysis produced by the Intelligence Community.
Compliance with this specification is measured against all aspects of the technical and documentary artifacts contained within the specification release package. This specification is maintained by the IC Chief Information Officer via the Services Coordination Activity (SCA) and Content Discovery and Retrieval Integrated Product Team (CDR IPT).
Value Proposition
This specification is designed to fulfill a number of requirements in support of the transformational efforts of the Intelligence Community and Department of Defense Enterprise(IC/DoD). Features of the Brokered Search Specification are to:
- Facilitate the distribution of queries to applicable/relevant Search Components and content collections these Search Components expose.
- Aggregate the results returned individually into a single, uniform results set which is returned to the Consumer Component.
Latest Approved Versions
- IC/DoD REST Encoding Specification for CDR Brokered Search, Version 1.1 (12 May 11)
- IC/DoD SOAP Encoding Specification for CDR Brokered Search, Version 1.1 (12 May 11)
Previous Versions
- IC/DoD Content Discovery & Retrieval Brokered Search Service Specification for OpenSearch Implementations, Version 1 (25 Oct 10)
- IC/DoD Content Discovery & Retrieval Brokered Search Specification for SOAP Implementations, Version 1 (26 Oct 10)
Intelligence Publications
Chief Information Officer
IC CIO Enterprise Integration & Architecture
Intelligence Publications
Data Encoding Specification for Intelligence PublicationsOverview
This IC enterprise data encoding specification defines XML elements and attributes, associated structures and relationships, mandatory and cardinality requirements, permissible values, and constraint rules for representing electronic textual information resources. Textual information resources consist primarily of text supplemented by interspersed non-textual information. Examples include assessments, studies, estimates, compilations, reports, and other document-oriented information.
This specification contains tagging structures for information resource metadata, mixed textual and media content found in the body of publications, source reference citations, classification and control markings, and knowledge assertions. Compliance with this specification is measured against all aspects of the technical and documentary artifacts contained within the specification release package.
This specification changed names and numeric designators multiple times since its inception in the late 1990's. Each version listed below supersedes the prior version.
This specification is maintained by the IC Chief Information Officer via the Data Coordination Activity (DCA) and Common Metadata Standards Tiger Team (CMSTT).
Data Encoding Specification Downloads
Prior Versions:
Mission Requirements
This specification is designed to fulfill a number of requirements in support of the transformational efforts of the Intelligence Community. Many of these requirements are articulated in IC Directives 203, 206, 208, 501, and 710, among others. Features of this specification are provided to support:
- Improving publication and dissemination efficiency by reducing the cost and time for performing manual and complex rendering, manipulation, and content transformation.
- Facilitating discovery and exchange of intelligence publications between collectors, all-source analysts, and consumers.
- Capturing overall security marking metadata in order to support attribute-and clearance-based information management practices, such as: secure collaboration, content management, content and portion-level filtering of discovery results, and content transfers across security domains.
- Capturing source reference citations to provide intelligence producers the ability to systematically analyze how and at what frequency the data they gather or produce is being used.
- Capturing and retaining a greater understanding of an intelligence publications meaning, purpose, genesis, and characteristics as identified by a human or service.
Abstract Data Definition
Chief Information Officer
IC CIO Enterprise Integration & Architecture
Abstract Data Definition
Intelligence Community Abstract Data Definition
Overview
The Intelligence Community Abstract Data Definition (IC.ADD) defines the high-level types of data and metadata that are important to the IC.
The selected or developed physical Data Encoding Specifications established by the IC map to the IC.ADD's abstract data elements providing a means to relate or translate different physical data encodings.The abstract data elements defined in the IC.ADD are not meant to be implementable within enterprise systems. IC elements should implement the physical Data Encoding Specifications that implement these abstract data elements.
This specification is maintained by the IC Chief Information Officer via the Data Coordination Activity (DCA) and Common Metadata Standards Tiger Team (CMSTT).
Data Encoding Specification Downloads
Current Version:
- Intelligence Community Abstract Data Definition, Version 2 and Signature Memo (09 Aug 2011)
Prior Versions:
- Intelligence Community Abstract Data Definition, Version 1 (07 May 2010) — Complete Package
Need-To-Know Metadata
Chief Information Officer
IC CIO Enterprise Integration & Architecture
Need-To-Know Metadata
XML Data Encoding Specification for Need-To-Know Metadata
Overview
This Data Encoding Specification (DES) defines the XML elements and attributes; associated structures and relationships; mandatory and cardinality requirements; and permissible values for representing NTK metadata associated with an information resource or part of an information resource using XML. NTK.XML can be incorporated into other Data Encoding Specifications.
NTK metadata facilitates automated systems making a “need-to-know” (NTK) access determination about an information resource. These metadata are used to represent the system-specific properties assigned to an information resource that will be used, in conjunction with information about the user, and possibly other information, to determine the user’s access to the data. A single information resource may include multiple occurrences of these metadata in order to specify NTK information according to multiple, different access systems.
Compliance with this specification is measured against all aspects of the technical and documentary artifacts contained within the specification release package.
This specification is maintained by the IC Chief Information Officer via the Data Coordination Activity (DCA) and Common Metadata Standards Tiger Team (CMSTT).
Data Encoding Specification Downloads:
Current Version:
Previous Version:
- XML Data Encoding Specification for Need-To-Know Metadata (Keywords: NTK.XML) - Version 6, (27 Feb 2012)
- XML Data Encoding Specification for Need-To-Know Metadata (Keywords: NTK.XML), Version 5 (9 Aug 2011)
- XML Data Encoding Specification for Need-To-Know Metadata (Keywords: NTK.XML), Version 4 (11 April 2011)
Mission Requirements
This DES provides a common specification for the means by which a data producer can encode, in their data, the information that an access system needs in order to determine how to grant access. This DES enables a comprehensive capability to appropriately protect data across the enterprise while also allowing access by individuals having appropriate NTK. The nature of the information to be encoded will vary system by system and could include lists of individuals or groups permitted access, descriptions of subject matter in terms defined by the access system, or other traits to be used in evaluating the access an individual has to the data.
This DES provides that common specification. Currently the particulars of any access system’s data needs are not defined. Details for specifying access information and documenting access parameters for particular access systems are to be added in the near future. The systems for which access information will be recorded and constrained will be expanded as their applicability’s are identified to the enterprise.
