Industry standards for the C2 Common Data Model & Framework

1. Industry Standards for C2 Common Core Data Model & Framework
Table of Contents
1. Introduction
2. Categories of Net-Centric Use Cases
3. XML Processing and Schemas
4. Metadata Tagging
5. Data Models and XML Representations
6. Data Transport
7. Enterprise Web of Services
8. Rich Internet Applications
9. Relationships among Standards
10. Conclusion and Recommendations
11. References
12. Appendix - Summary of Standards Information
13. Attachment - Web Services Protocol Functional Collection
14. Attachment - Instant Messaging Protocol Functional Collection
1. Introduction
The objective of this report is to "identify current and future specific standards and
technologies used by, and projected to be used by industry providers of IT for the DOD
C2 community" as requested in the draft CRADA Execution Plan. The report is divided
into several sections based on the initial input from JFCOM. The standards discussed in
this report include metadata tagging, data models, data transport, messaging, and rich
Internet applications. (Enterprise Web Services, XML schemas and Instant Messaging are
discussed in detail in NCOIC Protocol Function Collection documents that are attached to
this report.) The relationships among the standards are illustrated in an architecture
diagram. A conclusion presents some recommendations for future standards-based
activities. All of this information is summarized in a tabular form in an appendix.
A key issue is the role of the simpler standards (REST, RELAX NG, XML messaging,
standard message formats) vs. more complex standards (WS-*, XML Schema,
messaging, common data models and semantics). Another important question is when to
use the run-time discovery and composition of services and messages as opposed to
design-time static implementations. A categorization of the types of net-Centric use cases
can be very useful in helping to make these decisions.
2. Categories of Net-Centric Use Cases
Net-Centric architectures can be divided into three general categories based on the
relationships of participating nodes. In an analogy with earlier classifications, these
categories can be described as Intranet-Centric, Extranet-Centric and Internet-Centric.

2. This categorization should be considered as guidelines for recommending standards
decisions as opposed to a rigid classification. The essential definitions and scope are:
Intranet-Centric = Activities within a group that has common operational standards (e.g.
data models, middleware, processes, platforms). Recommended standards and technology
(e.g. Enterprise Service Bus) in this area are chosen by management based on specific
organizational requirements and standards.
Extranet-Centric = Collaboration across groups with different operational standards but
common interoperability standards (e.g. message formats, communication protocols,
collaborative processes) based on negotiation. This is the area where the NCOIC
recommended interoperability standardizations can have the biggest impact
Internet-Centric = Ad hoc interactions among diverse nodes and users based on public
standards (e.g. basic Web standards, network protocols, standard data representations)
which may not be deployed to all participants. This approach can also be used for rapid
development of non-mission critical applications within organizations. Within the
government application domain, there is increasing interest for emergency and stability
operations which should be addressed by the NCOIC.
Table 1 maps some key concepts to Intranet-Centric, Extranet-Centric and Internet-
Centric categories.
Concepts Intranet-Centric Extranet-Centric Internet-Centric
Business analogs Internal Enterprise Business to business Business to public
Examples of Use
Cases
Single organization
operations
Joint operations Emergency and
stability operations
Implementation
of standards
Mandated Negotiated Partial and de facto
Coupling
between systems
Tighter coupling Looser coupling Ad hoc coupling
Communities of
users
Communities of
interest (COI)
Cross COI
collaboration
External non-COI
collaborators
Governance Centralized pre-
defined policies
Contractual
agreements
Dynamic policies
enforced
User
authentication
Individuals users
known in advance
User organizations
known in advance
Dynamic users and
organizations
Middleware for
services
Enterprise Service
Bus
SOAP Web Services,
Service Gateways
Simple Web
services e.g. REST

3. Table 1 Mapping of concepts to use case categories
Figure 1 shows the relationship and interfaces between Intranet-Centric, Extranet-Centric
and Internet-Centric Standards
!
Figure 1 Relationship among use case categories and standards
3. XML Processing, Schemas and Data Binding
Structured markup enables multiple Internet-Centric standard approaches for parsing of
XML documents including Document Object Model (DOM) [1], the Simple API for
XML (SAX) [2] , and the Streaming API for XML (StAX) [3]. DOM is the W3C
Service
Discovery
Design-time Deployment and
Configuration
Run-time
Composition and
mashups
More static and
controlled
More dynamic based
on standards
Ad hoc and less
maintainable
Data sharing Common databases,
data models, and
semantics
Standard data models
and message formats
for data exchange
Public databases
and self describing
data in messages
XML Metadata Internal standards Shared standards Public standards

