[CAP] CAP-list Digest, Vol 5, Issue 10
Mark D. Urban
docurban at nc.rr.com
Wed Nov 30 14:28:30 PST 2005
Here's one from Government Technology:
Interoperability Emergency Standards Successfully Demonstrated in Arizona
http://www.govtech.net/magazine/channel_story.php/97406
BTW- Is there any documentation regarding the accessibility advantages of
CAP? Something we may need to look at, since many states and the Federal
Government have legal requirements regarding persons with disabilities..
Regards,
-Mark D. Urban
919-395-8513 (cell)
Chair, North Carolina Governor's Advocacy Council for Persons with
Disabilities
Keep up with the latest in worldwide accessibility at
(http://www.icdri.org/)
-----Original Message-----
From: cap-list-bounces at lists.incident.com
[mailto:cap-list-bounces at lists.incident.com] On Behalf Of
cap-list-request at lists.incident.com
Sent: Wednesday, November 30, 2005 3:00 PM
To: cap-list at lists.incident.com
Subject: CAP-list Digest, Vol 5, Issue 10
Send CAP-list mailing list submissions to
cap-list at lists.incident.com
To subscribe or unsubscribe via the World Wide Web, visit
http://eastpac.incident.com/mailman/listinfo/cap-list
or, via email, send a message with subject or body 'help' to
cap-list-request at lists.incident.com
You can reach the person managing the list at
cap-list-owner at lists.incident.com
When replying, please edit your Subject line so it is more specific
than "Re: Contents of CAP-list digest..."
Today's Topics:
1. Re: Corrupt or faulty .pdf (Art Botterell)
2. Re: Open Source "caplib" (Art Botterell)
3. The Wired article has been posted online (David Stephenson)
4. CAP feed definiton format (Mick Jagger)
----------------------------------------------------------------------
Message: 1
Date: Tue, 29 Nov 2005 12:07:04 -0800
From: Art Botterell <acb at incident.com>
Subject: Re: [CAP] Corrupt or faulty .pdf
To: cap-list at lists.incident.com
Message-ID: <2449628A-0B1D-4D67-A655-B3CB853B0FBD at incident.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
On Nov 29, 2005, at 11/29/05 11:41 AM, Brian Butcher wrote:
> Page 10 of http://www.oasis-open.org/committees/download.php/14759/
> emergency-CAPv1.1.pdf is unreadable. The unreadable content is
> important.
Yes, apparently there was a file-conversion glitch in preparing that
file for the OASIS website. I'm told that a corrected version, or at
least an erratum, is in the works.
Meantime, I've posted the version I have of that object drawing at
<http://www.incident.com/cap/CAP_1.1_DOM.pdf>.
(Please note that this isn't a normative version... only what gets
posted on the OASIS website is official... I'm just posting this as a
convenience until the OASIS site gets updated.)
- Art
------------------------------
Message: 2
Date: Tue, 29 Nov 2005 15:39:11 -0800
From: Art Botterell <acb at incident.com>
Subject: Re: [CAP] Open Source "caplib"
To: cap-list at lists.incident.com
Message-ID: <2ED25B01-9968-48E0-BB81-729204FE9282 at incident.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
On Nov 29, 2005, at 11/29/05 7:16 AM, David R Robison wrote:
> Have you given any thought to hosting this library on
> SourceForge.net? This could be used to allow the CAP community to
> share and contribute in its on going development. Just a thought...
Thought about it briefly... but I wasn't sure there'd be so many
actual contributions that I couldn't just merge them in manually, so
for starters I did it the easy way (for me).
Also... I can't find the reference right now, but I have a vague
impression that sourceforge has some rules about the particular
licensing for projects it hosts. I've released caplib under the MIT/
X11 license, since I didn't want to let commercial shops' occasional
issues with GPL or other licenses get in the way of uptake. But
maybe I'm confused...
Anyway, my mind is open about it. Is there interest among the group?
- Art
------------------------------
Message: 3
Date: Tue, 29 Nov 2005 20:54:40 -0500
From: David Stephenson <D.Stephenson at stephensonstrategies.com>
Subject: [CAP] The Wired article has been posted online
To: cap-list at lists.incident.com
Message-ID:
<b035ac3b0511291754k477875c1t6eb3f1185002265b at mail.gmail.com>
Content-Type: text/plain; charset="us-ascii"
Art -- the Wired article featuring you is now online:
http://www.wired.com/wired/archive/13.12/warning.html?pg=2&topic=warning&top
i
c_set=
Nice to see you get this recognition!
--David Stephenson
--
W. David Stephenson | Principal | Stephenson Strategies
D.Stephenson at Stephensonstrategies.com
335 Main St. Medfield, MA 02052 | (508) 359-5112
Making Homeland Security Everyone's BusinessTM
"W. David Stephenson is outlining a new approach to national security that
is closer to a 'new politics' way of organizing a government service than
anything I've seen." -- Blogging of the President
"Google 'homeland security blog' and security consultant W. David
Stephenson's site tops the list." -- CIO.com
Demolishing and replacing obsolete paradigms since 1988. (:o (|)
------------------------------
Message: 4
Date: Wed, 30 Nov 2005 11:25:05 -0500
From: Mick Jagger <lists at jpw.biz>
Subject: [CAP] CAP feed definiton format
To: cap-list at lists.incident.com
Message-ID: <20051130112505.295418fc.lists at jpw.biz>
Content-Type: text/plain; charset=US-ASCII
Hi,
I'm in the process of developing a CAP-aware alerting client that
can access all manner of published CAP feeds. However, despite the great
work done on development of the CAP standard itself, the methods of
implementation are varied - with good reason, making supporting different
feeds difficult. To account for this, I've started scratching out some
ideas for a "feed definition" format that would be used to describe a CAP
feed and what is needed to process it.
For instance, feed X is published using an ATOM index, with no
message encryption, is updated only once a day, covers a specific geographic
area, and only issues MET alerts. The feed definiton file would be
accessible as part of subscribing to this feed and the monitoring client
would use it for configuration. This file would also be great for indexing
in a CAP feed search engine style application. A user can search this app
to find a feed for their home town, or if I'm on vacation, I can get all of
the local CAP feeds on my wifi-connected laptop at the hotel.
Briefly, here is some of the info about a CAP feed that could go
into this definition file. Distribution method and format (HTTP vs Email,
ATOM vs RSS vs single file), Encryption (Encrypted vs Signed, and the
current public key), Frequency (Immediate publishing vs regular interval
only), Geographic area (Covers a specific county, city, state), Location
codes (Specific location codes for filtering, ie EDIS zones), Authority (CAP
publisher), and also allow for custom elements specific to that
implementation.
I'd like to know what the list thinks about this idea? I'm already
using an ad-hoc implementation of this, should there be a process for
developing it instead?
--
lists at jpw.biz
--
------------------------------
_______________________________________________
CAP-list mailing list
CAP-list at lists.incident.com
http://eastpac.incident.com/mailman/listinfo/cap-list
End of CAP-list Digest, Vol 5, Issue 10
***************************************
More information about the CAP-list
mailing list