Subscribe to ODNI news via emailSubscribe via RSSListen to ODNI PodcastsLike ODNI on FacebookFollow ODNI on TwitterView ODNI photos on FlickrVisit ODNI’s YouTube Channel

Organization

Virtual Coverage

Friday, August 17, 2012

Chief Information Officer

IC CIO Enterprise Integration & Architecture

Virtual Coverage

Overview

This XML Data Encoding Specification for Virtual Coverage (VIRT.XML) defines detailed implementation guidance for using Extensible Markup Language (XML) to encode virtual coverage data. This Data Encoding Specification (DES) defines the XML elements and attributes, associated structures and relationships, mandatory and cardinality requirements, and permissible values for representing VIRT data concepts using XML.

This specification is applicable to the Intelligence Community (IC) and information produced by, stored, or shared within the IC. This DES may have relevance outside the scope of intelligence; however, prior to applying outside of this defined scope, the DES should be closely scrutinized and differences separately documented and assessed for applicability.

This specification applies to the IC, as defined by the National Security Act of 1947, as amended; and such other elements of any other department or agency as may be designated by the President, or designated jointly by the Director of National Intelligence (DNI) and the head of the department or agency concerned, as an element of the IC. Joint and Coalition forces may use this specification but it is not required.

This specification is maintained by the IC Chief Information Officer via the Data Coordination Activity (DCA) and Common Metadata Standards Tiger Team (CMSTT).



Current Version


Mission Requirements

Information sharing within the national intelligence enterprise will increasingly rely on describing virtual locations in shared intelligence. A structured, verifiable representation of virtual coverage to the intelligence data is required in order for the enterprise to become inherently "smarter" about the information flowing in and around it. Such a representation, when implemented with other data formats, improved user interfaces, and data processing utilities, can provide part of a larger, robust information assurance infrastructure capable of automating some of the management and exchange decisions today being performed by human beings.

The Intelligence Community (IC) has standardized the various classification and control markings established for information sharing within the Information Security Markings (ISM) and Need-To-Know (NTK) XML specifications of the Intelligence Community Enterprise Architecture (ICEA) Data Standards. The Virtual Coverage XML specification combines elements of the ISM and NTK specifications and extends them to virtual coverage needs.

Multi Audience Collections

Friday, August 17, 2012

Chief Information Officer

IC CIO Enterprise Integration & Architecture

Multi Audience Collections

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 packaging specific types of electronic information resources that are tailored for select audiences and grouped together for exchange. Examples of this type of information resource may be something as familiar as a tearlined cable message, each tearline of which is tailored for a specific audience based on classification, or as complex as a packaging together of many customized variants of the same textual product for dissemination on JWICS.

The types of electronic information resources that can be packaged with MAT.XML currently includes: 1) textual information resources conformant with PUBS.XML, and 2) information resource metadata records conformant to IRM.XML. 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.

Compliance with this specification is measured against all aspects of the technical and documentary artifacts contained within the specification release package.

The IC Chief Information Officer maintains this specification via the Data Coordination Activity (DCA) and Common Metadata Standards Tiger Team (CMSTT).


Current Version


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, and 501, among others. These policies cover topics such as "write for maximum utility", "responsibility to provide", and "information sharing".

 Broad information sharing within the intelligence enterprise can be facilitated by the creation, identification, packaging, and sharing of information resources tailored by the producer to support different audiences (e.g., variants). This tailoring is commonly based on, among other things, characteristics of the information, such as classification or topical interest.

The creation of multiple classification variants (e.g., TOP SECRET, SECRET, and UNCLASSIFIED versions of the same intelligence product) and sharing of those variants across secure network channels allows a producer to communicate more information to intended and unintended consumers across the broader information sharing enterprise in a way that reliably protects classified information and intelligence sources and methods.

The existence of variants today is quite common across the intelligence enterprise. This is a routine practice in cable message traffic in which tearlines, delimited blocks of text, are used to capture each variant which are then separated (often manually) prior to delivery. Producers also routinely create intelligence product variants for their different customers, but these are typically created as different documents which are stored, managed, and delivered separately.

MAT introduces a packaging structure for these separately tagged variants that allows for the efficient exchange, if not also storage, of these related variants in a form that is bound and managed together. Binding the variants together reduces the confusion that exists today when a consumer searches the enterprise and finds multiple versions of the same product and cannot discern the relationship between the products; thereby leading to a possible source of circular intelligence reporting.

Additionally, if one producer packages and shares all of the versions of a product they have created in the form of a MAT on JWICS, then other producers and consumers would not only better appreciate what other variants exist and where they may have been shared, but they would also be able to share appropriate variants with other downstream consumers who are also supporting our intelligence mission.

CDR: Reference Architecture

Friday, August 17, 2012

Chief Information Officer

IC CIO Enterprise Integration & Architecture

CDR: Reference Architecture

Overview

This IC/DoD enterprise Content Discovery and Retrieval Reference Architecture (CDR RA) provide conceptual and contextual guidance to architects, engineers, and developers tasked to implement CDR specifications. The CDR Reference Architecture (RA) is the keystone artifact for the overall set of guidance artifacts. The primary content of the CDR RA is the definition of an extensible set of capabilities and components that are realized via service specifications. It also describes various architecture interaction patterns and the specific technical framework to enable robust, scalable, and repeatable implementations across varying business and mission boundaries.

The CDR RA defines two primary capabilities - content discovery and content retrieval and is comprised of six core CDR components: Search, Brokered Search, Retrieve, Describe, Deliver, and Query Management that provide these capabilities. The CDR RA describes an architecturally driven approach for guiding the IC/DoD Enterprise towards enabling content discovery and retrieval.

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.

This reference architecture 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 CDR reference architecture defines two distinct, but inter-related capabilities: Content Discovery, and Retrieval.
  • Content Discovery provides consumers with the ability to discover the existence of potentially relevant content resources and content collections from across the IC/DoD Enterprise. Content Discovery also enables consumers to discover valuable metadata about content resources to support making them visible, accessible, understandable, and trusted.
  • Retrieval provides consumers the ability to retrieve and route specific content resources. To do so, content providers are to ensure their content is accessible to the Enterprise.



Latest Approved Version

 

Previous Version

 

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

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