4. standard tree-based model for XML documents that is easier to access through an API.
However building and storing large trees can be costly in terms of processing time and
memory use.
The Simple API for XML (SAX) is an API for XML parsing that uses an event-driven
stream-based approach that avoids the need to build a tree structure. The Streaming API
for XML (StAX) is a Java API for pull-parsing of XML documents.
Data schemas are templates for describing instances of data content (e.g. documents,
messages). There are several templates that can be used to describe XML data content
including the XML Schema [4] definition developed by the Worldwide Web Consortium
and Relax NG [5] from OASIS which is now an ISO standard.
XML Schema is a W3C standard XML specification for defining the contents and
structure of XML documents RELAX NG is a simpler schema than W3C XML Schema
that can also be used for describing XML documents [6].
XML data binding [7] is the extraction of the content of XML documents to data objects
The Java API for XML Binding (JAXB) [8] is a standard from the Java Community
Process that uses XML Schemas to create bindings. Standards for other programming
languages are currently Intranet-Centric (i.e. organization specific) Using a programming
language API based on a schema is usually more efficient than parsing the full document.
XSLT [9] is a language for transforming XML documents into a tree structure e.g. to
create a new XML document. The transformation is achieved by matching patterns with
elements in the document. When a pattern is matched, a template is instantiated as part of
the target tree.
4. Metadata Tagging
XML schemas and tags can be used to give initial structure to data but it is not sufficient
for semantic interoperability. There are several standards that can be used to provide
more extensive information about data content to facilitate interoperability. For structured
data, standards include Resource Description Framework (RDF) [10], Web Ontology
Language (OWL) [11] and Microformats [12]. There is an emerging standard for
unstructured data called Unstructured Information Management Architecture (UIMA).
The standards for the usage of specific metadata tags can be Intranet-Centric (e.g.
internally mandated), Extranet-Centric (e.g. cross-organizational agreements) or Internet-
Centric (e.g. public standards)
Microformats are markup components embedded in HTML documents. They provide a
simple ways to provide information in standardized formats. Internet-Centric examples
include hCard for contact information and hCalendar for scheduling events.
Microformats could add value in Intranet-Centric and Extranet-Centric applications.

5. The Resource Description Framework (RDF) is a W3C standard for adding semantic
content to XHTML pages and XML documents. It is based on triplets in subject-
predicate-object form that can be expressed in XML syntax. The subject and predicate are
resources that are identified by Universal Resource Identifiers (URIs). The object can be
a resource or a Unicode string. RDF Schema is an RDF vocabulary for describing
properties and classes of RDF resources including an inheritance semantics.
The Web Ontology Language (OWL) OWL extends RDF Schema by adding more
vocabulary for describing relations between classes (e.g. disjointness), cardinality (e.g.
"exactly one"), equality, richer typing of properties, characteristics of properties (e.g.
symmetry), and enumerated classes.
Unstructured Information Management Architecture (UIMA) [13] is a framework and
SDK for developing such applications being standardized by OASIS. UIMA applications
input plain text and extract entities and related information. The framework supports the
decomposition of these applications into components and manages the collaboration
among components. The components must support the framework APIs and provide
metadata in XML descriptor files. There is an Apache implementation of UIMA under
development.
5. Data Models and XML Representations
Standard data models are used in many industries to enable Extranet-Centric
collaboration across diverse companies. Some examples include ACORD [14] for
insurance, HL-7 [15] for healthcare, and FIX [16] for finance.
In the C2 space the Command and Control Information Exchange Data Model (C2IEDM)
[17] and its extension, Joint Consultation Command & Control Information Exchange
Data Model (JC3IEDM) [18] provide standardized data model endorsed by many
organizations. The NATO Multilateral Interoperability Programme (MIP) [19] is leading
the standardization effort for C2IEDM and JC3IEDM. There are also Intranet-Centric
data models in many defense organizations.
Extranet-Centric industry ontologies have been defined in some cases to ensure semantic
interoperability. IBM has made available Industry Ontology Packs for its customers.
Work is underway to add a semantic layer on top of C2IEDM.
Intranet-Centric master databases are used to rationalize data across multiple systems.
Standardized data models can be used as the schemas for master databases. Legacy data
models can be mapped to the standardized model by adaptors. The initial application in
many industries is Customer Data Integration (CDI). CDI enables data to be shared
across diverse multiple applications. A similar approach has been used in demonstrations
of C2 interoperability using C2IEDM as the schema for a master database.

