Draft Meeting Notes from the EM CAP-Profile SC Telecon Meeting

Date: January 5 200811:00 PM EST

A quorum was in attendance.

1 Attendance

Sukumar Dwarkanath
Tom Ferrentino
Bob Bunge
Art Botterell
Rich Van Dame
Steve Streetman / Rex Brooks
Bill Kalin
Jacob Westfall
Gary Ham
Elysa Jones
Bill Kalin

2 Note taker appointed

Tom Ferrentino will take notes.

3 CAP IPAWS Requirements Crosswalk – Discussion

Remain silent on event hoping that NWEM will come on board. Gary doubts there is a technical reason. He feels it is the way it is programmed which requires the weather service to make the change.

3.1 Remain silent on event hoping the NWEM will come on board. Gary doubts it is a technical issue he believes it is a programming issue with the National Weather Service (NWS) . The NWS will have to make a change to the programming to handle the event code issue.

3.1.1.1 Art feels this should not hold up our progress and hopefully it can be touched on during the comment period.

3.1.1.2 No constraints will be placed on the event tag at this time.

3.1.3 Resource Type: The only constraint is from CMAS which states: “Value of "Assess" will result in rejection by CMAS gateway. Additional value of "Avoid" recommended.”

3.1.4Non standard value of avoid may occur and can be handled at the next version of CAP (Art). Sukumar asked will it break the current version. Gary suggests it will not validate against the schema.

3.1.5Rex suggests adding Avoid as errata (omission) and once the errata are passed it would then validate. Need to add a qualifying question. An errata is just a correction.

3.1.6 Art does not like this type of practice that a standard can be amended by errata. Can we acknowledge a deviant usage?

3.1.7Rex…May be included in the next CAP version but Art said he also doesn’t not want to get into this practice to wait for TC action. Art says we can just let it known that this exception is possible until the 3.1.8 TC can take action. Sukumar is looking for an expanded definition. Art and Rex says it is best to leave as a non-validated exception. We will go with this option for now.

3.2Urgency – No normative specifications

3.3Severity – No normative specifications

3.4Certainty – No Normative specifications

3.5EventCode – System level required for Hazcollect, EAS, and recommended in CMAS. This element must be present with a value name of SAME in CAP and using a SAME standard three letter value. There may be other values present.

3.5.1Gary says there may be a programming change within Hazcollect in order to read a value name of “SAME” and also value names without “SAME”.

3.5.2Jacob asks if this should be profile specific. If we are setting this up for profiles then .it should be tied to the profile itself.

3.5.3Gary suggests a value list URN for SAME values.

3.5.4Rex said it has not been built within the EDXL framework as yet.

3.5.5Gary says it is not illogical to use it separately either.

3.5.6Jacob is asking if this is a profile then do we set a standard based on required parameters. Set a precedent on how we go forward in the future.

3.5.7Elysa – CAP implementer’s workshop in Geneva – Opportunity with ITU to register profiles with CAP worldwide. Interesting to hear how Jacob is using profiles. Wait on what the subcommittee submits to the TC and we should look at giving the International community consideration.

3.6Effective and Onset –

3.6.1Jacob says we need to act on this and Art agrees. If we are going to use info block to represent different time frames then onset and effective become necessary. The intent that this be buffered but may not be feasible. For this particular profile we need to rule this out.

3.6.2If you get a message an hour in the future it is up to your device on how to handle it. Art – No system is going to buffer anything for future release. Gary – NWS sees on set and effective as the exact same thing. Jacob says if it is the same in other systems also then we need to document this as an exception.

3.6.3Info block should not be used for different time frames (for staging per Jacob).

3.7Worksheet of the profile cap elements included at front of the specification allowing everyone to know for informative purposes what makes up the different profiles and their requirements.

4 Meeting Adjourned. 12 noon EST