[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: Fwd: RE: [emergency] Fwd: Re: [cam] Re: [xml-dev] What dowant in a FAQ for a new spec
Rex - Mindful of Jamie's advice on yesterday's call, I'd like to suggest that we keep our focus on the immediate "fact sheet" project and not get sidetracked just yet on larger and longer-term projects like FAQ's or implementation guides... especially since we have limited time (and a limited number of people offering to do the actual writing work. ;-) I expect to circulate a first cut at the fact sheet tomorrow. - Art PS - I think we should be careful how we talk about APIs. An API describes a particular implementation and frequently requires or implies a particular programming environment. CAP is a messaging standard, not an application standard. DMIS has an API, and other systems have their own interfaces, some similar, some different. But the CAP message itself is not defined by any particular API. (That's one way, although perhaps not the best, of explaining the phrase "transport agnostic.") At 10:48 AM -0800 2/25/04, Rex Brooks wrote: >Hi Everyone, > >Please excuse the rather disorganized way in which I have gone about >this. Adding a new and very non-trivial task to a list that was >already longer than I can adequately address was not wise, but I >think we have a fairly reasonable basis to get started in terms of >the most basic questions that we should answer in the FAQ. > >I have attached the Content Assembly Mechanism TC's brochure as >another example of collateral support materials that we should >consider developing. > > If we take Eleanor's question as the basis for the FAQ and David's >numbered points as the basis for a brochure-type document, and start >working on some newsletter articles, perhaps based on some of the >following specific topics, I think we would have the arena just >about covered. > >Having beaten myself to shreds on the WSRP Primer (just one section >of it), I'm not ready to start an implementation guide real soon, >and I would suggest that one of the representatives of one of the >firms in the TC who have developed implementations would be better >qualified for that. I also suggest working from the message logs >(with and without SOAP) that CAP alerts are generated by and show >how those are used in implmentations to generate the markup which an >emergency manager (end-user) sees and uses would be the best way to >proceed for encouraging adoption by developers. > >Here's my list of specific questions: > >Is there an API? Yes. More than one? Yes. DMIS http://www.cmi-services.org/ > >Are there examples? Yes. http://www.edis.ca.gov/cap/ > >Is there a support community? Yes, Emergency Interoperability Consortium > > (We need a member to explain what the current status is, and maybe >someone should correct the article found below. People will get >confused if they see OASIS and EIC claiming development of CAP. >http://www.homelandsecurityintelwatch.net/200401/storyinterop.html ) > >What does "transport agnostic" mean? (Art explains this better than I could.) > >Ciao, >Rex > > > > >>From: "Robinson, Eleanor" <Eleanor.Robinson@associates.dhs.gov> >>To: 'Rex Brooks' <rexb@starbourne.com> >>Subject: RE: [emergency] Fwd: Re: [cam] Re: [xml-dev] What do want >>in a FAQ for a new spec >>Date: Wed, 25 Feb 2004 10:07:15 -0500 >>X-Rcpt-To: rfc822;rexb@starbourne.com >>X-DPOP: Version number supressed >>Status: U >> >>My two cents: >> >>What is the value being added by the FAQ? Can we provide good tips for >>technical implementation of the spec in a timely manner? Are there early >>implementers of the spec who can provide some good general questions/answers >>to start the FAQ off on the right foot? >> >>Eleanor >> >>-----Original Message----- >>From: Rex Brooks [mailto:rexb@starbourne.com] >>Sent: Wednesday, February 25, 2004 10:34 AM >>To: emergency@lists.oasis-open.org >>Subject: [emergency] Fwd: Re: [cam] Re: [xml-dev] What do want in a FAQ for >>a new spec >> >>>From: "David RR Webber" <david@drrw.info> >>>To: "Chiusano Joseph" <chiusano_joseph@bah.com>, >>> "Rex Brooks" <rexb@starbourne.com> >> >Cc: <egov@lists.oasis-open.org>, >>> <wsrp@lists.oasis-open.org>, >> > <cam@lists.oasis-open.org>, >>> <xml-dev@lists.xml.org>, >>> <public-ws-chor@w3.org> >>>Subject: Re: [cam] Re: [xml-dev] What do want in a FAQ for a new spec >>>Date: Wed, 25 Feb 2004 00:12:54 -0500 >>>X-Priority: 3 >>>X-Rcpt-To: <rexb@starbourne.com> >>>X-DPOP: Version number supressed >>>Status: U >>> >>>Rex, >>> >>>That's easy >>> >>>#1 - the vision and the motivation (why is this happening?) >>>#2 - the appropriateness and the need (value / fit to existing work) >>>#3 - technical approach / innovation / chair / feasibility >>>#4 - applicability to work I am contributing to / part of / using >>>#5 - social benefit(s) / delivery schedule / sponsors >>> >>>Thanks, DW. >>> >>>----- Original Message ----- >>>From: "Chiusano Joseph" <chiusano_joseph@bah.com> >>>To: "Rex Brooks" <rexb@starbourne.com> >>>Cc: <egov@lists.oasis-open.org>; <wsrp@lists.oasis-open.org>; >>><cam@lists.oasis-open.org>; <xml-dev@lists.xml.org>; >><public-ws-chor@w3.org> >>>Sent: Tuesday, February 24, 2004 6:20 PM >>>Subject: [cam] Re: [xml-dev] What do want in a FAQ for a new spec >>> >>> >>>> Rex Brooks wrote: >>>> > >>>> > Hi Folks, >>>> > >>>> > Please excuse the cross post, but I'm looking for two kinds of >>>> > questions that you want answered when you are evaluating a new >>>> > specification to decide if you think it is worth exploring further to >>>> > determine if you think it is ready for adoption. >>>> > >>>> > First, what is most immediately important, or else you wont look >>>further. >>>> >>>> I can't say that this is #1, but I always look at who's behind the >>>> specification in terms of both authors (vendors/federal >>>> agencies/consulting firms, etc.) and consortium (if there is a >>>> consortium). >>>> >>>> Kind Regards, >>>> Joe Chiusano >>>> Booz | Allen | Hamilton >>>> Strategy and Technology Consultants to the World >>>> >>>> > Second, what do you look for in ease of implementation. >>>> > >>>> > I am asking because I'm helping with a FAQ for a spec that is moving >>>> > toward approval, and we need to build a FAQ to help evaluators make >>>> > these kinds of decisions. >>>> > >>>> > Thanks, >>>> > Rex >>>> > -- >>>> > Rex Brooks >>>> > GeoAddress: 1361-A Addison, Berkeley, CA, 94702 USA, Earth >>>> > W3Address: http://www.starbourne.com >>>> > Email: rexb@starbourne.com >>>> > Tel: 510-849-2309 >>>> > Fax: By Request >>>> > >>>> > ----------------------------------------------------------------- >>>> > The xml-dev list is sponsored by XML.org <http://www.xml.org>, an >>>> > initiative of OASIS <http://www.oasis-open.org> >>>> > >>>> > The list archives are at http://lists.xml.org/archives/xml-dev/ >>>> > >>>> > To subscribe or unsubscribe from this list use the subscription >>>> > manager: <http://www.oasis-open.org/mlmanage/index.php> >>>> >>>> To unsubscribe from this mailing list (and be removed from the roster of >>>the OASIS TC), go to >>>http://www.oasis-open.org/apps/org/workgroup/cam/members/leave_workgroup.ph >>p. >>>> >>>> >> >> >>-- >>Rex Brooks >>GeoAddress: 1361-A Addison, Berkeley, CA, 94702 USA, Earth >>W3Address: http://www.starbourne.com >>Email: rexb@starbourne.com >>Tel: 510-849-2309 >>Fax: By Request >> >>To unsubscribe from this mailing list (and be removed from the roster of the >>OASIS TC), go to >>http://www.oasis-open.org/apps/org/workgroup/emergency/members/leave_workgro >>up.php. > > >-- >Rex Brooks >GeoAddress: 1361-A Addison, Berkeley, CA, 94702 USA, Earth >W3Address: http://www.starbourne.com >Email: rexb@starbourne.com >Tel: 510-849-2309 >Fax: By Request > >Attachment converted: Macintosh HD:CAM_brochure_draft1_15Feb04.doc >(WDBN/MSWD) (0017DDA4) >To unsubscribe from this mailing list (and be removed from the >roster of the OASIS TC), go to >http://www.oasis-open.org/apps/org/workgroup/emergency/members/leave_workgroup.php.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]