Re: [emergency] RE: Recent CBRN Interoperability for Situational Awareness Workshop

[creed@opengeospatial.org]

I would be very wary of using CAP to encode anything related to a sensor
description, metadata, semantics, or processes. This is what the OGC
sensor standards are designed for. I would, however, suggest that
providing CAP examples for the CBRN community where the observation that
triggered the alert is a component of the CAP message would be extremely
helpful. The CAP message could include a reference to the full sensor
description (A SensorML schema) using the
cap.alertInfoResource.uri.identifier.

Cheers

Carl


>> mechanisms focused on particular issues would be helpful. As Art
>> notes, we may eventually see patterns develop that we can incorporate
>> in a more comprehensive document if we think that's best.
>
> So instead of a sensor profile, or single best practices guide, create a
> number of "application notes" or "usage guides"?  What would these guides
> be called and the topics be?  Is this something Adoption might want to ask
> for comments/feedback on from the CAP community in order to develop a
> list?
>
> --
> jake@jpw.biz
> --
>
> ---------------------------------------------------------------------
> 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
>
>