#1418 Marine Links Kristine Marcy Common Alerting Protocol to Serco Clock and Captain Chic Wrongful Death

Plum City – (AbelDanger.net). United States Marine Field McConnell has linked his sister Kristine Marcy’s development of a Common Alerting Protocol (CAP) at the U.S. Department of Justice in the '90s to a Serco Stratum 0 clock apparently used during a 9/11 continuity of government exercise (‘Global Guardian’) to transmit the phony decoy-and-drone navigation data which allegedly caused the wrongful death of Captain Charles ‘Chic’ Burlingame III, pilot of AA Flight 77.

McConnell notes his sister used U.S. SBA companies to install Serco slave clocks on E4B Nightwatch aircraft and that she and her DOJ Pride colleagues had motive, opportunity and weapon to stage a death-by-plane CAP event to kill ‘Captain Chic’, McConnell’s U.S. Naval Academy classmate of 1971.

See #1:
Abel Danger Mischief Makers - Mistress of the Revels - 'Man-In-The-Middle' Attacks (Revised)

Prequel:
#1416 Marine Links Kristine Marcy to Conair Alien Hijack Crimes and Serco Contract Network Time

 

 “American Airlines Flight 77 Reconstruction with ATC Recording” 

"Debra Burlingame: How Obama [BlackBerry is one of Serco’s Common Alerting Protocol devices allowing users to synchronize timing of MitM attacks!] duped the 9/11 and USS Cole Families”

"The Common Alerting Protocol (CAP) is an XML-based data format for exchanging public warnings and emergencies between alerting technologies. CAP allows a warning message to be consistently disseminated simultaneously over many warning systems to many applications. CAP increases warning effectiveness and simplifies the task of activating a warning for responsible officials. Individuals can receive standardized alerts from many sources and configure their applications to process and respond to the alerts as desired. Alerts from the Department of Homeland Security, the Department of the Interior's United States Geological Survey, and the Department of Commerce's National Oceanic and Atmospheric Administration (NOAA), and state and local government agencies can all be received in the same format, by the same application. That application can, for example, sound different alarms based on the information received. 

By normalizing alert data across threats, jurisdictions, and warning systems, CAP also can be used to detect trends and patterns in warning activity, such as trends that might indicate an undetected hazard or hostile act. From a procedural perspective, CAP reinforces a research-based template for effective warning message content and structure. 

The CAP data structure is backward-compatible with existing alert formats including the Specific Area Message Encoding (SAME) used in Weatheradio and the broadcast Emergency Alert System as well as new technology such as the Commercial Mobile Alert System (CMAS), while adding capabilities including: 

Flexible geographic targeting using latitude/longitude “boxes” and other geospatial representations in three dimensions; 

Multilingual and multi-audience messaging; 

Phased and delayed effective times and expirations;

Enhanced message update and cancellation features; 

Template support for framing complete and effective warning messages; 

Digital encryption and signature capability; 

Facility for digital images, audio, and video.” 

“THE COMMON ALERTING PROTOCOL: AN OPEN STANDARD FOR INTEROPERABILITY IN ALL-HAZARD WARNING 

The Common Alerting Protocol (CAP) is a simple, flexible data interchange format for collecting and distributing “all-hazard” safety notifications and emergency warnings over information networks and public alerting systems. 

The Common Alerting Protocol (CAP) specifies an open, non-proprietary digital message format for all types of alerts and notifications. The CAP format is fully compatible with existing formats including the Specific Area Message Encoding (SAME) used for NOAA Weather Radio and the Emergency Alert System, while offering enhanced capabilities that include: 

Flexible geographic targeting using latitude/longitude “boxes” and other geospatial representations in three dimensions;

Multilingual and multi-audience messaging; 

Phased and delayed effective times and expirations; 

Enhanced message update and cancellation features; 

Template support for framing complete and effective warning messages; 

Digital encryption and signature capability; and, 

Facility for digital images [time stamped snuff film money shots], audio and video. 

