|
Existing EDA/CEP Standards |
|
|
|
|
|
v2.1 – March 1, 2007 |
|
|
|
|
|
|
|
|
|
|
|
Standards |
Standard
Name |
Description |
Status |
URL |
|
JCP |
JSR 190: Event Tracking API for J2ME |
This specification will define an optional code
package that will standardize the tracking of application events on a mobile
device and the submission of these event records to an event-tracking server
via a standard protocol. |
Final Draft |
|
|
OASIS |
Common Alerting Protocol |
The Common Alerting Protocol (CAP), a data
interchange standard for alerting and event notification applications,
currently in version 1.1. CAP functions both as a standalone protocol and as
a payload for EDXL messages. |
Approved Standard |
http://www.oasis-open.org/committees/download.php/14759/emergency-CAPv1.1.pdf |
|
OASIS |
WS-Base |
WS-Notification is a family of related
specifications that define a standard Web services approach to notification
using a topic-based publish/subscribe pattern. |
Approved Standard |
http://docs.oasis-open.org/wsn/wsn-ws_base_notification-1.3-spec-os.pdf |
|
OASIS |
WS-Brokered |
WS-Notification is a family of related specifications
that define a standard Web services approach to notification using a
topic-based publish/subscribe pattern. |
Approved Standard |
http://docs.oasis-open.org/wsn/wsn-ws_brokered_notification-1.3-spec-os.pdf |
|
OASIS |
WSDM Management Of Web Services (MOWS) |
Defining a Web services architecture to manage
distributed resources |
Approved Standard |
http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wsdm#overview |
|
OASIS |
WSDM Management Using Web Services (MUWS) |
Defining a Web services architecture to manage distributed
resources |
Approved Standard |
http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wsdm#overview |
|
OASIS |
WS-Topics |
WS-Notification is a family of related
specifications that define a standard Web services approach to notification
using a topic-based publish/subscribe pattern. |
Approved Standard |
http://docs.oasis-open.org/wsn/wsn-ws_topics-1.3-spec-os.pdf |
|
OMG |
BPMN |
BPMN provides a Business Process Diagram (BPD),
which is a Diagram designed for use by the people who design and manage
business processes. BPMN also provides a formal mapping to an execution
language of BPM Systems (BPEL4WS) |
Adopted Standard |
|
|
OMG |
Enterprise Collaboration Architecture (ECA) |
The Events profile, which describes a set of UML
extensions that may be used on their own, or in combination with the other
EDOC elements, to model event driven systems. |
Adopted Standard |
|
|
OMG |
Event Service Specification |
Defines two roles for objects: the supplier role
and the consumer role. produce event data and consumers process event data.
Event data are communicated between suppliers and consumers by issuing
standard CORBA requests |
Adopted Standard |
http://www.omg.org/technology/documents/formal/event_service.htm |
|
OMG |
Event-driven architecture for SOA |
Developing modeling standards for the iteration of
Event Driven Architectures and Service Oriented Architectures |
RFI |
|
|
OMG |
Management of Event Domains |
Specifies an architecture and interfaces for
managing event domains |
Adopted Standard |
http://www.omg.org/technology/documents/formal/mgmt_event_domains.htm |
|
OMG |
Notification / JMS Interworking |
The interworking involves several aspects such as:
event message mapping; QoS mapping; event and message filtering; automatic
federation between Notification Service channel concept and topic/queue
concepts; and transaction support. |
Adopted Standard |
http://www.omg.org/technology/documents/formal/notification_jms.htm |
|
OMG |
Notification Service |
An extension to the existing OMG Event Service,
adding to it: transmitting events in the form of a data structure; event
subscription; discovery; QoS; and an optional event type repository. |
Adopted Standard |
http://www.omg.org/technology/documents/formal/notification_service.htm |
|
OMG |
Production Rules Representation (PRR) |
Production Rules Representation - Specification for
Event - Condition - Action rule sets |
RFP |
|
|
OMG |
SysML |
The OMG systems Modeling Language (OMG SysMLª) is a
general-purpose graphical modeling language for specifying, analyzing, designing,
and verifying complex systems that may include hardware, software,
information, personnel, procedures, and facilities |
Adopted Standard |
|
|
OMG |
UML Profile and Metamodel for Services (UPMS) |
UML profile for modeling services |
RFP |
|
|
OMG |
Unified Modeling Language (UML) |
A specification defining a graphical language for
visualizing, specifying, constructing, and documenting the artifacts of
distributed object systems. |
Adopted Standard |
|
|
W3C |
Document Object Model Level 2 Events Specification |
Design of a generic event system which
allows registration of event handlers, describes event flow through a tree structure,
and provides basic contextual information for each event |
Recommended |
|
|
W3C |
Document Object Model Level 3 Events Specification |
Design of a generic event system which allows
registration of event handlers, describes event flow through a tree
structure, and provides basic contextual information for each event |
Draft |
|
|
W3C |
Ubiquitous Web Applications Activity Proposal |
The Ubiquitous Web Applications Working Group seeks
to simplify the creation of distributed Web applications involving a wide
diversity of devices. |
Chartered Group |
|
|
W3C |
WS-Eventing |
This specification defines a protocol for one Web
service to register interest with another Web service (called an "event
source") in receiving messages about events. |
Draft |
|
|
W3C |
Xforms |
XForms is an XML application that
represents the next generation of forms for the Web. |
Recommended |
|
|
W3C |
XHTML Events Module |
This specification defines the XHTML Event Module,
a module that provides XML languages with the ability to represent in syntax
the semantics of the Document Object Model (DOM) Level 2 event interfaces |
Draft |
|
|
W3C |
XML Events 2 |
An Events Syntax for XML |
Draft |
|
|
W3C |
XML State Chart XML (SCXML) |
State Machine Notation for Control Abstraction |
Draft |
|
|
|
|
Please send any corrections or
additions to rcovington@rhysome.com |
|
|
Last updated on: 11/09/2007