Version 29 (modified by Nuwan Waidyanatha, 10 years ago) ( diff )


Common Alerting Protocol (CAP) Code-fest

Place: Orion IT City Park Date: 19 June 2014

Software Tools

Software tool name coding platform team contact documentation
SAMBRO Python/Web2Py/PostgreSQL Nuwan Waidyanatha, Francis Boon , Dominic Konig CAP Broker Blueprint
CAP Editor Java Eliot Christian documentation included
Google AlertHub Java talk to Steve Hakusa (and/or Nigel) ??? A simple, open, mechansim based on the Pubsubhubbub protocol & open source reference implementation
Mobile publisher HTML5/JS Art Botterell CAPTools on GitHub
Other other skills other team contact other documentation

Suggestions of Coding Needs

  • Google AlertHub Testing facility - Need to allow test-only use of the AlertHub for implementors of CAP feeds and during alerting exercises (talk to Steve Hakusa about this)
  • Notice of Direction facility - Need to allow posting of notice of works-in-progress for use by implementors, such as harmonizing CAP parameter values, promoting particular best practices for CAP feeds, etc. These are intended for efforts that are less formal than profiling, although some may progress to that over time
  • Symbol Sets facility - Need to have a source of well-known sets of symbols (pictographs) relevant to alerting. This might be organized simply as a thesaurus (entries related to each other by "broader", "narrower" and "alias for" relationships), with a simple network service for fast access to symbols


  1. Eliot Christian, CAP Program Committee Chair
  2. Elysa Jones, OASIS EM-TC Chair
  3. Nuwan Waidyanatha, Sahana Software Foundation Standards & Interoperability Chair and LIRNEasia Senior Research Fellow
Note: See TracWiki for help on using the wiki.