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

Organization

Geopolitical Entities, Names, and Codes

Friday, August 17, 2012

Chief Information Officer

IC Technical Specifications

Geopolitical Entities, Names, and Codes

Overview


This IC enterprise CVE encoding specification defines XML elements and attributes, associated structures and relationships, mandatory and cardinality requirements, permissible values, and constraint rules for representing Geopolitical Entities, Names, and Codes (GENC) data concepts.

This specification supports ISO-3166-1 (which replaced FIPS 10-4), moving from a two-character country code base to a three character code.  This profile is considered to be the authoritative set of country codes and names for use by the Federal Government for information exchange.  Although GENC will use ISO-3166 code elements whenever possible, they may be modified where necessary to comply with U.S. law and U.S. government recognition policy.

This specification provides a subset of the permissible GENC codespaces and code values that are used in the IC.  Specifically, this specification only utilizes the short Uniform Resource Number (URN) based codespaces with the three-character codes.

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

 

Technical Specification Downloads


Latest Approved Version


Mission Requirements

Many IC encoding specifications use Controlled Vocabulary Enumerations (CVEs) to define allowable values for various elements and attributes.  However, over time several encoding specifications became dependent on the same list of values and dual (or more) maintenance was required to keep the lists aligned.  Changes to a specification's CVEs also caused an entire version of that specification to be created.

To prevent these two situations from occurring, a new type of encoding specification, the CVE Encoding Specification (CES), was created to decouple the vocabulary from the specifications.  Each CES contains one or more CVEs and optionally a master schema defining

Fine Access Control

Friday, August 17, 2012

Chief Information Officer

IC Technical Specifications

Fine Access Control

Overview


Any IT system performing entity authentication may use this specification to determine if a given entity should be granted access to a specific piece of data.

This specification applies to the IC, as defined by the National Security Act of 1947, as amended, and ICS 500-27, Collection and Sharing of Audit Data,  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.

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

 

Technical Specification Downloads


Latest Approved Version


Mission Requirements

Information sharing within the national intelligence enterprise relies on the ability to discover and access intelligence content from any location, at any time, with as few restrictions as possible.  ICD 501 empowers analysts, operators, and collectors with a wide range of capabilities for discovering, using, and sharing content within the IC and with partners.  This authority comes with great responsibility, a responsibility that must be tracked, analyzed, and reported on.

The auditing of person and non-person entities within the IC protects the nation from abuse, voluntary or involuntary disclosure, as well as insider and outside threats.  The audit specification is derived from the fundamental mission requirement to track and audit the discovery and access of intelligence content and information resources within the IC enterprise.

Community Shared Resources

Friday, August 17, 2012

Chief Information Officer

IC Technical Specifications

Community Shared Resources

Overview


This IC enterprise data encoding specification defines detailed implementation guidance for Community Shared Resources (CSR) to sub-set the large possible combinations of specification versions.  CSRs are systems or services that live on the enterprise and are made available for use by the community.  This specification defines the minimum relationship sets of specifications mandatory for consuming systems (CSRs that receive data), and the allowed relationship sets for production systems (CSRs that transmit data).

This standard supports Executive Order (EO) 13526, Classified National Security Information which "prescribes a uniform system for classifying, safeguarding, and declassifying national security information," across national security disciplines, networks, services, and data.

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

 

Technical Specification Downloads


Latest Approved Version


Mission Requirements

All systems at the enterprise level need to be able to send and receive with a common vocabulary to permit understanding.  Since the decoupling of the IC Technical Specifications from one another, permitting them to revision independently, the potential combinations of versions of the specifications that can be mixed and matched together have grown exponentially.  This puts a large burden on data producers and consumers on the enterprise to be able to produce and/or interpret all possible combinations. The ever-growing number of combinations leads to a need to have a minimal number of sets of combinations that CSRs must be able to produce/consume to relieve them of the infeasible burden of being able to produce/consume all possible combinations.

CDR: Specification Framework

Friday, August 17, 2012

Chief Information Officer

IC Technical Specifications

CDR: Specification Framework

Overview

This Content, Discovery and Retrieval (CDR) Specification Framework document provides guidance for ensuring consistency and interoperability in the development of CDR Service Specifications. Generally, it describes the structure and content for CDR Service Specifications including the description of their key characteristics and a decomposition of key behaviors in the context of various environmental and technical considerations.

This CDR Specification Framework document is intended to provide both CDR Service Specification developers/authors and CDR service developers/implementers guidance for developing and implementing CDR Service Specifications. Specifically, this Specification Framework describes the Interface models and related behavior for each Service Specification and how they should be codified. For CDR Service Specification developers/authors, the framework provides the structure and content guidance for how CDR Service Specifications should be documented. For CDR service developers/implementers, the framework provides the common implementation and behavior guidance that, coupled with a specific CDR Service Specification, enables the realization of a CDR service.

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 specification framework is maintained by the IC Chief Information Officer via the Services Coordination Activity (SCA) and Content Discovery and Retrieval Integrated Product Team (CDR IPT).


Interface Encoding Specification Downloads


Latest Approved Version:

 

Previous Version:

Value Proposition

This CDR Specification Framework describes in greater detail the CDR Components and capabilities presented in the CDR Reference Architecture. It is meant to provide guidance in enough detail to enable interoperability among independent implementations without otherwise constraining the implementation itself. In this vein, this document describes inputs and outputs to each component in the context of the expected behavior that clarifies what is needed as inputs, outputs, and other effects that are expected to be produced. It does not, however, specify the details of the internal implementation processing.

Virtual Coverage

Friday, August 17, 2012

Chief Information Officer

IC Technical Specifications

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.

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