[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: CAP-AU Custodian involvement in RIM SC activities [SEC=UNCLASSIFIED]
|
UNCLASSIFIED Thanks Werner. I thought a response to your RIM SC invitation should be sent back via the RIM SC email List, so that all members could appreciate my predicament. I have re-subscribed to the RIM SC as a Member (vice my original status as Observer) so that I can monitor the layers / extensions discussions occurring in OASIS. I plan to contribute to the RIM SC discussions
if I detect any topics of interest to the Australian CAP Profile. I also plan to forward anything of interest from the RIM SC to my Australian CAP Stakeholder Group as they are the ones who possess the expertise to correctly interpret and implement the guidance in your draft
document. If they wish to feedback any observations, I will facilitate that through Kavi. When I recently downloaded the Extensions document I have to admit that it made little sense to me as I have no experience with EDXL or XML. I am not the right Australian person to get involved in the RIM SC
technical discussions as I have no expertise or experience in using CAP or EDXL or XML; but I will be aiming to interact with OASIS and RIM SC on behalf of Australian CAP Users for anything that may impact the CAP-AU Profile. I won’t be willing to participate in the RIM SC telecons at 1200-1300 US EST, as this is 0400 my time and I don’t have my Department’s approval to be working at that time of the day (due to OH&S and overtime
approval issues). I am also not driving any agenda items at the RIM SC meetings so the value of my participation would be extremely minimal anyway. I believe most value can be gained by me monitoring related posts on Kavi during my business hours and posing
questions to the RIM SC as necessary to clarify ambiguities. Once a formal OASIS position is agreed for Extensions and Layers, we should request OASIS to arrange a briefing session for interested global stakeholders (Video conference or Skype etc) to explain
the concepts to an Australian audience – this approach would ensure that the right experts gain first hand input from the OASIS experts (rather than relying on me to provide second hand information about topics I am not expert in). I hope you understand
my predicament. Cheers Greg Trott Custodian for the Australian Government standard for the Common Alerting Protocol – Australia Profile (CAP-AU-STD) Australian Government Attorney-General's Department From: Joerg, Werner [mailto:Werner.Joerg@iem.com]
Greg, This looks to me like a good test-candidate for the extensions concepts that are being worked out in the RIM SC. Here is a link to a draft document
EDXL_Extensions_Draft_ver_1.doc - would be great if you could join in the on-going discussions (see kavi
for meeting details). Best regards, Werner From:
emergency@lists.oasis-open.org [mailto:emergency@lists.oasis-open.org]
On Behalf Of Trott, Gregory UNCLASSIFIED EM-TC Members, I am contacting you all in the hope that I can locate an organisation among the TC membership who has used Common Alerting Protocol (CAP) messages with Twitter and is willing to share their approach and experiences with CAP Users in Australia.
The reason I ask is because an Australian CAP User is seeking to generate all-hazard alerts to the public via twitter, using the CAP message standard to create the alert message. The Australian CAP User is interested in looking at any
examples where the hashtag and twitter message content are incorporated into a CAP message. Our initial thoughts are that either the OPTIONAL <headline> or <description> sub-elements could be used to incorporate the text that would be used in a character
limited twitter message that gets distributed via twitter feeds, and the following hashtags might appear in the message: authority releasing the alert; and the “official” tag for the particular emergency event. I attempted to use the Kavi search engine to search for “twitter” and “hashtag” keywords but found nothing related to my question, so I am hoping this email approach puts me in contact with a knowledgeable person within the EM-TC membership
who might be able to assist with this inquiry. Please let me know if there is an alternate method that OASIS would prefer me to use in the future to pose questions like this one. Regards, Greg Trott Custodian for the Australian Government standard for the Common Alerting Protocol – Australia Profile (CAP-AU-STD) Australian Government Attorney-General's Department 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. |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]