MHonArc v2.5.0b2 -->
















emergency message






[Date Prev]
 | [Thread Prev]
 | [Thread Next]
 | [Date Next]

--

[Date Index]
 | [Thread Index]
 | [List Home]








Subject: CAP 1.1 Issue # 11




From: "Aymond, Patti" <Patti.Aymond@ieminc.com>
To: Emergency_Mgt_TC TC <emergency@lists.oasis-open.org>
Date: Tue, 26 Jul 2005 10:59:26 -0500






I would like to offer some clarification on the issue CAP version that I
raised. Just as HTTP, SOAP, and other protocols include a version number in
their specification, I think CAP needs to do so as well.

A resolving schema namespace id is not required in a CAP message. If a CAP
message is received without one, the only sure way of determining what
version of the CAP specification the message follows is by process of
elimination while parsing the message. As more and more CAP specification
versions are released, the burden on developers discerning CAP version
numbers will increase.

I do hope this clarifies the issue.

Patti

Patti Iles Aymond, PhD
Senior Scientist
Bioterrorism Preparedness & Response

Innovative Emergency Management, Inc.
Managing Risk in a Complex World

8555 United Plaza Blvd.   Suite 100
Baton Rouge, LA 70809
(225) 952-8228 (phone)
(225) 952-8122 (fax)



IEM CONFIDENTIAL INFORMATION PLEASE READ OUR NOTICE:
http://www.ieminc.com/e_mail_confidentiality_notice.html







Follow-Ups:

Re: [emergency] CAP 1.1 Issue # 11
From: "Carl Reed OGC" <creed@opengeospatial.org>








[Date Prev]
 | [Thread Prev]
 | [Thread Next]
 | [Date Next]

--

[Date Index]
 | [Thread Index]
 | [List Home]