6. Standardized structured message formats can enable information exchange. There are
many examples from industry (e.g. EDI [20]) and military applications (e.g. VMF [21]).
Basing the message format on a standard data model or ontology enables more robust
interoperability. The Coalition Battle Management Language (C-BML) [22] is a new
messaging format for C2 Information Exchange being built on top of JC3IEDM.
XML representations can be used for the message formats. Several industries have
adopted standardized XML formats e.g. XBRL [23] for business reporting. Extensible
Battle Management Language (XBML) [24] is a prototype that uses XML representations
of C2IEDM data and Web Services interfaces for information exchange.
6. Data Transport
There are many messaging products that can be used for data transmission. There are
several standards available for messaging. For Java applications, the Java Message
Service (JMS) [25] provides a standard application programming interface to messaging
middleware. JMS support message queuing and publish/subscribe messaging.
A new standard for near real-time structured data transport is the Data Distribution
Service (DDS) API [26] from the Object Management Group. DDS supports QoS-based
publish/subscribe messaging based on pre-defined topics. There is a standard DDS
Interoperability Protocol [27] that enables different implementations of DDS to work
together.
The Extranet-Centric Message Exchange Mechanism (MEM) [28] and event-driven Data
Exchange Mechanism (DEM) [28] have been defined by the Multilateral Interoperability
Programme (MIP) that also developed C2IEDM.
The use of standard XML data representations for information exchange is increasing.
Textual XML formats can be very verbose compared to binary messages. Efficient XML
[29] is a newly adopted standard from the Worldwide Web Consortium (W3C) that
supports XML compression that is competitive with existing binary formats.
Instant Messaging (IM) is a commonly used collaboration tool for users to exchange
information. There are several products in this area that have been adopted as Intranet-
Centric standards within organizations. The Extensible Messaging and Presence Protocol
(XMPP) [30] is an IETF XML-based instant messaging standard that has also been
endorsed by NCOIC's Building Blocks team. The Session Initiation Protocol (SIP) [31] is
an IETF standard for initiating and managing sessions that can work with XMPP. The SIP
Protocol for Instant Messaging & Presence Leveraging (SIMPLE) is an IETF standard
that overlaps XMPP and is also included in the NCOIC IM PFC. [32] The Real-time

7. Transport Protocol is the IETF standard for transmitting non-XML multimedia data that
can be used in conjunction with XMPP and SIP. [33]
7. Enterprise Web of Services
One of the key issues for the future of distributed architectures is the role of SOAP-based
Web Services [34] vs. services based on the original Web architectural style called
Representational State Transfer (REST). [35] SOAP-based Web Services use stacks of
standards (WS-*) that have been developed by the W3C and OASIS. [36] This
architecture has similarities to earlier middleware approaches in that many capabilities
are made available at the cost of greater complexity an increased difficulty in maintaining
interoperability. The REST approach is simpler and more scalable but has fewer built-in
standard services. [37]
In general, SOAP-based services are useful for Extranet-Centric architectures where
robust supporting services and security are required. REST is often used for Internet-
Centric services to take advantage of increased simplicity and Web scalability capabilities
(e.g. caching). There is Web Application Definition Language (WADL) [38] under
development for REST services that is an attempt to add descriptive information similar
to WSDL for SOAP Services.
The NCOIC Interoperability Framework (NIF) group created a Web Services Protocol
Function Collection (PFC) with detailed descriptions and recommendations on Web
Services and REST architectures. The PFC document is attached to this report and is the
NCOIC-endorsed approach.
.In Intranet-Centric architectures, Enterprise Service Buses (ESBs) [38] and existing non-
HTTP middleware are frequently deployed for increased functionality and performance
In general, there are no Extranet-Centric standards beyond Web Services for
interoperability across ESBs. However there is a Service Data Objects (SDO) [39]
standard under development by OASIS that provides a data graph format for data
exchange across distributed applications. Data Access Services (DAS) [40] is a related
standard for mapping data from multiple sources (e.g. databases, XML) bi-directionally
to SDO.
The Business Process Execution Language (BPEL) [41] is a declarative XML-based
language for specifying executable composite processes. BPEL can interoperate with
ESBs and Web Services.
8. Rich Internet Applications
Recently there has been a rapid increase in Web-based applications with richer user
interfaces than traditional browser application. This has been made possible by the use of

