MHonArc v2.5.0b2 -->
emergency message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: EDXL-DE routing and valueListUrn
ALL
I have a reasonably mature strategy for creating valueListUrn lists and
how they can be used to deploy a national architecture for Alerting and
Warning. I have been trying to develop this to support Chips Disaster
Management efforts (e.g. EDXL-RM) and to allow for national sensor
capabilities (e.g. DNDO) to have the EDXL-DE routing system (execution
context) which provides the following capabilities:
1. Allow for establishment of Communities of Interest (COIs) where
appropriate authority can establish roles of entities, information
routing rules between them and issue certificate to ensure
authentication and authorization.
2. Permit interaction between COIs to instantiate robust MOUs enforced
by execution context allowing creation of national information grid.
3. Permit secure delivery of multiple levels of sensitive information
via signing, encryption and labeling within the EDXL-DE.
4. Allow abstraction of the implementation details (what) so national
planners can implement various operational concepts (documented in
DoDAF, FEA etc.) with minimal confusion on "how" it is accomplished.
I have tried to engage NIEM for over one year to explain these concepts
without success. There is finally understanding between the various
standards organization on how important this is to major government
implementations. On the other hand, major information providers are
claim our capabilities either don't exist or have never been
demonstrated. Both are not true and in fact the EDXL-DE is being used
in an operational system within the DoD. Unfortunately, it is not
branded as EDXL-DE since we have not issued the EDXL-DE OASIS standard
yet.
I need as many of the organization implementing EDXL-DE to attempt
sending outputs from your applications to the developing EDXL-DE routing
capability at NuParadigm in Saint Louis or our capability at Sandia
National Laboratories. Also, a generic ability to wrap CAP messages in
EDXL has been created and we need to discuss the security implications
of doing this from local applications or by the "execution context" for
legacy/warning-only CAP applications.
I need to be able to list all the capabilities of your applications even
if they use explicated routing (e.g. DMIS COGs) and have no security
capability. The design of our governments emerging national
capabilities is moving at lighting speed and EDXL-DE capabilities needs
to be a substantial portion of it. Attached are two briefings present
this past week on sensor routing.
David E. Ellis
Information Management Architect
(505) 844-6697