THE NEED 

Warning systems in the United States today are “a patchwork of technologies and processes,” according to the national non-profit Partnership for Public Warning. Different systems have evolved to meet different threats in different places. Until now there’s been no way to distribute warnings consistently over all available channels. Nor has there been any way to monitor the whole picture of local, state and national warnings at any one time. Decisions about new alerting systems have been fraught with concerns about compatibility and operational complexity. 

BACKGROUND AND PROCESS 

In November 2000 the National Science and Technology Council released a report on “Effective Disaster Warnings.” One key recommendation of the blue-ribbon panel was that “a standard method should be developed to collect and relay instantaneously and automatically all types of hazard warnings and reports locally, regionally and nationally for input into a wide variety of dissemination systems.” 

During 2001 an international working group of more than 120 emergency managers and emergency information technologists developed initial requirements and a straw man design for CAP. In 2002 that effort was adopted by the Partnership for Public Warning (PPW), a national public-private partnership of agencies, vendors and academic experts. In 2003 PPW sponsored CAP into the OASIS standards process for refinement and testing. In April 2004, CAP 1.0 was adopted as an OASIS standard. 

COMPATIBILITY, FLEXIBILITY AND BENEFITS 

CAP is a content standard, deliberately designed to be “transport-agnostic.” In web-services applications, CAP provides a lightweight standard for exchanging urgent notifications. CAP can also be used in data-broadcast applications and over legacy data networks.

CAP provides compatibility with all kinds of information and public alerting systems, including those designed for multilingual and special-needs populations. CAP is fully compatible with the existing national broadcast Emergency Alert System (EAS). A 2003 whitepaper describes details of the CAP/EAS interface. 

CAP incorporates geospatial elements based on Open GIS Consortium recommendations to permit flexible but precise geographic targeting of alerts. It provides for associating digital images and other binary information with alerts. It supports various mechanisms for ensuring message authenticity, integrity and confidentiality (where required) including in particular the work of the OASIS Web Services Security and PKI Technical Committees [Canada’s MDA set up algorithms to manipulate Serco target clocks]. 

The chief benefit of CAP will be reduction of costs and operational complexity by eliminating the need for multiple custom software interfaces to the many warning sources and dissemination systems involved in all-hazard warning. The CAP message format can be converted to and from the “native” formats of all kinds of sensor and alerting technologies, forming a basis for a technology-independent national and international “warning internet.” 

IMPLEMENTERS AND SUPPORTERS 

A partial list of public and private organizations that have implemented CAP includes: 

National Weather Service xxUnited States Geological Survey 

California Office of Emergency Services 

Virginia Department of Transportation 

Capital Wireless Integrated Network (CapWIN) 

GeoDecisions, Inc. 

E Team 

Blue292 

Warning Systems, Inc. 

Comlabs, Inc. xxmobileFoundations 

Ship Analytics 

MyStateUSA 

IEM, Inc. 

Hormann America, Inc. xxOregon RAINS 

NDS, Ltd. [Murdoch MoD Serco time-stamped snuff-film encryption used in Common Alert on 9/11] CAP-capable applications have been deployed in multi-vendor events and field trials in Washington, D.C., Virginia, Florida, Nevada and California.

CAP data elements have been incorporated in the U.S. Department of Justice’s “Global Justice XML Data Model [by Kristine Marcy]”. 

CAP has been endorsed by the National Emergency Management Association’s Preparedness Committee, the Partnership for Public Warning, the ComCARE Alliance, the Emergency Interoperability Consortium and the Capital Wireless Integrated Network (CapWIN). 

For More Information: 

CAP 1.0 Specification xxOverview of CAP 
PPW press release 
Contact Mr. Art Botterell, PPW Representative to OASIS and Chair of the CAP Working Group and the OASIS Emergency Management Notification Methods and Messages Subcommittee. He can be reached by email or (707) 425-4916.” 

More to follow.

PresidentialField Mandate

Abel Danger Blo