Re: [emergency-adopt-docs] Follow-up to C&D SC Meeting Notes of Aug09, 2011 [SEC=UNCLASSIFIED]

[Rex Brooks <rex.brooks@ncoic.org>]

Thanks Greg,

I agree with your comments, FWIW. Just wanted to let you know that we are planning to reschedule our next meeting on the 23rd of this month for 4:00 p.m. Eastern Time so that perhaps you can join us, even though that is still quite early in the morning in Australia.

We still have to make certain that we are not in conflict with the EDXL-HAVE SC who have reserved that slot on a regular basis. However, they have been holding off on new work while EDXL-SitRep and the supporting specifications of Common Types, the Profile of the Simple Features Profile of the OGC GML Spec v3.3 (edxl-gsf) and the Profile of the Customer Information Quality v3.0 (edxl-ciq) are being resolved.

Those supporting specs have been passed through to create a nimble mechanism for elements that are used across the EDXL family. We now have the EDXL-SitRep spec pushing through for its first Public Review this week and next. So that work will be at a point where we can set it aside for the review process and give this the focus it deserves. However, we spoke briefly about the logo this week in Collateral and Documents SC meeting in addition to an EDXL Poster for the NIEM Training Event and the IAEM Conference.

Given all that, the logo will be the main topic for the 23rd and we hope you can attend. We have a report due on the various uses to which the logo is anticipated to be used, including the more general corporate identity type programs for letterhead and business cards as well as electronic identity management, so we should be well grounded a week from next Tuesday.

Cheers,
Rex

On 8/10/11 4:54 PM, Trott, Gregory wrote:

FF6E510A52664144B394B9BB1F45BB72325AACAC@ACTDC01ML01C.agdnet.ag.gov.au" type="cite">

UNCLASSIFIED

C&D SC members,

 

I saw the Draft Meeting Notes from the C&D Telecon held on Aug 9^th, and noted the issue about proposed material from myself that has not yet been received by Werner or Rex.  Now that my membership status has been upgraded I can post information onto Kavi, so please find the missing material listed below.

 

I also noted the intention to hold the next C&D SC meeting on Aug 23^rd from 4-5pm ET, to allow me to participate.  Thank you for that consideration.  I will plan to participate and will look out for the dial in numbers (the time will be 6-7am in my location)

 

 

 

The following contributions are offered from Australian CAP users to the discussions about development of a CAP icon symbol for future use on websites.   The comments are provided from two Australian CAP User organisations (Bureau of Meteorology and a State-based Emergency Service Agency) and relate to each of the 4 icon solutions that were being discussed back in the July timeframe.  Please refer to the attached image file regarding the four CAP icon symbols that have been discussed by the Australian CAP Users to date. 

 

Icon 1 represents nothing more than a printout of the CAP acronym – we feel it is meaningless in an iconic sense.

 

Icon 4 is possibly a bit too busy.  Best to keep it reasonably simple.

 

Icons 2 & 3 - the inclusion of the standard RSS icon as a key component, conveys an implied message that CAP is limited to, or is a subset of, the RSS protocols - and is limited to RSS type applications. This may not be the preferred message that OASIS wishes to convey, so an alternative approach is probably required to avoid any unintended associations with the RSS symbol.

 

An alternate but less formal symbol that could be considered might be the baseball cap symbol as currently used on the CAP Cookbook website, with the CAP abbreviation located beside it or on it. The analogy is similar to the way a padlock symbol is often associated with a secure/non-secure website and an envelope symbol is used for email.

 

 

 

Greg Trott

CAP-AU Project Manager

Australian Government Attorney-General's Department

Tel: +61 - 2 - 6141 3904 

Email: Gregory.Trott@ag.gov.au

 

---

If you have received this transmission in error please
notify us immediately by return e-mail and delete all
copies. If this e-mail or any attachments have been sent
to you in error, that error does not constitute waiver
of any confidentiality, privilege or copyright in respect
of information in the e-mail or attachments.

---

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