RE: [emergency] RE: Recent CBRN Interoperability forSituational Awareness Workshop

["Gary Ham" <hamgva@cox.net>]

I very much agree with Art.
Sometime the right profile is to leave the base CAP alone and just publish a
standard profile way of using the structures that were designed for
extensibility (like parameters).

R/s

Gary A. Ham
http://grandpaham.com
703-899-6241
Grandpa can do IT!
 
-----Original Message-----
From: Art Botterell [mailto:ABott@so.cccounty.us] 
Sent: Monday, November 17, 2008 8:43 PM
To: emergency@lists.oasis-open.org; creed@opengeospatial.org
Cc: gpercivall@opengeospatial.org; rsingh@opengeospatial.org
Subject: Re: [emergency] RE: Recent CBRN Interoperability forSituational
Awareness Workshop

Perhaps even before drilling into domain-particular profiles it might be
useful to publish an application note on how parameters and resources
can be used to include specialized information within CAP messages.  

I've come across several implementers who were going to unnecessary
lengths because they didn't understand how to use those existing
mechanisms.

- Art
  
-----Original Message----- 
From: Rex Brooks <rexb@starbourne.com> 
To:  <emergency@lists.oasis-open.org> 
To: Reed, Carl <creed@opengeospatial.org> 
Cc: Percivall, George <gpercivall@opengeospatial.org> 
Cc: Singh, Raj <rsingh@opengeospatial.org> 
 
Sent: 11/17/2008 4:44:04 PM 
Subject: [emergency] RE: Recent CBRN Interoperability for Situational
Awareness Workshop 
 
Thanks Carl, 
 
Sounds like a lot of folks are on the same page. 
 
Cheers, 
Rex 
 
At 3:58 PM -0700 11/17/08, Carl Reed wrote: 
>Lat week I attended a CBRN Interoperability for Situational  
>Awareness Workshop. Very well attended, informative, and organized.  
>A variety of topics were covered, from networks to communications to  
>sensor integration to standards (interface and encoding). 
> 
>CAP was discussed a number of times. Several take aways from the
discussions: 
> 
>CAP is definitely seeing high interest and potential uptake in the  
>CBRN community. 
>However, CAP implementations in this community are doing a variety  
>of interesting additions (such as embedding sensor metadata) that  
>will make the implementations non-interoperable. 
>And numerous requests for more flexible or extensible mechanisms for  
>expressing geo content. The requests were pretty much in line with  
>what we received during the public comment period. 
> 
>One thing that stuck in my mind for sure is the need for a profile  
>of CAP for the CBRN community! 
> 
>Cheers 
> 
>Carl Reed, PhD 
>CTO and Executive Director Specification Program 
>OGC 
> 
>The OGC: Helping the World to Communicate Geographically 
> 
>--------------------- 
> 
>This communication, including attachments, is for the exclusive use  
>of addressee and may contain proprietary, confidential or privileged  
>information. If you are not the intended recipient, any use,  
>copying, disclosure, dissemination or distribution is strictly  
>prohibited. If you are not the intended recipient, please notify the  
>sender  immediately by return email and delete this communication  
>and destroy all copies. 
> 
>"The important thing is not to stop questioning." -- Albert Einstein 
>"Security is mostly a superstition. It does not exist in nature.  
>Life is either a daring adventure or nothing." -- Helen Keller 
> 
>--------------------------------------------------------------------- 
>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 
 
 
--  
Rex Brooks 
President, CEO 
Starbourne Communications Design 
GeoAddress: 1361-A Addison 
Berkeley, CA 94702 
Tel: 510-898-0670 
 
--------------------------------------------------------------------- 
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  
 

---------------------------------------------------------------------
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