8. JavaScript, page content descriptions (e.g. XML), and partial updating of sections of Web
pages. This technical approach has been given the name Asynchronous JavaScript and
XML (Ajax) [42]. There are many toolkits that support Ajax. A new industry group called
the OpenAjax Alliance [43] is developing standards to enable interoperability across
these toolkits.
There are several other technologies that can be used to support rich interface
applications. One example is Web data feeds such as RSS [44] and Atom [45]. RSS is a
family of standards for distributing data that is posted to subscribed Web sites. RSS
content is displayed through a reader that regularly checks sites that for new content and
downloading updates. Atom is a newer Web feed alternative to the RSS family that has
been endorsed by the IETF.
Ajax, Web Feeds and othe data sources (e.g. Google Maps) can be combined to rapidly
create Rich Internet Applications. This approach is often called "mashups"[46]. Mashups
and services compositions can also be used together to create distributed applications on
top of existing capabilities. Typically mashups have been employed with Internet-Centric
standards (e.g. REST services). There are currently no standards for combining mashups
and Extranet-Centric Web Services.
9. Relationship among Standards
Figure 2 shows the architectural relationships among standards
!

9. Figure 2 Relationships among Standards
Figure 2 show the role of the individual standards in an end-to-end implementation. The
implementation layers and some associated standards are:
Web Client Applications - Rich Interface Application
Web Message Bus - XML Messaging
Enterprise Service Manager - SOAP servers
Composites - Business Process Execution Language (BPEL)
Enterprise Service Bus - Java Message Service (JMS)
Enterprise Data and Systems - Service Data Objects (SDO), Data Access Services (DAS)
Gateway - XSLT transformations
External Networks- Efficient XML, Data Distribution Services (DDS)
10. Conclusion and Recommendations
{TBD based on future discussions}
11. Appendix -Summary of Standards Information
Table 2 summarizes standards information from this document and the NCOIC Web
Services Protocol Functional Collection Document.
Standard or
Technology
Description
and Purpose
Status and
Future Plans
Relationships to
Other
Standards
Recommendatio
ns
SOAP was
initially the
Simple Object
Access Protocol
SOAP is a
protocol for XML
messaging that is
used for remote
procedure calls
and one-way
messaging
SOAP is a W3C
standard and is
used in many Web
Services
deployments
SOAP is the
foundation of the
Web Services stack
SOAP-based Web
services should
comply with Simple
Object Access
Protocol (SOAP) 1.1
W3C Note, dated 8
May 2000.
Web Services
Definition
Language
(WSDL)
WSDL is an
XML-based
service description
for web services.
The WSDL
defines services as
collections of
network endpoints,
or ports
WSDL is a W3C
standard. WSDL
2.0 is the latest
version
WSDL is used in
many Web
Services
applications
WSDL is used to
specify SOAP
interfaces
SOAP-based Web
services should
comply with Web
Services Description
Language (WSDL)
1.1 W3C Note, dated
15 March 2001.

