Changes between Version 76 and Version 77 of Event/2011/GCI

Timestamp:

11/20/11 12:28:50 (13 years ago)

Author:

Pat Tressel

Comment:

--

Event/2011/GCI

@@ -259 +259 @@
 Difficulty : Nuwan:'''MEDIUM''', Pat:'''HARD''' Proposed by: [http://lirneasia.net/profiles/nuwan-waidyanatha | Nuwan][[BR]]
 
-This is for Common Alerting Protocol (CAP) with capabilities for multi-language alerting and multi-media delivery.  Use Agasti CAP Broker as a starting point.  (This needs clarification. Eden does not have a CAP broker that I know of. So before there can be a GUI, there would need to be a port or implementation of a CAP broker. --Pat)
+This is for Common Alerting Protocol (CAP) with capabilities for multi-language alerting and multi-media delivery.  Use Agasti CAP Broker as a starting point.  (This needs clarification. Eden does not have a CAP broker that I know of. And the current Agasti CAP support is in Krakatoa, not Mayon, so needs to be ported there too. So before there can be a GUI, there would need to be a port or implementation of a CAP broker, no? --Pat)
 
 '''Specific    : ''' Build a [http://sixrevisions.com/user-interface/website-wireframing/ | wireframe] with functionality for the [http://www.incident.com/cookbook/index.php/Welcome_to_the_CAP_Cookbook | Common Alerting Protocol] messaging broker. It should follow a publisher subscriber model. Some specifications are in the [http://lirneasia.net/wp-content/uploads/2009/05/Sahana-CAP-Msg-Mod-v0.2.pdf | CAP Software Requirement Specifications] [[BR]]
@@ -273 +273 @@
 '''Reevaluate  : ''' Once the wireframe is built on the concluded requirements that will be put to test through the scenario based testing. [[BR]]
 
-=== Design a GUI to build and test XSL file ===
+=== Write a blueprint for a GUI tool to build and test XSL files ===
+'''''Migrated'''''[[br]]
 Difficulty : Nuwan:'''MEDIUM''', Pat:'''HARD''' Proposed by: [http://lirneasia.net/profiles/nuwan-waidyanatha | Nuwan][[BR]] 
-'''Specific    : ''' Given that Sahana is getting heavy on XML there should be a tool to develop text, html, etc outputs based one's own XSL transformation file.  The user should be presented with the option to select the XML file; i.e. tags and schema, then include/exclude those tags with inserts of fixed text. The user should be able to preview the output. The built XSL file can then be stored to be used for a particular function. In this case it would be producing CAP message based user specific outputs for email, web, rss, twitter, google, etc. [[BR]]
+'''Specific    : ''' Given that Sahana is getting heavy on XML there should be a tool to develop text, html, etc. outputs based one's own XSL transformation file.  The user should be presented with the option to select the XML file; i.e. tags and schema, then include/exclude those tags with inserts of fixed text. The user should be able to preview the output. The built XSL file can then be stored to be used for a particular function. In this case it would be producing CAP message based user specific outputs for email, web, rss, twitter, google, etc. [[BR]]
 '''Measurable  : ''' This would allow super users to develop implementation specific CAP content delivery outputs. [[BR]]
 '''Attainable  : ''' [[BR]]