A Mentor for Software Process, Business Process Re-engineering, Software Architecture, XML Schema Design, etc.
Why you should attach security at the message level, not just use SSL.
I found the following today as a good explanation. It goes all the way back to 2005, but the metaphor still works. See: Naked Motorcycle Riding
I wrote the following Comment on a LinkedIn NIEM Thread and thought it might be worth sharing:
In my opinion (perhaps not so humble 
) NIEM is very good if you use it right. But, if you think of NIEM as a standard by itself, it is NOT GOOD. Too much stuff. Hard to keep organized. It is actually incredible how well organized it is given its volume, but as a standard by itself, it is just too BIG to be anything but unwieldy.
Now, as a model for building standard exchanges, it has TREMENDOUS value. It is like a mine. You have to refine the ore through an appropriate standards development process. (The IEPD process works for this.) But the ore is super high quality when compared with building standards from scratch, because the NEIM model has been preprocessed in the sense that most definition and relationships are well defined and understood. Even so, you still have to refine NIEM input using the IEPD process to actually create a usable exchange or a useable standard exchange.
Bottom line, if you expect NIEM to be “auto-reusable,” you will be disappointed. But, If you use NIEM appropriately, it has a lot to offer in the way of documented data structure and definition.
Giving a talk on the ways to use CAP using the new IPAWS CAP 1.2 interface at noon tomorrow (15 Feb 2012). Details:
Integrated Public Alert and Warning System (IPAWS) Joint Developer/Practitioner Webinar
Using the Open Platform for Emergency Networks (OPEN) for Public and Private Alerting
Wednesday February 15, 2012 12:00 Noon EasternIn addition to its role as message aggregator for public alerting, IPAWS-OPEN enables the interoperable sharing of emergency alerts and incident-related data between incident management systems that comply with non-proprietary information standards.
During our next Webinar, System Architect Gary Ham will describe how IPAWS-OPEN provides support for exchanging alerts within a single response organization, between one or more response organizations, with all response organizations, and/or with the public. He will also explain how the Common Alerting Protocol (CAP) scope element is implemented by IPAWS-OPEN for public and private alerting.
This program is intended primarily for IPAWS-OPEN developers and testers; however, emergency management practitioners who are interested in learning more about IPAWS incident management-related capabilities are also encouraged to participate. Please make plans to join us via Live Meeting. As always, your questions and comments are welcome.
IMPORTANT: The audio portion of the program will be delivered via your computer speakers. The Live Meeting client must be used in order to receive the audio. Please review the instructions available from: http://www.fema.gov/pdf/emergency/ipaws/livemtginstruct.pdf prior to the program.
Login to MS Live Meeting for visuals: The following login link can only be used 30 minutes prior to the scheduled meeting time: https://www.livemeeting.com/cc/eiip/join?id=DMprogram&role=attend
#I will be explaining the contents of the new IPAWS-OPEN Developer’s Guide tomorrow. It will soon be added to downloads from the FEMA IPAWS-OPEN web site.
details are per the following:
Integrated Public Alert and Warning System (IPAWS) Developer Webinar
Open Platform for Emergency Networks (OPEN)
Introduction to the New IPAWS-OPEN Developer’s Guide
Wednesday January 18, 2012 12:00 Noon EasternIPAWS-OPEN enables the interoperable sharing of emergency alerts and incident-related data between systems that comply with non-proprietary information standards, and serves as the alert aggregator for the Integrated Public Alert and Warning System.
During our next Webinar, System Architect Gary Ham will provide an introduction and overview of the new IPAWS-OPEN Developer’s Guide. The purpose of the guide is to help developers successfully write IPAWS-OPEN interoperable code.
This program is intended primarily for third party IPAWS-OPEN developers and testers. Please make plans to join us via Live Meeting. As always, your questions and comments are welcome.
IMPORTANT: The audio portion of the program will be delivered via your computer speakers. The Live Meeting client must be used in order to receive the audio. Please review the instructions available from: http://www.fema.gov/pdf/emergency/ipaws/livemtginstruct.pdf prior to the program.
Login to MS Live Meeting for visuals: The following login link can only be used 30 minutes prior to the scheduled meeting time: https://www.livemeeting.com/cc/eiip/join?id=DMprogram&role=attend
If you are unable to attend this month’s program due to other commitments, a recording will be accessible from the FEMA Library.
I now have two very useful jar files to support Java developers connect to IPAWS-OPEN for CAP 1.2 Origination. The first takes a CAP 1.2 message as an XML String and signs it using the signature provided. The second, I wrote as a test driver for all IPAWS Origination and retrieval functions of the Originating System Interface (aka Interface A). It is entirely Property file driven, but it can also use the command line to override some properties in execution and can serve as a Java Class for providing the interface to systems that might want to put their own GUI front end in place (It has no GUI). It also does message signing for post operations. I cannot just put it on the open Internet, but I can provide the jar(s) to developers who have valid MOA’s to develop to IPAWS-OPEN Interface A. If you qualify, please contact me and I will the find a way to get the jar(s) to you. It is, after all, Government property that you, as taxpayers, paid for. One caveat: No warranties on this test code. You use it at your own risk. But it may help a lot.
FEMA has announced its new course for Alerting Authorities. Alert Origination Software developers/vendors may also find the course useful to understand the context of alerting via IPAWS-OPEN to EAS, CMAS, and NOAA Radio. The course is required for alerting authorities as a pre-requisite for getting Alerting Authority for IPAWS push dissemination, but it also provides info for developers as they define requirements for the software they build. Here is the notification that I received:
The FEMA Integrated Public Alert and Warning System (IPAWS) program office has worked with FEMA’s Emergency Management Institute (EMI) and subject matter experts to create a course that provides alert and warning training. This course (IS-247) is now available at no cost on-line. See http://training.fema.gov/EMIWeb/IS/is247.asp
IS-247 provides basic information on the Integrated Public Alert and Warning System (IPAWS). The goal of this course is to provide public safety officials with: increased awareness of the benefits of using IPAWS for effective public warnings; skills to draft more appropriate, effective, and accessible warning messages; and best practices in the effective use of Common Alerting Protocol (CAP) to reach all members of their communities. The course is expected to take 2 hours to complete and includes a final exam.
Regional, State and Local alerting authorities must successfully complete this course prior to being authorized to use IPAWS OPEN to send alerts via EAS, mobile devices, and other communications pathways. Although the course is designed primarily for emergency management, law enforcement, fire services, dispatch, and other public safety personnel, anyone wishing to learn more about IPAWS may take the course.
