Re: [emergency] CAP 1.1 Issue # 11

["Carl Reed OGC" <creed@opengeospatial.org>]

Patti -

I support the idea of a version number 100%. Clients and servers need to be 
able to do version negotiation. Without this, then interoperability suffers 
(like perhaps none at all). All OGC specs have version numbers as part of 
the interface specification and this information is expressed in each 
interface call or payload encoding. An interesting side benefit is that 
applications can then actually support multiple CAP versions.

Cheers

Carl



----- Original Message ----- 
From: "Aymond, Patti" <Patti.Aymond@ieminc.com>
To: "Emergency_Mgt_TC TC" <emergency@lists.oasis-open.org>
Sent: Tuesday, July 26, 2005 9:59 AM
Subject: [emergency] CAP 1.1 Issue # 11


>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
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  You may a link to this group and all your TCs in 
> OASIS
> at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
>
>
>