Hey guys,
As promised in the last TC meeting, here’s the
questions that Mr. Charroux sent in and our responses. I haven’t
heard anything back since my reply.
--Josh
From: Josh Shows
Sent: Wednesday, December 19, 2007 8:33 AM
To: Carl Charroux
Subject: RE: CAP Questions
Hi Carl,
I’m afraid there
isn’t currently a lot of detailed documentation available for CAP.
Our committee is working to rectify that but we’re just really getting
started. Please let me know any other issues or questions that you have
about CAP. It would be a big help in as we try to identify the areas to
initially focus on. In answer to your question, the application of scope
rules are going to depend on your system implementation. If you have
multiple systems talking to each other through a switch, it would probably be
the switch’s job. If it is point to point it would probably be the
receiving system. I’m afraid that’s the best I can do without
knowing more about your implementation. Please let me know if that
doesn’t answer your question and definitely let me know about any other
problems you encounter.
--Josh
From: Elysa Jones
[mailto:ejones@warningsystems.com]
Sent: Sunday, December 16, 2007 10:08 AM
To: Carl Charroux
Cc: Josh Shows; Dee Schur
Subject: Re: CAP Questions
Hi Carl,
Thanks for your questions and interest in CAP. I am copying Josh Shows on
this response as he is the chair of the OASIS Adoption Subcommittee. They
are currently working to identify what issues folks have with implementing
CAP. We are hoping that some good documentation and use cases will come
out of this effort.
I also encourage you to become a member of OASIS and get involved on the
Emergency Management Technical Committee so that you can provide input to the
standard as it evolves from its 1.1 version. For that reason, I am also
copying Dee Schur about your interest.
Additionally, I will respond to your comment about the security of the message,
recipients, etc. You may be interested in another OASIS Standard that has
come from our TC, the EDXL-DE (Distribution Element). The DE provides a
messaging standard for the content based routing assertions for emergency
data. It is designed to answer the question: to whom and under what
circumstances the associated data is to be sent/received. Security,
authorization, authentication, etc. are addressed in the DE. The
associated data is not limited to a CAP message but can be any data - xml or
non xml content. The "header" or DE identifies what data is to
follow, it's security and any specifics about it's contents important to the
routing of the message in addition to whom and under what circumstances it is
sent/received. Hope this helps.
Good luck in your pursuits,
Elysa Jones, Chair
OASIS Emergency Management Technical Committee
Program Manager
Warning Systems, Inc.
256-880-8702 x102
At 11:07 AM 9/11/2007, Carl Charroux wrote:
Hello,
I am creating an application to create CAP messages and am in need of
some info.
Is there a place where I can find detailed documentation? I already have the
spec and I have a good idea about most of the information required, but I have
specific questions like...
When the Scope of an alert is set to Private, I know the user must supply in
the Address field who has access to this message, but who handles the actual
security of hiding the alert from other users?
Same question for Restriction alerts?
Are the rules handled by the reader application?
Any info/insight would be appreciated.
Thanks
Carl Charroux
818.808.1764
CONFIDENTIALITY NOTICE: This e-mail transmission,
and any documents, files or previous e-mail messages attached to it, may
contain confidential information that is for the sole use of the intended
recipient. If you are not the intended recipient, or a person
responsible for delivering it to the intended recipient, you are hereby
notified that any disclosure, copying, distribution or use of any of the
information contained in or attached to this message is STRICTLY PROHIBITED. If
you have received this transmission in error, please immediately notify us by
reply e-mail at support@ntigroup.com
or by telephone at (866) HELP-NTI (435-7684), and destroy the original
transmission and its attachments without reading them or saving them to disk.
Thank you.