RE: [emergency] Starter Document for Emergency Data Exchange Language (EDXL) Common Alerting Protocol Logo/Symbol and Guidance (CAP-Logo) Version 1.0

["Joerg, Werner" <Werner.Joerg@iem.com>]

Title: RE: [emergency] Starter Document for Emergency Data Exchange Language (EDXL) Common Alerting Protocol Logo/Symbol and Guidance (CAP-Logo) Version 1.0

If I recall properly, none of the SC members present were enthusiastic about the title, but I decided to let it be, as is, till we had a chance to clarify the notions of logo vs. symbol, vs. icon with Carol, after which time we could reconsider the title.
In my opinion, Chet's suggestion is the best so far and we may well agree on that after our discussion with Carol.

Any other input is welcome, of course.

Regards,
Werner


-----Original Message-----
From: emergency@lists.oasis-open.org on behalf of Elysa Jones
Sent: Thu 12/1/2011 7:18 PM
To: rex.brooks@ncoic.org; 'Chet Ensign'
Cc: 'Paul Knight'; emergency@lists.oasis-open.org
Subject: RE: [emergency] Starter Document for Emergency Data Exchange Language (EDXL) Common Alerting Protocol Logo/Symbol and Guidance (CAP-Logo) Version 1.0

I'm ok with it.  Perhaps Werner or others will have input?  Elysa

-----Original Message-----
From: emergency@lists.oasis-open.org [mailto:emergency@lists.oasis-open.org]
On Behalf Of Rex Brooks
Sent: Thursday, December 01, 2011 6:10 PM
To: Chet Ensign
Cc: Paul Knight; emergency@lists.oasis-open.org
Subject: Re: [emergency] Starter Document for Emergency Data Exchange
Language (EDXL) Common Alerting Protocol Logo/Symbol and Guidance (CAP-Logo)
Version 1.0

That's fine with me, Chet,

Cheers,
Rex

On 12/1/11 2:10 PM, Chet Ensign wrote:
> All,
>
> I had a thought on the title. I found the wording a bit hard to parse.
> Would something like
>
> Emergency Data Exchange Language (EDXL) Guidance on Common Alerting
> Protocol Logos and Symbols (CAP-Logo) Version 1.0
>
> accurately express the purpose of the document? It gives it room to
> grow if you add more graphics over time plus (at least for me) it
> eliminates confusion about whether the document address symbols or
> logos.
>
> Best,
>
> /chet
>
> On Thu, Dec 1, 2011 at 9:58 AM, Paul Knight<paul.knight@oasis-open.org>
wrote:
>> Per the TC's submission request [1], please find the attached starter
>> document for:
>>
>> Emergency Data Exchange Language (EDXL) Common Alerting Protocol
>> Logo/Symbol and Guidance (CAP-Logo) Version 1.0
>> WP-abbrev: edxl-cap-logo
>>
>> The expected URI pattern:
>> http://docs.oasis-open.org/emergency/edxl-cap-logo/v1.0/cnd01/edxl-ca
>> p-logo-v1.0-cnd01.odt
>>
>> Please let me know if anything here fails to meet your expectations.
>> Further revisions to this Work Product must be maintained in Working
>> Drafts, following procedures detailed in the TC Handbook [2].
>> Working Drafts should be made available by uploading the document(s)
>> to the TC's Kavi document repository, or (provisionally/temporarily)
>> to the TC's Subversion (SVN) repository, if SVN has been activated
>> for your TC [3].  TCs are encouraged to use ZIP packaging when the WD
>> releases contain multiple files (and directories).
>>
>> For each WD revision, you will need to:
>> 1) increment the Working Draft revision (number) from 01 to 02, 03,
>> 04 etc., as successive Working Drafts are produced; the revision
>> number needs to be updated at the top of the document in the stage
>> identifier (Working Draft
>> ##) and in the document identifier within the page footer.
>> 2) supply the relevant publication/release/upload date for each
>> successive Working Draft instance, using the  prescribed date format:
>> DD Month YYYY; the date needs to be updated at the top of the
>> document (just below the stage identifier, Working Draft ##) and in the
page footer.
>> 3) provide suitable text for a document Abstract, updating this
>> summary with successive revisions to provide an accurate description
>> of the subject matter, goals, scope, etc.
>> 4) keep the Acknowledgments (Appendix A) and Revision History
>> (Appendix C) up-to-date with each WD revision.
>> 5) consult the OASIS Naming Directives document when creating new
>> artifacts that may be part of the Work Product (e.g., image files,
>> XML schemas), observing the rules for name characters in files and
>> proposed directories, and for proposed URIs/namespaces [4].
>> When the TC votes [5] to approve a Working Draft as a Committee Draft
>> (CSD or CND), the Chair or other designated person must submit a
>> "Committee Specification Draft Creation and Upload Request"
>> accessible on the TC Administration Requests Page [6].  Upon receipt
>> of this form, the TC Administrator will QC and process the Work
>> Product for official publication in the OASIS Library as a Committee
>> Draft (http://docs.oasis-open.org/), including addition of the
>> requisite cover page metadata and other boilerplate information, as
>> described in the TC Handbook. [7] =========== References:
>> [1] http://tools.oasis-open.org/issues/browse/TCADMIN-770
>> [2] Working Drafts
>>     
>> http://docs.oasis-open.org/TChandbook/Reference/WorkingDrafts.html
>> [3] SVN Version control, via Tools
>>      http://tools.oasis-open.org/
>> [4] OASIS Naming Directives
>>     
>> http://docs.oasis-open.org/specGuidelines/ndr/namingDirectives.html
>> [5] Approval of a WD as a CD (CSD or CND)
>>
>> http://www.oasis-open.org/committees/process-2010-07-28.php#committee
>> Draft [6] TC Administration Requests Page, see Committee
>> Specification Draft Creation / Upload Request
>>      http://www.oasis-open.org/resources/tc-admin-requests
>> [7] Committee Specification Drafts and Committee Note Drafts
>>
http://docs.oasis-open.org/TChandbook/Reference/CommitteeSpecDrafts.html
>>     
>> http://docs.oasis-open.org/TChandbook/Reference/CommitteeNoteDrafts.h
>> tml
>>
>> Best wishes,
>> Paul
>>
>> --
>> Paul Knight  - Tel: +1 781-861-1013
>> OASIS - Advancing open standards for the information society Document
>> Process Analyst
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: emergency-unsubscribe@lists.oasis-open.org
>> For additional commands, e-mail: emergency-help@lists.oasis-open.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: emergency-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: emergency-help@lists.oasis-open.org


---------------------------------------------------------------------
To unsubscribe, e-mail: emergency-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: emergency-help@lists.oasis-open.org