10. WS-
Interoperability
(WS-I)) Basic
Profile
WS-I has several
profiles consisting
of sets of Web
Services. The
Basic Profile 1.2
includes SOAP
1.1, WSDL 1.1
and UDDI v2
WS-I is an
industry group
whose members
include the leading
software
companies
including IBM,
Microsoft, BEA,
Oracle etc.
Additional WS-I
Profiles include the
Basic Security
Profile and the
Reliable Secure
Profile
SOAP-based Web
services should
comply with WS-I
Basic Profile
Version 1.1, dated
10 April 2006 and
other WS-I profiles
SOAP-Based
Web Services
stacks
SOAP is a W3C
standard. The Web
Services
Interoperability
Organization
(WS-I) publishes
profiles of
interoperable
standards
There are many WS-
* standards built on
top of SOAP that are
under development
at the W3C and
OASIS
SOAP-based Web
services should
comply with WS-I
Basic Profile
Version 1.1, dated
10 April 2006.
Extranet-Centric
collaborators should
agree on supported
standards
Representationa
l State Transfer
(REST)
REST is a set of
architectural
principles that are
an alternative to
the SOAP WS-*
approach
REST is based on
existing W3C
standards
There are many
large-scale
implementation of
REST-based
services
Ajax and mashup
applications can be
built on top of REST
Services
REST is sometimes
proposed as a
simpler alternative
to WS-* Web
Services
Use RESTful
services for large-
scale Internet-
Centric deployments
RESTful Web
services should track
all necessary session
state with the client
and not the server.
XML Schema XML Schema is a
specification for
templates that can
be used to validate
conforming XML
data content/ XML
Schema Datatypes
(XSD)define the
data types that can
be used in XML
content
XML Schema is a
W3C standard
XML Schema is
used in many data-
Centric XML
applications
There are several
alternatives to XML
Schema including
DTDs and Relax-
NG
W3C XML Schema,
as specified in XML
Schema Part 1:
Structures Second
Edition W3C
Recommendation,
dated 28 October
2004 and XML
Schema Part 2:
Datatypes Second
Edition W3C
Recommendation,
dated 28 October
2004
RELAX NG Schema language
for XML
RELAX NG is an
OASIS standard
Simpler schema
language alternative
to XML Schema
RELAX NG
Schema, as specified
by the RELAX NG
OASIS Specification
dated 3 December
2001

11. Web
Application
Description
Language
(WADL)
A machine
process-able
description of
HTTP-based Web
applications.
WADL describes
the related
available
resources, their
supported
inputs and outputs,
and links between
resources
Specification has
been stable since
Nov 2006 but has
not yet
been submitted to
a standards body.
Future Plans
depends on
feedback from
implementers.
Alternatives
include
development of a
new version of the
specification and/
or
submission to a
standards body.
WADL is an XML-
based language.
WADL depends on
W3C XML Schema
or RELAX NG for
describing XML
message formats and
uses XHTML for
embedding human-
readable
documentation
within a WADL
description.
Track development
of WADL to see if it
becomes a standard.
Microformats Microformats are
standardized
markup embedded
within HTML.
Semantics can be
embedded and
encoded using
HTML attributes
such as rel, rev,
and class.
Examples of
microformats
include hCard for
contact
information and
hCalendar for
events.
The Web site
microformats.org
is coordinating
information
dissemination
about
microformats
Many Web sites
are using
microformats
Microformats make
it easier to create
mashups
Use de facto
industry standard
microformats.
Consider the
possible definition
of additional
microformats
targeted at domain-
specific content
Extensible Style
Sheet Language
Transformation
(XSLT)
XSLT is designed
to translate XML
documents into
other XML
documents or
other formats.
XSLT uses
templates, pattern
matching and style
sheets.
XSLT is a W3C
standard currently
in version 2.0
XALAN-Java is
an open source
implementation of
XSLT
XSLT uses XPath
for parsing through
XML documents
Evaluate the recently
released XSLT 20
(Jan 2007)
Business
Process
Execution
Language
(BPEL)
BPEL provides a
declarative format
for describing
executable
composite
processes
BPEL is an OASIS
Standard
BPEL can
interoperate with
Web Service
standards.
Careful evaluation is
recommended
before using BPEL
to ensure that it
meets needs

12. Service Data
Objects (SDO)
Service Data
Objects is a data
graph format for
representing data.
Read and write
access is available
from multiple
languages
Service Data
Objects has been
submitted to
OASIS for
approval
Apache Tuscany is
an open source
implementations .
Multiple vendor
versions
Service Component
Architecture uses
SDO as a preferred
data transport
Should be evaluated
in cases (e.g.
Extranet-Centric)
where multiple
diverse applications
have to exchange
data
Data Access
Services (DAS)
Data Access
Services provide
bidirectional
mappings between
SDO and multiple
data sources (e.g.
XML, relational
data bases)
Data Access
Services has been
submitted to
OASIS for
approval
Apache Tuscany is
an open source
implementation.
Multiple vendor
versions are
available.
SDO uses Data
Access Services to
interface to data
sources
Should be used to
provide the
interface to data
stores when SDO is
the data format for
data exchange
Efficient XML Efficient XML is a
specification for
an encoding
format that allows
efficient
interchange of the
XML Information
Set.
Efficient XML is a
W3C standard
AgileDelta
developed the
Efficient XML
format. They sell
an implementation
including API
interfaces to and
from applications
Can be used to
reduce the size of
XML messages that
are used by many
industry and
domain-specific
standards
Should be evaluated
for transmitting
XML data over
networks with
constrained
bandwidth (e.g.
mobile networks)
Data
Distribution
Services (DDS)
Specified API for
data-Centric
publish-and-
subscribe
messaging for
real-time
distributed
systems
Support
subscription by
topics, QoS, and
data objects
Data Distribution
Services is an
OMG standard.
New DDS
Interoperability
Protocol standard
will enable
interoperability
between DDS
implementations
DDS products are
available from RTI
and Prismtech
DDS can be
interfaced to ESBs
DDS can use
Efficient XML
compression to
support XML data
distribution
Should be used for
data distribution on
networks where near
real-time delivery
and QoS guarantees
are important
considerations

