reminder TC meeting

[Jacques Durand <JDurand@us.fujitsu.com>]

Title: reminder TC meeting

(Host: Fujitsu
Time: 11amPT
Toll only :  1-512-225-3050
Participant code: 375491)

Agenda:

1. Review Monica comments (see below) on requirements for ebBP deployment template draft. How far are we to conclude. Also about Universal Business Processes.

2. Follow-up on the test case script mark-up, discussion on requirements especially ebBP related.
3. Update on the Test Assertions guideline.

Jacques

---------------------------------------

BT Pattern:
- matrices
- Pattern used legally intentional or not
- business signals used given type of bt pattern used document security selections
isGuaranteedDeliveryRequired quality - non-repudiation of receipt and content/identity
do I use a concrete pattern with the minimum set of requirements defined
- yes or no? If no, what do
I need to change? If I change, use Data Exchange.
Do I need to add semantic information (ontology class) to the process definition?
If so, this is outside of the specification but see open source tool?
Conventions are used in naming.

other:
- isPositiveResponse (not in matrices but important to business success)
- time to perform - time of specification, external reference time to perform - where
can value be acquired from external document specification (impacts logical business
document used and how) 
a. externalDocDefRef: Additional processing details related
to document envelope and specification  (for example use of UBL v1.0 Invoice vs.
UBL SBS v1.0 invoice) 
b. DocumentSpecificationType also provide processing hints to
the implementer  partner should specify whether or not this may raise decisions to a
human involved in the process are standard business signals used, if not specify
location of the user-defined signals.
- legibility check prior to receipt ack (not possible in current ebMS) is reliable
messaging used? (see spec as if so some other assumptions apply - must be used to
ensure state alignment, used of NOF) is concurrency allowed Check well-formedness
rules in specification regarding operational development of process definition and
implementers hints and constraints.

decisions:

- bound what values can be overridden in the cpp/a - it is now limited in the BT
characteristics only to the TimeToPerform if available, it must be used on a
Business Collaboration (because of the limitations of CPP/A and messaging to
handle a complex interaction, i.e. more than a BTA).

- can you delegate to underlying messaging, i.e. the monitoring is of the transport
messages rather than the process transitions of which they may be associated.

composability:

- if modular process definitions are used, what other processes may be included with it?
are the packages contained in design (i.e. semantic requirement in the specification)?
only packages can be xincluded
- what bus collaborations are composed of the modular process definitions (i.e.
purchase order, delivery status and invoice or purchase order and response only).

- composition could be quite complex so this is an incentive for the parties to
define how modular or nested they wish the collaborations to be. If the latter,
that requires thinking about the transitions defined and allowed for the
transactions available.

semantic variables (impacts logical business document used and how)

monitoring:

- what do I wish to monitor
- BT (business messages) used as specified signals used as specified Signals and
processing inferred (legibility, signals - AA necessitates successful processing
of business rules around the business document) transitions checking condition
expressions external document specification (humans may be involved) timing
(including acquisition of an external time to perform) document security used
 as specified quality used as specified

- monitoring if delegating to transport messaging how to circumvent sending of RA
if legibility required how to control or direct timing expectations how does
transport messaging send AA only after business processing validation?
what if hybrid environment of web services and other transports are used?
ebBP would allow you to specify both where one could be an abstract name for
a web services operation that is concretely referenced in a CPP/A.
how to map mep to bt patterns (and BTA)