| 4 | | |
| 5 | | == Notes == |
| 6 | | Common Alerting Protocol: |
| 7 | | |
| 8 | | ''Originating CAP alerts is one need, receiving them and using them to actuate alerting systems, be they SMS drivers or sirens or whatever is another. Another is a message broker that can interoperate with the commercial boxes. Authentication systems are also a factor, especially where cross-jurisdictional reciprocity is required'' |
| 9 | | |
| 10 | | ''Ideally the CAP XML should be signed end-to-end, especially in a federated system where there's more than one authority running servers/aggregators. Our current implementations sign the alerts at the originating server, so they're at least traceable to the source server but not necessarily the individual operator. Current servers check integrity when they get a message from another server, but there isn't a regional PKI.'' |
| 11 | | |
| 12 | | * http://docs.oasis-open.org/emergency/cap/v1.2/CAP-v1.2.html |
| 13 | | * Use an XSLT |
| 14 | | * Subset of EDXL-DE: http://docs.oasis-open.org/emergency/edxl-de/v1.0/EDXL-DE_Spec_v1.0.pdf |
| 15 | | * Use another XSLT |
| 16 | | * http://code.google.com/p/pyedxl/source/browse/trunk/edxl/edxl.py |
| 17 | | * http://edxlsharp.codeplex.com |
| 18 | | * SQL schema: http://wiki.sahanafoundation.org/doku.php/wiki:user:edxl_discussion#proposed_sahana_edxl-de_database_implementation |
| 19 | | * http://talksahana.com/2009/03/04/firefox-browser-cap-alerting-plugin-sahana-idea-for-gsoc2009/ |
| 20 | | * Sahana CAP/EDXL Broker specification - http://lirneasia.net/wp-content/uploads/2009/05/Sahana-CAP-Msg-Mod-v0.2.pdf |