13. Unstructured
Information
Management
Architecture
(UIMA)
Defines standard
interfaces for
processing
unstructured
information
(automatically
generating meta-
data for text,
image, and audio
as part of
distributed
workflows) and
declarative
mechanisms for
describing the
specific behaviors
of these interfaces.
The DARPA -
Sponsored UIMA
Working Group
was formed by
DARPA and IBM
in January 2005 to
facilitate
cooperation in
advancing the
UIMA
architecture.
IBM makes UIMA
available as a free
SDK and makes
the core Java
framework
available as open
source software
Aligned with SE
standards/tools like
OMG/MOF/UML,
aligned with XML
standards (XML
Schema and XMI)
The UIMA platform
independent spec
allow for different
transports. To
provide immediate
value it uses WSDL
to define SOAP
bindings for the
general analytic
interfaces..
UIMA seems to be
the leader
framework for
generating metadata
and creating
workflow processes
for unstructured.
However it should
be evaluated
carefully for
functionality in
specific domains
Joint
Consultation
Command &
Control
Information
Exchange Data
Model
(JC3IEDM)
JC3IEDM is
intended to
represent the core
of the data
identified for
exchange across
multiple functional
areas and multiple
views of the
requirements.
The program is
managed by the
Multilateral
Interoperability
Programme (MIP)
JC3IEDM is a
successor to
C2IEDM. It is being
used to develop new
battle management
languages
The scope of
JC2IEDM is an
organizational
decision for Intranet-
Centric use cases.
For Extranet-Centric
information
exchange JC3IEDM
seems to be a
preferred data
model
Resource
Description
Framework
(RDF)
RDF provides a
lightweight
ontology system to
support the
exchange of
knowledge on the
Web.
RDF is a W3C
standard
RDF is the basis for
other Semantic Web
standards
The eventual impact
of RDF and
Semantic Web
technologies on
industries is still not
clear.
Web Ontology
Language
(OWL)
OWL provides a
ontology language
that can to
describe data
content
OWL is a W3C
standard
OWL is used to
define an Ontology
for Services called
OWL-S
The eventual impact
of RDF and
Semantic Web
technologies on
industries is still not
clear.
Extensible
Messaging and
Presence
Protocol
(XMPP)
A protocol for
instant messaging
and presence that
was originally
developed to
support Jabber
instant messaging
product
Internet
Engineering Task
Force (IETF)
Standard
Six open source
implementation
available.
Interfaces have been
created between
SOAP and XMPP
Recommended in
NCOIC IM PFC

14. Table 2 Summary of standards information
12. References
[1] Document Object Model (DOM)
http://www.w3.org/DOM/
[2] Simple API for XML (StAX))
http://www.saxproject.org/
[3] Streaming API for XML (SAX))
http://stax.codehaus.org/
[4] XML Schema
http://www.w3.org/XML/Schema
[5] RELAX NG
http://relaxng.org/
[6] XML Schema vs Relax NG
http://www.webreference.com/xml/column59/
[7]Data Binding
http://www.rpbourret.com/xml/XMLDataBinding.htm
[8] XSLT
OpenAjax Hub
(Ajax was
initially
Asynchronous
JavaScript and
XML )
OpenAjax Hub
enables Ajax
toolkits to
interoperate.
Features include a
library manager,
publish/subscribe
event hub, and
load/unload event
notification
Twelve toolkits
demonstrated
interoperability at
2007 Interopfest
Reference
implementation at
SourceForge
OpenAjax Registry
under development
Use standards
supported by the
OpenAjax Alliance
which is supported
by all major
software vendors
RSS RSS is a family of
standards for Web
feeds of published
data to RSS reader
software on
subscribing clients
The RSS 1.*
family is
supported by a
RSS-DEV
Working Group
The RSS 2.*
family is
supported by an
RSS Advisory
Board
RSS content is
specified using XML
RSS Readers can be
using Ajax
The RSS 2.* family
has more support
and is the preferred
choice for
podcasting
Atom Atom is a newer
Web feed and
publishing
standard
Atom is a an IETF
standard
Atom uses multiple
XML standards such
as XML schema and
namespaces
Atom Readers can
be built using Ajax
Atom has many
enhanced features
over RSS and is
supported by a
major standards
group.

