MHonArc v2.5.0b2 -->




















emergency message






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

--

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








Subject: Re: [emergency] Re: [sia-pilot6] [emergency] EDXL-DE routing and valueListUrn




From: "Carl Reed OGC Account" <creed@opengeospatial.org>
To: "SIA Pilot-6" <sia-pilot6@humanml.cim3.net>,       <emergency@lists.oasis-open.org>, "Rex Brooks" <rexb@starbourne.com>
Date: Tue, 21 Mar 2006 10:14:12 -0700






What he said . . .

And this also gets to the issue we discussed in the IF SC call today. There 
is considerable misunderstanding and need for education in the market place 
regarding the use and implementation of EDXL. Part of this education is that 
EDXL is a transport mechanism and must/can be viewed as independent from the 
technology implementation infrastructure. It should not matter if the 
enterprise (in the virtual sense) is implementing against a middleware bus, 
using SOAP/WSDL/UDDI, using ebRIM/XML, using an OGC Catalog, using the 
COMCARE EPAD application, using Java enterprise beans, etc. I view EDXL as 
technology implementation neutral - as it should be.

Am I wrong in thinking this?

Also, my previous email was more about making sure that the discussions in 
the EM TC on EDXL do not totally go totally US DHS/DoD centric. I understand 
the immediate requirement but we cannot loose sight of the bigger picture. 
For example, I would love to be able to recommend EDXL to ORCHESTRA in 
Europe.

Cheers

Carl