Published: 03 December 2012

National Intelligence Council

Global Trends 2030: Alternative Worlds

Global Trends 2030 is intended to stimulate thinking about the rapid and vast geopolitical changes characterizing the world today and possible global trajectories over the next 15 years.  In depth research, detailed modeling and a variety of analytical tools drawn from public, private and academic sources were employed in the production of this report.  Visit this page for continuing coverage of Global Trends 2030.

Download Global Trends 2030

This edition of Global Trends is the most widely disseminated in its history. The report is available for the most popular content platforms and e-readers. Brief talking points are available here.

Events & Live Coverage

On December 10th, 2012 at 1PM Eastern the Atlantic Council will kick off its Global Trends 2030: US Leadership in a Post-Western World, event. The two day conference is being held in partnership with the National Intelligence Council.

BEGINNING AT 1PM 12/10/2012:   View a live video stream of the Atlantic Council Global Trends event.

FOLLOW THE NIC ON TWITTER:  For coverage of the Atlantic Council Global Trends event and more.

Media Coverage

Global Trends has a global audience. We're keeping track of worldwide media coverage of the Global Trends 2030 report.

View the latest GT2030 articles.

Video

Dr. Mathew J. Burrows, counselor, National Intelligence Counsel and principal author of the NIC's Global Trends 2030 report discusses "Alternative Worlds" in a series of ODNI videos.
To view Dr. Burrows Q&A responses, please vist ODNI's YouTube page.

Additional Resources

See additional research on natural resources used to support the NIC’s Global Trends 2030: Alternative Worlds

Published: 17 October 2012

Chief Information Officer

IC Technical Specifications

XML Data Encoding Specification for Trusted Data Format

Overview

This XML Data Encoding Specification for Trusted Data Format (IC-TDF.XML) defines detailed implementation guidance for using Extensible Markup Language (XML) to encode IC-TDF data.

Information sharing within the national intelligence enterprise will increasingly rely on information assurance metadata (including enterprise data headers) to allow interagency access control, automated exchanges, and appropriate protection of shared intelligence. A structured, verifiable representation of security metadata bound 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), Information Resource Metadata (IRM), and Enterprise Data Header (EDH) XML specifications of the Intelligence Community Enterprise Architecture (ICEA) Data Standards. The IC Trusted Data Format XML specification further expands on this body of work, adapting and extending it as necessary for TDF to function as the IC submission format for binding assertion metadata with data resource(s). This TDF functionality supports the IC way ahead strategy of implementing secure cloud-based information exchange and discovery on the IC Enterprise

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 Standards Coordination Activity (DSCA) and Common Metadata Standards Tiger Team (CMSTT).

Technical Specification Downloads

Latest Approved Public Release:

• XML Data Encoding Specification for Trusted Data Format (V2021-NOV - Standalone Package)
• XML Data Encoding Specification for Trusted Data Format (V2021-NOV - Convenience Package)
• XML Data Encoding Specification for Trusted Data Format (V2021-NOV - Light Package)

Mission Requirements

Information sharing within the national intelligence enterprise will increasingly rely on information assurance metadata (including enterprise data headers) to allow interagency access control, automated exchanges, and appropriate protection of shared intelligence. A structured, verifiable representation of security metadata bound 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), Information Resource Metadata (IRM), and Enterprise Data Header (EDH) XML specifications. The IC Trusted Data Format XML specification further expands on this body of work, adapting and extending it as necessary for TDF to function as the IC submission format for binding assertion metadata with data resource(s). This TDF functionality supports the IC way ahead strategy of implementing secure cloud-based information exchange and discovery on the IC Enterprise. 

Published: 03 December 2012

National Intelligence Council

Global Trends

• Global Trends 2025
• Global Governance 2025
• Mapping the Global Future: 2020 Project
• Global Trends 2015

Published: 05 October 2012

Chief Information Officer

IC Technical Specifications

CDR Retrieve

Overview

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

The Retrieve Component, as defined by the Intelligence Community/Department of Defense (IC/DoD) CDR Specification Framework, serves as a “pull” mechanism to access the information resource.

The REST Retrieve Component relies on mechanisms that are already well established in the internet infrastructure:

• HTTP GET method - HTTP/HTTPS – http://www.w3.org/Protocols/
• HTTP Result Codes (maintained by Internet Assigned Numbers Authority – IANA) Hypertext Transfer Protocol (HTTP) Status Code Registry – http://www.iana.org/assignments/http-status-codes
• MIME Types (maintained by IANA): MIME types http://www.ietf.org/rfc/rfc2045.txt

The SOAP Retrieve specification covers the following aspects of a SOAP-based Retrieve Component:

• Service Interface defines the base SOAP constructs to expressing inputs, outputs, and faults
• Implementation provides additional implementation guidance beyond the behavior and interface guidance
• Reference Documentation provides references to other CDR and community artifacts (i.e., CDR Reference Architecture)

The Retrieve Component supports the retrieval for a specified resource from a Content Collection. The Retrieve Component, as defined, can only support returning a resource directly to the requestor. It cannot redirect output to a component other than the requestor. In addition, no special handling instructions (e.g., routing) may be specified.

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

Technical Specification Downloads

Latest Approved Public Release:

• IC-DoD REST Interface Specification for CDR Retrieve (V2 - Standalone Package (Release Date: 3 Oct 2012))
• IC-DoD SOAP Interface Specification for CDR Retrieve (V2 - Standalone Package (Release Date: 3 Oct 2012))

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 retrieval of an identified content resource from the Content Collection in which it is stored.
• Initiate delivery of the retrieved resource to the requestor or to a designated alternate location using the Deliver Component.