RE: [emergency] RIPAWS Profile Discrepancy

["Paulsen,Norm [Ontario]" <Norm.Paulsen@ec.gc.ca>]

Timothy

In this case, the IPAWS profile is just a hardening of the CAP protocol.
In other words, by being IPAWS compliant in this particular case, the
message is still CAP compliant. IPAWS just needs to make this
distinction clear in their profile documentation (if it isn't already
done so).

In our Canadian Profile, we make <language> required, however the
resulting file is still CAP compliant.

What has to happen here is to understand that CAP compliancy is not the
same as IPAWS compliancy.

Norm


-----Original Message-----
From: Gilmore, Timothy [mailto:TIMOTHY.D.GILMORE@saic.com] 
Sent: March 9, 2010 8:32 AM
To: emergency@lists.oasis-open.org
Subject: [emergency] RIPAWS Profile Discrepancy

All,

One of our engineers wanted me to pass along some information about
another IPAWS Profile issue:

CAP 1.2 specifies that the <info> element is optional (presumably, a
"cancel," "update," "error," or "acknowledgement" alert could use the
<references> element to specify a previous alert), and the IPAWS Profile
document doesn't say otherwise.  The IPAWS Profile *schema*, however,
makes the <info> element *required*.

Which is correct? 

Thanks,

Timothy D. Gilmore | SAIC
Senior Test Engineer | ILPSG | NIMS SC | NIMS STEP
phone: 606.274.2063 | fax: 606.274.2012
mobile: 606.219.7882 | email: gilmoret@us.saic.com Please consider the
environment before printing this email.


-----Original Message-----
From: Sommers, Daniel B. 
Sent: Tuesday, March 09, 2010 8:07 AM
To: Gilmore, Timothy
Cc: Duncans, Charlene; Gooch, Martena M.; Roe, Tom A.
Subject: IPAWS Profile Discrepancy

Tim,

Here is another IPAWS Profile issue:


Thanks,
Dan

--
Daniel B. Sommers | SAIC
Software Engineer | ILPSG
phone: 606.274.2079 | fax: 606.274.2025
mobile: xxx.xxx.xxxx | email: daniel.b.sommers@saic.com

Please consider the environment before printing this email.

---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php