Subscribe to ODNI news via emailSubscribe via RSStumblr offtwitter off 2Like ODNI on FacebookView ODNI photos on FlickrVisit ODNI’s YouTube Channelscribd off

Organization

CDR: Search

Friday, August 17, 2012

Chief Information Officer

IC CIO Enterprise Integration & Architecture

CDR: Search

Overview

This IC/DoD enterprise encoding specification defines requirements and provides guidelines for the realization of the Content Discovery and Retrieval (CDR) Search component as both a RESTful, OpenSearch [OS] web service and using the SOAP binding, hereafter termed a Search Service. This component provides a common interface and behavioral model for IC and DoD content collections, enabling content consumers to discover relevant content resources from disparate collections across the IC/DoD Enterprise. The content of this specification describes the Search Service’s behavior, interface and other aspects in detail, providing enough information for Search Service providers and consumers to create and use CDR-conformant Search services.

The Search service exposes a single Search operation that is responsible for three activities that underpin Content Discovery capabilities: search, result presentation, and results paging. A Search service’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. Results normally contain information needed for a consumer to retrieve or otherwise use the referenced resource.


Value Proposition

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).

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:
  • Searching through content and metadata in multiple formats as specified by the consumer, such as image files and textual documents.
  • Searching through information content that is static, dynamic, structured and unstructured.
  • Enable searching through and appropriately processing of information content and metadata at different classification levels, and with different handling caveats; information which could be located on different security domains.
  • Searching through natural language content (probably in many different languages) or highly formatted content such as geospatial or temporal content. (Data sources can be active [current, dynamically changing] or historic [static], each containing different data types).



Latest Approved Versions



Previous Versions

  • IC/DoD REST Interface Encoding Specification for CDR Search, Version 1.1 (12 May 11)
  • IC/DoD SOAP Interface Encoding Specification for CDR Search, Version 1.1 (12 May 11)

CDR: Query Management

Friday, August 17, 2012

Chief Information Officer

IC CIO Enterprise Integration & Architecture

CDR: Query Management

Overview

This IC/DoD enterprise encoding specification defines requirements and provides guidelines for the realization of the Content Discovery and Retrieval (CDR) Query Management component as a web service using both a RESTful, OpenSearch [OS] and SOAP style binding, hereafter termed the Query Management (QM) Service, as a web service using the SOAP style binding. The Query Management (QM) Component, as defined by the “IC/DoD Content Discovery and Retrieval (CDR) Specification Framework” , is a CDR Component that manages Saved Searches and may initiate search requests based on Saved Searches. It describes the external service interfaces and the internal activities that provide service behaviors so that service providers and consumers can create and use CDR-compliant Query Management Services.

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). ). The six functions listed below provide QM service consumers with a coordinated set of capabilities that support managing and using both searches and search related information. This specification mandates the generic interfaces that a QM consumer would utilize to manage and use a Saved Search:
  • Create –The Create function is used to insert a new Saved Search into the QM Collection.
  • Read – The Read function is used to retrieve a Saved Search from the QM Collection.
  • Update – The Update function is used to change a Saved Search in the QM Collection.
  • Delete – The Delete function is used to logically remove a Saved Search from the QM Collection.
  • Execute – The Execute function enables a QM consumer to execute (run) a Saved Search at the location specified by the Target Search Capability. To process an execute request, the Query Management Service retrieves the Target Search Capability (the location of the Search Service) and the Search Request from the Saved Search. This information is then used to initiate the Search. This capability SHOULD leverage the CDR Search approach to effect the execution of a Saved Search.
  • Search – The Search function enables a prospective consumer to interrogate the QM Collection on the basis of anything to be found in the Saved Search Bundle or the Saved Search Description to determine if a suitable search has already been created. Generic search terms can be used to provide functionality that provides a ‘list’ of the contents of the QM Collection. This capability SHOULD leverage the CDR Search discovery approach.

Latest Approved Versions

CDR: Deliver

Friday, August 17, 2012

Chief Information Officer

IC CIO Enterprise Integration & Architecture

CDR: Deliver

Overview

This IC/DoD enterprise encoding specification defines requirements and provides guidelines for the realization of the Content Discovery and Retrieval (CDR) Deliver Component as a web service using both the SOAP messaging protocol and REST style binding, hereafter termed a Deliver service. This component provides a common interface and behavioral model for IC and DoD content collections, enabling content consumers to deliver relevant content resources from disparate collections across the IC/DoD Enterprise. The content of this specification describes a Deliver service’s interface and other aspects in detail, providing enough information for Deliver service providers and implementers to create CDR-compliant Deliver services.

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:
The SOAP Deliver Service exposes a Deliver function. While the function is often used in concert with delivering the results of a Content Discovery search, it may be used in general to process any compliant Deliver instructions. The Deliver function can be used in a few different patterns:
  • 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)
The Deliver Service facilitates the transfer of a content resource to a specified destination. In its simplest form, the Deliver Service will take a consumer-supplied payload and send it to another consumer as specified by the delivery destination and properties. The Deliver Service may include additional (interim) processing, including but not limited to compression, encryption, or conversion.

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.


Latest Approved Versions



CDR: Brokered Search

Friday, August 17, 2012

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


Previous Versions

 

Intelligence Publications

Friday, July 27, 2012

Chief Information Officer

IC CIO Enterprise Integration & Architecture

Intelligence Publications

Data Encoding Specification for Intelligence Publications

Overview

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

Current Version:
  • XML Data Encoding Specification for Intelligence Publications V12 (PUBS.XML.V12) 10 Apr 13

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.

You are leaving DNI.gov

You have selected to open
http://www.anotherwebsite.com

If you would like to not see this alert again, please click the
"Do not show me this again" check box below