OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

emergency-adopt message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


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


Yes for both but in different meeting notes.

The decision for EDXL-CAP was made in the F2F 
EM-TC meeting held during the TCIP conference 2010.

The decision for CAP 2.0 to require the DE was 
made over a year ago but would need to search 
meeting notes to find the precise time.

Elysa

At 05:38 AM 6/24/2010, McGarry, Donald P. wrote:
>Is that a "yes" for both 1 & 2?
>
>-Don
>Office: 315-838-2669
>Cell: 703-595-9375
>dmcgarry@mitre.org
>
>
>-----Original Message-----
>From: Elysa Jones [mailto:ejones@warningsystems.com]
>Sent: Thursday, June 24, 2010 6:12 AM
>To: McGarry, Donald P.; rexb@starbourne.com; THOMAS FERRENTINO
>Cc: WernerJoerg; Camille L.Osterloh; emergency-adopt@lists.oasis-open.org
>Subject: RE: [emergency-adopt] EDXL Product 
>Directory - Vendor Outreach Updated
>
>Yes, that was decided and is included in our minutes from that meeting. Elysa
>
>At 05:05 AM 6/24/2010, McGarry, Donald P. wrote:
> >1. I was under the impression that at the NIEM face to face we agreed
> >that from then on "CAP"
> >would be referred to as "EDXL-CAP"
> >2. I was also under the impression that CAP 2.0 would require use of the DE.
> >
> >-Don
> >Office: 315-838-2669
> >Cell: 703-595-9375
> >dmcgarry@mitre.org
> >
> >
> >-----Original Message-----
> >From: Rex Brooks [mailto:rexb@starbourne.com]
> >Sent: Wednesday, June 23, 2010 8:55 PM
> >To: THOMAS FERRENTINO
> >Cc: WernerJoerg; Camille L.Osterloh;
> >emergency-adopt@lists.oasis-open.org
> >Subject: Re: [emergency-adopt] EDXL Product Directory - Vendor Outreach
> >Updated
> >
> >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 
> referencences os of âCAP❠to
> > >     âEDXL-CAPÃL-CAP❠
> bââ¬Â but there is a motion to referference âEDXL
> > >     inclcluding CAP❠fo for all 
> communication about the standardds.
> > >
> > >     Here is relevant portion of the meeting notes
> > >
> > >     */CAP and the EDXL family of Standards. /*
> > >
> > >     /â¦Since this has been the process for all SSttandards 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.p
> > > hp
> > >
> >
> >--
> >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



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]