15. http://www.w3.org/TR/xslt
[9] Java API for XML Binding [JAXB]
http://java.sun.com/developer/technicalArticles/WebServices/jaxb/
[10] Resource Description Framework (RDF)
http://www.w3.org/RDF/
[11] Web Ontology Language (OWL)
http://www.w3.org/TR/owl-ref/
[12] Microformats
http://en.wikipedia.org/wiki/Microformats
[13]Unstructured Information Management Architecture (UIMA)
http://www.oasis-open.org/committees/uima/charter.php
[14] ACORD
http://www.acord.org/
[15] HL-7
http://www.hl7.org/
[16] FIX
http://www.fixprotocol.org/
[17] C2IEDM
http://www.e-mapsys.com/C2IEDM-MIP_Overview_20Nov2003.pdf
[18] JC3IEDM
http://en.wikipedia.org/wiki/JC3IEDM
[19] MIP Programme
http://www.mip-site.org/
[20] EDI
http://en.wikipedia.org/wiki/Electronic_Data_Interchange
[21] VMF
http://www.lm-isgs.co.uk/defence/datalinks/variable_message_format.htm
[22] JC3IEDM and Coalition Battle Management Language (C-BML)
http://www.movesinstitute.org/~blais/Documents/05F-SIW-041.pdf
[23] XBRL
http://www.xbrl.org/
[24] XBML
http://netlab.gmu.edu/xmsf/pubs/XBML-SCS.pdf
[25] JMS
http://java.sun.com/products/jms/
[26] DDS
http://www.omg.org/docs/formal/04-12-02.pdf
[27] DDS Interoperability protocol
http://www.omg.org/docs/ptc/06-08-02.pdf

16. [28]MIP Message Exchange
http://www.mip-site.org/011_Public_Home_Concept.htm#PA-Home-Concept-02-ExchMech0
[29] Efficient XML
http://www.w3.org/XML/EXI/
[30] XMPP
http://en.wikipedia.org/wiki/Extensible_Messaging_and_Presence_Protocol
[31] SIP
http://en.wikipedia.org/wiki/Session_Initiation_Protocol
[32] SIMPLE
http://www.ietf.org/html.charters/simple-charter.html
[33] XMPP, SIP, and RTP in the Real time Internet
http://www.jabber.com/media/Jabber_Inc_SIP_RTP_XMPP_White_Paper.pdf
[34] SOAP
http://en.wikipedia.org/wiki/SOAP
[35] REST
http://en.wikipedia.org/wiki/Representational_State_Transfer
[36] Emerging Standards for SOA Seminar
http://www.omg.org/news/meetings/tc/special-events-dc/Emerging_Standards_forSOA.htm
[37] Combining REST and SOAP Web Services
http://colab.cim3.net/file/work/SOACoP/2007_05_0102/KLaskey05012007.ppt
[38] Web Application Description Language (WADL)
https://wadl.dev.java.net/wadl20061109.pdf
[39] Enterprise Service Bus
http://www.capeclear.com/technology/messaging.shtml
[40] SDO
http://www.osoa.org/display/Main/Service+Data+Objects+Home
[41] DAS
http://incubator.apache.org/tuscany/das_index.html
[42] BPE L
http://en.wikipedia.org/wiki/BPEL
[43] Ajax
http://en.wikipedia.org/wiki/Ajax_(programming)
[44] OpenAjax Alliance
http://www.openajax.org/
[45] RSS
http://en.wikipedia.org/wiki/RSS_(file_format)
[46] Atom
http://en.wikipedia.org/wiki/Atom_%28standard%29
[47] Mashups
http://blogs.zdnet.com/Hinchcliffe/?p=4