anchor.diff:  "DI2E-SVCV4-A","DI2E SvcV-4 Alignment","true","true","true","false","2.6.2.3","2.6.2.3 Database Definition","<b>Definition:</b>Database Definition enables the creation of the database and its structure, i.e., tables, indexes, triggers, etc., and the ability to modify the database structure.<br><b>Description:</b>Database Definition includes capabilities to create database, drop database, create tables, drop tables, alter tables, create indexes, drop indexes, etc.",
   "DI2E-SVCV4-A","DI2E SvcV-4 Alignment","true","true","true","false","2.6.2.4","2.6.2.4 Database Administration","<b>Definition:</b>Database Administration enables the overall management of existing database repositories in a organization.<br><b>Description:</b>Database Administration includes capabilities to backup a database, recover a database, upgrade a database, restart a database, monitor database performance, tune database parameters, etc.",
   "DI2E-SVCV4-A","DI2E SvcV-4 Alignment","true","true","true","false","2.6.2.5","2.6.2.5 Data Object Tagging","<b>Definition:</b>Data Object Tagging tags data with various forms of content topic metadata for information discovery and automated dissemination purposes.<br><b>Description:</b>Data tagging allows users to organize information more efficiently by associating pieces of information with tags, or keywords.  A tag is a non-hierarchical keyword or term assigned to a piece of information such as an image, file or record. This kind of metadata helps describe an item and allows it to be found again by browsing or searching.",
  -"DI2E-SVCV4-A","DI2E SvcV-4 Alignment","true","true","true","false","2.6.3","2.6.3 Workspace Management","<b>Definition:</b>Workspace Management services enable users to efficiently and locally establish, update, and share data in a persistent state between work sessions.<br><b>Description:</b>Workspace Management services enable users to efficiently and locally establish, update, and share data in a persistent state between work sessions.     This lets users then �start where they left off� between sessions, quickly view and analyze certain information conditions, or readily share their work session information with others.   Other benefits include:<br><br>� Removing the need for developers to create their own persistence solutions for multiple applications<br>� Common access to certain data layer content<br>� Removes certain product specific dependences (i.e. Oracle Database)<br>� Creates a �contract� for sharing data between components<br>� Enables customization of data structure based on user needs",
  -"DI2E-SVCV4-A","DI2E SvcV-4 Alignment","true","true","true","false","2.6.3.1","2.6.3.1 Manage Workspace","<b>Definition:</b>Manage Workspace services enable a user to add documents a new workspace session (Create), get documents (Read) documents in their workspace, edit (Update) the relationships among documents in their workspace, or remove (Delete) documents in their workspace.<br><b>Description:</b>Manage Workspace services enable a user to add documents a new workspace session (Create), get documents (Retrieve) documents in their workspace, edit (Update) the relationships among documents in their workspace, or remove (Delete) documents in their workspace.  The typical paradigm is to store documents in a hierarchical structure that contains �parents� and �children�. Using the manage workspace service, users can then Create/Retrieve/Update/Delete (CRUD) documents using this structure in a persistent state for use between various work sessions.    <br><br>Typical operations are broken down as follows:<br>Create - add documents to the workspace<br>Retrieve � get a document, a document�s children, a documents parents, documents by type, or children documents by type<br>Update � change the content of a document, or modify hierarchical relationships among documents<br>Delete � remove individual documents, or entire �families� of documents",
  +"DI2E-SVCV4-A","DI2E SvcV-4 Alignment","true","true","true","false","2.6.3","2.6.3 Workspace Management","<b>Definition:</b>Workspace Management services enable users to efficiently and locally establish, update, and share data in a persistent state between work sessions.<br><b>Description:</b>Workspace Management services enable users to efficiently and locally establish, update, and share data in a persistent state between work sessions.     This lets users then  start where they left off  between sessions, quickly view and analyze certain information conditions, or readily share their work session information with others.   Other benefits include:<br><br>  Removing the need for developers to create their own persistence solutions for multiple applications<br>  Common access to certain data layer content<br>  Removes certain product specific dependences (i.e. Oracle Database)<br>  Creates a  contract  for sharing data between components<br>  Enables customization of data structure based on user needs",
  +"DI2E-SVCV4-A","DI2E SvcV-4 Alignment","true","true","true","false","2.6.3.1","2.6.3.1 Manage Workspace","<b>Definition:</b>Manage Workspace services enable a user to add documents a new workspace session (Create), get documents (Read) documents in their workspace, edit (Update) the relationships among documents in their workspace, or remove (Delete) documents in their workspace.<br><b>Description:</b>Manage Workspace services enable a user to add documents a new workspace session (Create), get documents (Retrieve) documents in their workspace, edit (Update) the relationships among documents in their workspace, or remove (Delete) documents in their workspace.  The typical paradigm is to store documents in a hierarchical structure that contains  parents  and  children . Using the manage workspace service, users can then Create/Retrieve/Update/Delete (CRUD) documents using this structure in a persistent state for use between various work sessions.    <br><br>Typical operations are broken down as follows:<br>Create - add documents to the workspace<br>Retrieve   get a document, a document s children, a documents parents, documents by type, or children documents by type<br>Update   change the content of a document, or modify hierarchical relationships among documents<br>Delete   remove individual documents, or entire  families  of documents",
   "DI2E-SVCV4-A","DI2E SvcV-4 Alignment","true","true","true","false","2.6.3.2","2.6.3.2 Share Workspace","<b>Definition:</b>Share Workspace services enable a user to send or retrieve their workspace files to other workspace component users.<br><b>Description:</b>Share Workspace services enable a user to send or retrieve their current or saved workspace files to other workspace component users.   Workspace content can be content currently in use, or a saved session of workspace content from an earlier session.   <br><br>The method of identifying candidate workspace users or methods of transmission are not prescribed as part of this service definition, but an illustrative example would be a workspace management component that enabled the storing e-mail addresses as one family within the workspace documents, then the ability to select e-mail addresses from this list and then optionally send entire workspace, or families within the overall workspace, to the selected set of e-mail addresses.",
   "DI2E-SVCV4-A","DI2E SvcV-4 Alignment","true","true","true","false","3.1.2","3.1.2 Workflow Management","<b>Definition:</b>Workflow Management enables coordination and cooperation among members of an organization, helping them to perform complex mission execution by optimizing, assigning, and tracking tasks across the enterprise.<br><b>Description:</b>Workflow Management services are a sequence of connected steps that describe a repeatable chain of operations, can include multiple processes, and can stem across organizations or agencies. The workflows represent the mission by means of elementary activities and connections among them. The activities represent fully automated tasks executed by computer or tasks assigned to human actors executed with the support of a computer. Workflow Management provides a consistent, streamlined, and traceable process for users to follow, and monitors the progress of who has performed the work, the status of the work, and when the work has been completed at all times.",
   "DI2E-SVCV4-A","DI2E SvcV-4 Alignment","true","true","true","false","3.1.2.1","3.1.2.1 Define Workflows","<b>Definition:</b>The Define Workflows service enables a workflow designer to capture and maintain enterprise workflows in human-readable and machine-readable formats.<br><b>Description:</b>Define Workflows models workflow using intuitive, visual tools and a model notation. Workflow definition helps to ensure control in execution of workflows to ensure both consistency in output and that no step is skipped. Each workflow represents a series of anticipated events by illustrating tasks, and connections among them. The tasks represent fully automated activities executed by computer or tasks assigned to human actors executed with the support of a computer. In DoD environments, workflows are most commonly defined in Business Process Modeling Notation (BPMN).",
  
