Archive for the ‘IPAWS’ Category.

Twitter Weekly Updates for 2011-10-02

  • It is New Years Eve! At least for all Federal budget and acquisition interested folks. – Former Comptroller, MCAS Iwakuni #

Twitter Weekly Updates for 2011-08-28

  • Power out. Doing #IPAWS 3.0 UAT in my little motor home in the front yard. It has a generator. #

IPAWS-OPEN Has “Connections”

The real blessing of standards is that they can make interoperability between lots of different systems possible. IPAWS-OPEN uses EDXL-CAP, and EDXL-DE in a standard SOAP Web Services environment with WS-Security. So far we have developers who have proven their interoperability using .NET, Java (Axis2 with Rampart), Java (Spring Framework), Ruby On Rails, and, as of yesterday, PHP. So, they will all be able to share vital alerting information with each other, and with the public via EAS, CMAS, and NOAA Radio. It is not easy, but it is coming together.

Still looking for the C, C++, and/or Objective C client application. 🙂

Twitter Weekly Updates for 2011-08-07

  • I believe in #NIEM but it can be misused by "carpenters with only a hammer."

Twitter Weekly Updates for 2011-07-24

Upcoming NIEM NTE Presentation – Using NIEM Metadata in an EDXL-DE wrapper to Support IPAWS

If you work with the National Information Exchange Model (NIEM) as well as with other standards, you often run into issues related to how your overall work should incorporate (or not incorporate) NIEM. The rules for NIEM allow you to use recognized external standards independently. FEMA’s Integrated Public Alert and Warning System (IPAWS) does this with it implementation of the Common Alerting Protocol (CAP). You can also use components from an external Standard within a NIEM conforming schema, but only if you use the formally defined NIEM “Adapter” approach. You can also use NIEM inside an externally defined standard wrapper as shown in the graphic below. NIEM_In_Wrapper_Graphic-300x175

My talk at the NIEM National Training Event (NTE) in Philadelphia this August will discuss using an OASIS Emergency Data Exchange Language – Distribution Element (EDXL-DE) as a wrapper as shown, but it will go beyond that. It will show how NIEM conforming data structures can be used within the EDXL-DE wrapper itself as DE conforming metadata to describe the content and desired distribution of the Information Exchange Package (IEP). The goal is to show an innovative use of NIEM that is actually made possible by the (also) innovative structure designed into the EDXL-DE standard. The actual content of the IEP will be an IPAW Profile conforming CAP message. The wrapping DE will use NIEM conforming metadata to define IPAWS distribution and content identification needs.

Twitter Weekly Updates for 2011-07-03

  • @OverlordQ not hard. Go to the IPAWS website. Fill out the MOA request form. #
  • XKCD's "reference implementation of the self referential Joke" – "I'm So Meta, Even This Acronym" – http://t.co/3aJ4Rng #

Twitter Weekly Updates for 2011-06-26

  • FEMA TDL still not back from upgrade. IPAWS-OPEN 2.0 still not available. Hoping for tomorrow. #

Twitter Weekly Updates for 2011-06-19

  • FEMA TDL is still not available for testing IPAWS-OPEN interop. Running tests 3 times daily. Will update any change. #

Twitter Weekly Updates for 2011-06-12

  • RT @ipawsopenstate IPAWS-OPEN is not operating due to Oracle 11 G upgrade. #
  • RT @ipawsopenstate Oops!!! IPAWS-OPEN in TDL is not in operation due to upgrade. Production is UP! #
  • IPAWS-OPEN 2.0 Test environment (TDL) remains down for completion and test of system upgrades. #