Re: [emergency-adopt] EDXL Product Directory - Vendor Outreach Updated

[Rex Brooks <rexb@starbourne.com>]

We are firing up CAP 2.0 so this is certainly something that should be 
clearly detailed in that new version. However, remember, we will need to 
have a standalone CAP as well as a fully fledged EDXL family member CAP. 
It's a spectrum or range, not a choice of one or the other.

Cheers,
Rex

THOMAS FERRENTINO wrote:
> Werner's comment suggestion is a good one (I believe). It does not 
> explicitly rename CAP as EDXL-CAP but it does place CAP within the 
> EDXL family. This may be a good way to gravitate slowly towards the 
> EDXL-CAP 1.2 re-titling of the CAP standard.
> E.g.
>
> "Vendors may provide a description of their product and identify 
> specific EDXL standards which are supported (CAP, DE, HAVE, and/or RM)."
>
> Tom
>
>
>
> --- On *Wed, 6/23/10, Osterloh, Camille L. 
> /<CAMILLE.L.OSTERLOH@saic.com>/* wrote:
>
>
>     From: Osterloh, Camille L. <CAMILLE.L.OSTERLOH@saic.com>
>     Subject: RE: [emergency-adopt] EDXL Product Directory - Vendor
>     Outreach Updated
>     To: "Joerg, Werner" <Werner.Joerg@iem.com>
>     Cc: emergency-adopt@lists.oasis-open.org
>     Date: Wednesday, June 23, 2010, 11:23 AM
>
>     Werner, Based on your comment below I did go back and pull
>     relevant section from notes captured in EM-TC 9-29-09 minutes. I
>     don’t see a decision to change any references of “CAP� to
>     “EDXL-CAP� but there is a motion to reference “EDXL
>     including CAP� for all communication about the standards.
>
>     Here is relevant portion of the meeting notes
>
>     */CAP and the EDXL family of Standards. /*
>
>     /…Since this has been the process for all Standards to date
>     beginning with CAP and including EDXL-DE, EDXL-RM, EDXL-HAVE, the
>     group discussed the need to single CAP out rather than include it
>     in the EDXL "family." Discussion included the fact that CAP is
>     transport agnostic and maybe should be considered separately for
>     that reason. However, the others are really transport agnostic.
>     CAP was done before the EDXL name was coined and the process
>     formalized at DHS S&T. However, it was basically the same idea.
>     After further discussion on the topic, *TGrapes made and RBrooks
>     seconded a motion that EM-TC begin using "EDXL including CAP" for
>     all communication about our Standards. All agreed.*/
>
>     If we need to adjust further please let me know. Thanks, -Camille
>
>     *Camille L. Osterloh* | SAIC
>
>     NIMS STEP Task Lead |
>
>     Test Manager | ILSPG
>
>     phone: 606.274.2019 | fax 606.274.2025
>
>     email: osterlohc@saic.com
>     <http://us.mc840.mail.yahoo.com/mc/compose?to=osterlohc@saic.com>
>
>     Please consider the environment before printing this email.
>
>     ------------------------------------------------------------------------
>
>     *From:* Werner.Joerg@ieminc.com [mailto:Werner.Joerg@ieminc.com]
>     *On Behalf Of *Joerg, Werner
>     *Sent:* Friday, May 28, 2010 5:37 PM
>     *To:* Osterloh, Camille L.; emergency-adopt@lists.oasis-open.org
>     *Subject:* RE: [emergency-adopt] EDXL Product Directory - Vendor
>     Outreach Updated
>
>     Camille,
>
>     thanks for the updated text - looks good, and to the point.
>
>     I do have ambivalent feelings about the reference to CAP: on one
>     hand it best is known under that name; on the other hand the EM-TC
>     had decided at the Baltimore F2F to use the designation EDXL-CAP
>     henceforth.
>
>     My first idea would be to simply replace all occurrences of CAP
>     with EDXL-CAP. On second thought however I'd like to suggest that
>     we rewrite the first sentence of the 2nd paragraph in a more
>     "viral" manner as
>
>     "Vendors may provide a description of their product and identify
>     specific EDXL standards which are supported (CAP, DE, HAVE, and/or
>     RM)."
>
>     Cheers,
>     Werner
>
>     ------------------------------------------------------------------------
>
>     *From:* Osterloh, Camille L. [mailto:CAMILLE.L.OSTERLOH@saic.com]
>     *Sent:* Fri 5/28/2010 11:12 AM
>     *To:* emergency-adopt@lists.oasis-open.org
>     *Subject:* [emergency-adopt] EDXL Product Directory - Vendor
>     Outreach Updated
>
>     Here is an updated vendor outreach email based on discussion in EM-TC
>     meeting today. Carol Geyer is POC for vendor questions and her email
>     address has been added.
>
>
>     The OASIS Emergency Management Adoption Technical Committee invites
>     vendors to register with the new EDXL Product Directory -
>     http://oasis-emergency.org/products. The directory provides a
>     searchable
>     listing of products implementing the EDXL suite of standards including
>     CAP.
>
>     Vendors may provide a description of their product and identify
>     specific
>     standards which are supported (CAP, EDXL-DE, EDXL-HAVE, and/or
>     EDXL-RM).
>     The directory also allows vendors to identify participation in
>     interoperability demonstrations and the NIMS Supporting Technology
>     Evaluation Program (NIMS STEP). There are no fees associated with
>     listing a product.
>
>     To take advantage of this opportunity please visit
>     http://oasis-emergency.org/products and select the "Add Product"
>     link in
>     the upper right corner of the page. You will be directed to the Log-in
>     page to create an account. Upon registration you will receive a reply
>     email with a password and initial instructions.
>
>     If you have any questions please contact Carol Geyer at
>     Carol.Geyer@oasis-open.org.
>
>     Regards,
>
>     <Signature>
>
>     ---------------------------------------------------------------------
>     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