positive.code: "DI2E-SVCV4-A","DI2E SvcV-4 Alignment","true","true","true","false","3.1.3.3","3.1.3.3 Intelligence Source Selection","<b>Definition:</b>Intelligence Source Selection services support the review of mission requirements for sensor and target range, system responsiveness, timelines, threat, weather, and reporting requirements.   to identify and determine asset and/or resource availability and capability.  Source selection applies to all types of collection sources (i.e. GEOINT, HUMINT, SIGINT, etc.).<br><b>Description:</b>none",
  "DI2E-SVCV4-A","DI2E SvcV-4 Alignment","true","true","true","false","3.1.3.2","3.1.3.2 Sensor Cataloging","<b>Definition:</b>Sensor Cataloging allows clients to request information about sensors and servers, add or delete sensor information from an external catalog,  subscribe or unsubscribe to a sensor status, or add, modify, or delete sensor metadata from a sensor instance.<br><b>Description:</b>Sensor Cataloging allows clients to request information about sensors and servers, add or delete sensor information from an external catalog,  subscribe or unsubscribe to a sensor status, or add, modify, or delete sensor metadata from a sensor instance.    The client can receive metadata documents describing a server's abilities, search for sensors instances on a registry server instance, and receive sensor instance descriptions from the server for either one or multiple sensors.       <br><br>The client can also insert sensor metadata into the registry server,  update sensor metadata on the registry server, or remove sensor metadata from the registry server.   In addition, the client can establish or remove a link between a sensor registry entry instance and an external OGC catalog.   Finally the client can get the sensor status, insert a sensor status, subscribe to a sensor status, or cancel a sensor status subscription.              <br><br>[This service is supported by the OGC SWE SIR discussion paper.]",
  "DI2E-SVCV4-A","DI2E SvcV-4 Alignment","true","true","true","false","3.1.3.1","3.1.3.1 Collection Requirements Planning","<b>Definition:</b>Collection Requirements Planning provides editing and visibility into the evolution of tasking and collection-related artifacts<br><b>Description:</b>Collection Requirements Planning aggregates information such as asset tasking lists as they mature into ISR Synch Matrix and Proposed Collection Plans.    Using this service collection requirements managers can view, add, delete, or update requirements for a specific collection.  It also allows them to view the mapping of collection requirement to collection task.    It also allows tasking managers to view, add, delete, or update tasking for a specific sensor.<br><br>Both tasking requirements managers and task managers can view mapping of the collection tasks to collection requirements, collection results, and status of collection tasks.",
  "DI2E-SVCV4-A","DI2E SvcV-4 Alignment","true","true","true","false","3.1.3","3.1.3 Planning","<b>Definition:</b>The family of services that support the Intelligence Planning Process.<br><b>Description:</b>Operation planning occurs in a networked, collaborative environment, which requires iterative dialogue among senior leaders, concurrent and parallel plan development, and collaboration across multiple planning levels. The focus is on developing plans that contain a variety of viable, embedded options (branches and sequels).  This facilitates responsive plan development and modification, resulting in �living� plans (i.e., the systematic, on-demand, creation and revision of executable plans, with up-to-date options, as circumstances require). This type of adaptive planning also promotes greater involvement with other US agencies and multinational partners.",
  "DI2E-SVCV4-A","DI2E SvcV-4 Alignment","true","true","true","false","3.1.1.2","3.1.1.2 RFI Management","<b>Definition:</b>The service to create, deconflict, monitor, and disseminate Intelligence Requests for Information (RFI)<br><b>Description:</b>An RFI is a specific time-sensitive ad hoc requirement for information or intelligence<br>products, and is distinct from standing requirements or scheduled intelligence production. An RFI can<br>be initiated at any level of command, and will be validated in accordance with the combatant command�s<br>procedures. An RFI will lead to either a production requirement if the request can be answered with<br>information on hand or a collection requirement if the request demands collection of new information.<br>Collection planning and requirement management are major activities during planning and direction.",
  "DI2E-SVCV4-A","DI2E SvcV-4 Alignment","true","true","true","false","3.1.1.1","3.1.1.1 PIR Management","<b>Definition:</b>PIR Management services support management of the Priority Intelligence Requirement (PIR) process .  Supports: <br>1. Deriving PIRs from CCIRs<br>2. Consolidating and recommending PIR nominations<br>3. Deriving Information Requirements from Intelligence Requirements and PIRs<br>4. Identifying EEIs which will answer PIRs<br><b>Description:</b>PIR Management services assist a commander in deriving Priority Intelligence Requirements (PIR) to support a mission, tracking, updating, consolidating existing PIRs, and turning those PIRs into specific requirements that can be used for intelligence collection planning.  The PIR Management service works with the Collection Requirements Planning service to task and plan collection activities.",
  "DI2E-SVCV4-A","DI2E SvcV-4 Alignment","true","true","true","false","3.1.1","3.1.1 Define and Prioritize Requirements","<b>Definition:</b>The family of services to define, document, and prioritize intelligence requirements<br><b>Description:</b>N/A",
  "DI2E-SVCV4-A","DI2E SvcV-4 Alignment","true","true","true","false","3.1","3.1 Planning and Direction","<b>Definition:</b>The Planning & Direction line includes services that provide the ability to synchronize and integrate the activities of collection, processing, exploitation, analysis and dissemination resources to meet BA information requirements.<br><b>Description:</b>The Planning & Direction line includes services that provide the ability to synchronize and integrate the activities of collection, processing, exploitation, analysis and dissemination resources to meet BA information requirements. This includes the following sub-areas: Define and Prioritize Requirements  � The ability to translate national through tactical objectives and needs into specific information and operational requirements.  Develop Strategies  � The ability to determine the best approach to collect, process, exploit, analyze, and disseminate data and information to address requirements and predict outcomes. Task and Monitor Resources  � The ability to task, track, direct, and adjust BA operations and their associated resources to fulfill requirements. Evaluation  � The ability to assess the results of BA operations and products to ensure that user requirements are being met. (Ref. Joint Service Areas, JCA 2010 Refinement, 8 April 2011)<br>Families in this line: ASSET MANAGEMENT and PLANNING and REPORTING.",
  "DI2E-SVCV4-A","DI2E SvcV-4 Alignment","true","true","true","false","0","0 DI2E","<b>Definition:</b>The DI2E SvcV-4 documents services that are needed for the DI2E to achieve the desired level of service reuse and interoperability .<br><b>Description:</b>The services that exist within the Defense Intelligence Enterprise that are governed by the DI2E.  The services shall be developed in a service oriented manner, be registered and accessible in the Enterprise Registry, and be tested and certified for reuse.",
  "DI2E-SVCV4-A","DI2E SvcV-4 Alignment","true","true","true","false","1","1 Infrastructure Services","<b>Definition:</b>The functions/services that support the Enterprise and don't usually have a direct relationship to the mission or business processes.<br><b>Description:</b>Infrastructure Services are fundamental to the DI2E.  This consistent set of services across the DI2E is foundational to future SOA-based enterprise services.     <br><br>Specific service lines include:<br><br>   � Enterprise Management<br>   � Web Service Security<br>   � Web Service Discovery<br>   � Messaging, and <br>   � Orchestration",
  "DI2E-SVCV4-A","DI2E SvcV-4 Alignment","true","true","true","false","1.4.2.2","1.4.2.2 Protocol Mediation","<b>Definition:</b>Protocol Mediation provides the ability to manage service communication format between sender and receiver.<br><b>Description:</b>The Protocol Mediation service provides transformation and processing of service communication between sending and receiving services.  One example is mediating e-mail messages between POP to IMAP formats.    Another example is chat mediation between IRC or XMPP formats. Mediation between SOAP and REST is another example.",
  "DI2E-SVCV4-A","DI2E SvcV-4 Alignment","true","true","true","false","1.4.2.1","1.4.2.1 Execution Engine","<b>Definition:</b>An execution engine takes the definition of a service orchestration (e.g., BPEL) and executes the process<br><b>Description:</b>Service orchestrations are only definitions of how services should be executed in sequence to complete a given business process. Execution of the orchestration requires some form of engine that will run the orchestrated process and return a result to the user. Most existing execution engines execute processes defined in Business Process Execution Language (BPEL). Other possibilities are available, including newer version of Business  Process Modeling Notation that are executable; mashup frameworks, and similar technologies",
  "DI2E-SVCV4-A","DI2E SvcV-4 Alignment","true","true","true","false","1.4.2","1.4.2 Orchestration Execution","<b>Definition:</b>Orchestration execution performs the ordered calling of services as designed in service orchestration models (see orchestration modeling service).<br><b>Description:</b>Orchestration execution makes in-sequence calls to services, holds intermediate inputs/outputs, handles exceptions, monitors execution status, and provides an interface for user presentation. <br><br>Common orchestration execution features include: W3C XHTML/CSS conformance, templating, class autoloading, object based design, nested groups with multiple assigned permissions, form design tools including help and error messages, labels, validation rules, inherited authorization, and macros support.",
  
