OASIS Emergency Management TC

  • 1.  RIPAWS Profile Discrepancy

    Posted 03-09-2010 13:33 
    All,

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

CAP 1.2 specifies that the


  • 2.  Re: [emergency] RIPAWS Profile Discrepancy

    Posted 03-09-2010 13:40 
    Logically both are correct.
Since the profile is, by definition, more restrictive than the standard schema, optional tags in the standard schema could very well be required by the profile.   The real question is whether the IPAWS profile allows a cancel, for example, to leave out the info block.  The answer appears to be no. But a cancel without an info block would be valid for CAP 1.2, outside the IPAWS profile.

That is the way I read it, anyway.

R/s

Gary

On Mar 9, 2010, at 8:32 AM, Gilmore, Timothy wrote:

> All,
> 
> One of our engineers wanted me to pass along some information about
> another IPAWS Profile issue:
> 
> CAP 1.2 specifies that the


  • 3.  Re: [emergency] RIPAWS Profile Discrepancy

    Posted 03-09-2010 14:46 
    Gary's correct about info being required, Tim,
Gary is also correct that you can't leave out the info block in a valid 
CAP-IPAWS message, regardless of whether it is an "Update" or "Cancel" 
msgType.

Cheers,
Rex



Gary Ham wrote:
> Logically both are correct.
> Since the profile is, by definition, more restrictive than the standard schema, optional tags in the standard schema could very well be required by the profile.   The real question is whether the IPAWS profile allows a cancel, for example, to leave out the info block.  The answer appears to be no. But a cancel without an info block would be valid for CAP 1.2, outside the IPAWS profile.
>
> That is the way I read it, anyway.
>
> R/s
>
> Gary
>
> On Mar 9, 2010, at 8:32 AM, Gilmore, Timothy wrote:
>
>   
>> All,
>>
>> One of our engineers wanted me to pass along some information about
>> another IPAWS Profile issue:
>>
>> CAP 1.2 specifies that the


  • 4.  RE: [emergency] RIPAWS Profile Discrepancy

    Posted 03-14-2010 04:22 
    My 2 cents that apply to any "Profile"

The following are the attributes of a HAVE Haiti Profile message that are
required:

•	A HAVE Haiti Profile message must NOT become a new or additional
“standard” (e.g. another Hospital Availability standard or another HAVE 1.0
“version”).
•	A HAVE Haiti Profile message must NOT be a Proprietary Format.
•	A HAVE Haiti Profile message must comply with the HAVE 1.0 standard.
o	A HAVE Haiti Profile message must validate against the HAVE 1.0
standard schema.
o	A HAVE Haiti Profile message must validate within the HAVE 1.0
standard namespace with no changes to root elements.
o	A HAVE Haiti Profile message must use all required elements (i.e. no
deletion of required elements are allowed).
o	A HAVE Haiti Profile message must not change attributes for required
fields.

The following are recommendations for clarity:

•	A HAVE Haiti Profile message may further constrain the HAVE 1.0
standard.*
(* may be thought of as a “constraint schema” against the standard)
•	A HAVE Haiti Profile message may add to required element
definitions.*
(* only to extend or interpret the definition)
•	A HAVE Haiti Profile message may limit size of required elements.
•	A HAVE Haiti Profile message may exclude optional elements.
•	A HAVE Haiti Profile message may use optional elements in a specific
way – as defined for the profile.


The aim of education should be to teach us rather how to think, than what to
think - rather to improve our minds, so as to enable us to think for
ourselves, than to load the memory with thoughts of other men.  ~Bill
Beattie



    
                                                
    
					
                                                    

        
                                                
				
    
                                                
    
                                                    
                                                        
                                                        Original Message


  • 5.  RE: [emergency] RIPAWS Profile Discrepancy

    Posted 03-09-2010 13:43 
    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


Related Content