tamie message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: Proposed Agenda for TaMIE F2F
- From: "Durand, Jacques R." <JDurand@us.fujitsu.com>
- To: <tamie@lists.oasis-open.org>
- Date: Fri, 14 Mar 2008 13:26:11 -0700
Proposed Agenda for TaMIE F2F Mar 31 - Apr
1:
------------------------------------------------------------------------
Monday 3/31, AM
------------------------------------------------------------------------
1. Kick-off:
- various administration matters.
- Get last minute "wish list items" from
participants.
- adjustments to agenda.
2. B2B and Business Transaction
Requirements:
- Drafting a set of "Canonical" Business
Transactions Use Cases
- review of most common B2B patterns in OAGI, AIAG,
RosettaNet, UMM
- the "areas of conformance": documents, QoS and
timing, MEP,...
(what needs to be monitored / validated / enforced)
3. Requirements for Event modeling:
- various inputs to be modeled as Events.
"Everythng is an event" approach vs.
other Internet resources.
- when event = message: standard XML mappings?
Review of the WS-I "XML container" for MIME / SOAP
messages.
- when events = metadata document.
- Events models in other standards.
- KIEC feedback on events. (identifiers,
typology...)
- Review of the eTSL event model.
------------------------------------------------------------------------
Monday 3/31, PM
------------------------------------------------------------------------
4. Requirements for the Event Board
(EB):
- EB Profiles: large scale repository (data
warehouse model) vs. light structure for
test runs?
- Event Board model (XML database? single XML
"trace"? references to
External resources, e.g. payload docs? metadata
docs?
- event Board operations (search, wait, post, mask,
correlation,...)
5. Review and assessment of some XML-based
dialects:
(functionality / maturity / adoption level /
availability / openess and integration prospects)
- XSLT and XPath
- XQuery
- STX
- XProc
- SML
- EDI-Path
- other?
6. Script Language features
- Control flow constructs: review of OGC
requirements and CTL.
- Integration model with external specialized
processors (XPath, XQuery, EDI-Path...).
(Pre-processing/translation? External procedure
call?)
- Extensibility design: coarse-grained
extensibility (adapters in eTSL)
vs. fine-grained extensibility (embedded external
expressions, e.g. XPath)
- impact on the event board operations (query
delegation to DBMS lge vs. basic access primitives).
------------------------------------------------------------------------
Tuesday 4/01, AM
------------------------------------------------------------------------
7. Beyond B2B: Other Areas of
Application:
- BPM and SOA Monitoring: CECID: OSB and Business
Process Status Tracking.
- SCA: conversational interfaces, policy
enforcement.
- BAM
- Event-Driven Architectures
8. A Closer Look at Process Languages:
- The orchestration aspect (private process) vs
choreography aspect (public process).
- Overview of BPM def lges: BPMN, XPDL, UML, BPEL,
from the monitoring/testing angle.
- YAWL
- review of choreography notations: ebBP, UMM
Transactions, WSDL, WS-Choreography.
9. Continuation
of Day 1 topics as appropriate:
- Extend list of "Canonical" Use
Cases (continuation item
#2)
- Script language
features (continuation item
#6)
------------------------------------------------------------------------
Tuesday 4/01, PM
------------------------------------------------------------------------
10. A "Critical" review of the eTSL Script
execution model
(in the light of previous
requirements).
- the general event-driven model, Triggers and
Monitors.
- the script markup language and its
primitives.
- the Case Execution Space, and "state" management
(variables...)
- the notion of Test Suite (or Monitoring
Suite)
- Event access and management.
- KIEC feedback.
11. A first pass at Deliverables:
- The requirements document:
o objectives
o sketching its content and structure
o work assignments.
- The specification(s), objectives, how to
distribute their features:
eTSM - event-centric Test Scripting and
Model
eMAM- event Model, Access and
Management
- timing and workplan.
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]