negative.code: "DI2E-SVCV4-A","DI2E SvcV-4 Alignment","true","true","true","false","3.4.1.3","3.4.1.3 Resection","<b>Definition:</b>Resection adjusts image support data when the sensor model data is unknown, incomplete, or imprecise.<br><br><b>Description:</b>Resection uses Digital Point Positioning Database (DPPDB) stereo reference image pairs or other reference imagery, possibly combined with a reference Digital Elevation Map (DEM), to adjust the support data of an image acquired by a less accurate source.  <br><br>The service ingests the image coordinates of tie points in all the images including reference images and the acquired image that is to be resected as well as instantiated sensor models.  The sensor model of the acquired image has adjustable parameters and enhancing the values of these adjustable sensor model parameters is the objective of the Resection service.<br><br>The Resection service uses the reference data to compute 3D geolocations for the selected tie points.  It then performs cycles of bundle adjustment (i.e. least squares sensor model parameter value and tie point coordinate value adjustment) until  it achieves convergence with the measured image coordinates for all the 3D reference points mapped onto the acquired image coordinate space. The resulting adjusted sensor model parameter values for the acquired image constitute the resection results.",
  "DI2E-SVCV4-A","DI2E SvcV-4 Alignment","true","true","true","false","3.4.1.2","3.4.1.2 Triangulation","<b>Definition:</b>Triangulation calculates a geolocation estimate based on multiple image collections acquired from distinct collection angles. <br><br><b>Description:</b>Triangulation performs a geolocation estimate of a photo identifiable point based on multiple image collections acquired from distinct collection angles.  In this process it combines four distinct algorithmic functions: 1) least squares adjustment of sensor support data along with selected image plane tie or control point measurements that are each common to two or more images, 2) rigorous uncertainty propagation calculations, 3) geolocation computations using a triangulation method, and 4) blunder detection to discard point measurement outliers.<br><br>To initiate a triangulation the service is presented with a set of images and associated image point coordinates.  Image sensor models and coordinates are also provided from each image for the point to be geolocated.    Adjustable parameters include image collection geometries and (sometimes) sensor internal parameters, such as lens focal length or lens distortion.<br>",
  "DI2E-SVCV4-A","DI2E SvcV-4 Alignment","true","true","true","false","3.4.1.1","3.4.1.1 Change Detection","<b>Definition:</b>Change Detection identifies feature changes via a pixel analysis between two images of the same area.<br><b>Description:</b>Change detection ingests two precisely co-registered images and identifies differences in pixels collected before and after some interval of time at the same geographic location.   Typically the changes in pixel values must exceed a user defined thresholds including registration uncertainty ""guard band"", size, color, and/or shape in order to screen out noise/clutter changes.   Output is an image formatted mask that identifies which pixels have significant changes between the two images.",
  "DI2E-SVCV4-A","DI2E SvcV-4 Alignment","true","true","true","false","3.4.1","3.4.1 GEOINT Analysis","<b>Definition:</b>GEOINT Analysis services describe, assess, and visually depict physical features and geographically referenced activities on the Earth.<br><b>Description:</b>GEOINT Analysis services provide intelligence information ( imagery, imagery intelligence, multi-spectral analysis, hyper-spectral analysis, etc.) for geographically referenced features and activities.   Specific services include:<br>   Change Detection - which identifies pixel-by-pixel differences between two images of the same area.<br>    Source Selection - which presents a user with sets of images that can satisfy a geopositioning precision requirement.<br>    Sensor Model Instantiation - which generates sensor model state data from image metadata. <br>    Triangulation  - which calculates a geolocation estimate based on multiple image collections acquired from distinct collection angles. <br>    State Service - which converts image support data into a related sensor model state string.<br>    Resection  - which adjusts image support data when the sensor model data is unknown, incomplete, or imprecise.<br>    Geomensuration  - which computes image based mensuration calculations using image points measured from an image.<br>    DPPDB Mensuration - which performs geopositioning by aligning directly to DPPDB metadata.<br>    Image Registration - which matches points in a selected image to one or more control images to increase the accuracy of geoposition coordinates.<br>    Moving Target Indicator (MTI) - which links 'dots' of point locations into tracks that indicate historical & projected direction and speed.<br>    Topographical Survey - which derives and represents elevation and terrain characteristics from reports and data. <br>    Automatic Target Recognition - which identifies specified entities on an image using image processing techniques. <br>    Emitter Geolocation - which determines the likely position of an emitter source from emitter intercept data.",
  "DI2E-SVCV4-A","DI2E SvcV-4 Alignment","true","true","true","false","3.4","3.4 Analysis, Prediction and Production","<b>Definition:</b>The Analysis, Prediction & Production line includes services that provide the ability to integrate, evaluate, interpret, and predict knowledge and information from available sources to develop intelligence and forecast the future state to enable situational awareness and provide actionable information.<br><b>Description:</b>The Analysis, Prediction & Production line includes services that provide the ability to integrate, evaluate, interpret, and predict knowledge and information from available sources to develop intelligence and forecast the future state to enable situational awareness and provide actionable information.  This includes the following sub-areas: Integration   The ability to identify, assimilate and correlate relevant information from single or multiple sources.  Evaluation   The ability to provide focused examination of the information and assess its reliability and credibility to a stated degree of confidence.  Interpretation   The ability to derive knowledge and develop new insight from gathered information to postulate its significance.  Prediction   The ability to describe the anticipated future state of the operational/physical environment based on the depiction of past and current information.  Product Generation   The ability to develop and tailor intelligence, information, and environmental content and products per customer requirements.  (Ref. Joint Service Areas, JCA 2010 Refinement, 8 April 2011)<br>Families in this line: GEOINT ANALYSIS, SIGINT ANALYSIS, HUMINT ANALYSIS, MASINT/AGI ANALYSIS, and TARGETING SUPPORT.",
  "DI2E-SVCV4-A","DI2E SvcV-4 Alignment","true","true","true","false","3.3.6.7","3.3.6.7 BDA/CDA","<b>Definition:</b>This component performs Battle Damage Assessment (BDA) analysis. BDA is the estimate of damage resulting from the application of lethal or nonlethal military force. BDA is composed of physical damage assessment, functional damage assessment, and target system assessment.  <br><br>GCCS Spec/USMTF message<br><b>Description:</b>N/A",
  "DI2E-SVCV4-A","DI2E SvcV-4 Alignment","true","true","true","false","3.3.6.6","3.3.6.6 Target Mensuration","<b>Definition:</b>Target Mensuration services provide the measurement of a feature or location on the earth to determine an absolute latitude, longitude, and height.<br><b>Description:</b>N/A",
  "DI2E-SVCV4-A","DI2E SvcV-4 Alignment","true","true","true","false","3.3.6.5","3.3.6.5 Target List","<b>Definition:</b>The Target List service maintains the various target lists that are kept as part of the target strike management process.<br><b>Description:</b>The Target List service provides methods to retrieve a prioritized list of target lists by type; query for an existing list by name; create or remove target lists;  and add, remove, or edit targets in existing target lists.  Targets can also be transferred from one target list to another list type in accordance with the target management process.<br><br>Examples of target list types include: 1) the Joint Integrated Prioritized Target List (JIPTL) which are targets prioritized to be struck; 2) the Air Tasking Order (ATO); 3) on-call targets; 4) no-strike targets; 5) nominated targets; and 6) targets scheduled for battle damage assessment (BDA).",
  