[ebxml-iic] RE: F-2-F agenda, Aug 22-23, San Jose

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

Title: minutes, and F-2-F agenda, Aug 22-23, San Jose

All:

 

For those who join the face-to-face meeting, an update:

 

1. See attached a more detailed proposed agenda for San Jose f-2-f  this Thu-Fri.

 

2. I know this is late, but is there any need for Hotel recommendation?

(I realize that only those who asked so far got some directions)

Please note that Fujitsu Software is very close to the SJ airport (~10mn)

so any hotel close to airport (which is itself not far from downtown) is OK.

 

3. For those not attending but calling-in (for all the sessions - we'll try to

be more specific about the hourly schedule of discussions)

Host: Fujitsu

Toll free number: 1-877-801-2058

International Number:1-712-257-6652

Participant passcode: 309951

 

4. Lunch info: could you answer this one preferably quickly (by tomorrow?)

Is there any particular restriction / wishes?

So far, options for in-house lunch:

- Sandwiches

- Bento box (Japanese)

 

See you here!

 

Jacques

 

 

Agenda for IIC f-2-f, Thursday-Friday Aug 22-23, San Jose CA.:

Location:
---------

Fujitsu Software Corporation
3055, Orchard Drive, San Jose, CA 95134-2022
Administrative contact: Satina Chiu (408)456-7950
Jacques Durand: (408) 456-7917, cell: (408) 807-5979

Thursday:
---------

Morning: (9am - 12)

1. Review of Test Framework document (ebXMLTestFramework.doc V0.4), in particular:
- Test Service: review and finalize the definition of Actions (Section 3.3).
- Architecture configurations assumed for MS COnformance, MS Interoperability.
- Overall positioning of the test Framework (just an automation option? 
indispensable for describing test semantics?)

2. Common issues for MS conformance and interoperability Test Suites:
- user perspective of testing procedures: who and how, overall usage of test suites. 
- review of general Test Case protocol (e.g. initial config & CPA aspects) 
- common approach for defining sequences of test steps, for specifying 
the verification condition 
- finalize format for message material:  CPA samples, message templates, parameters.
 
Afternoon: (1:30pm-3:30pm and 4pm-6pm)

3. Continuation of (2) if needed.

4a. MS conformance Test Suite:
- Test Cases definitions for the current set of Test Requirements ("Master list"):
(can we identify some "test case patterns" that could be reused across Test Cases?)
- XML mark-up?
- Conformance profiles/levels.

4b. MS interoperability Test Suite:
- finalize a basic set of interoperability profile(s)
- Test Cases definitions for our profile(s)
- operational issues (initialization, sharing CPA data)

4c. MS Deployment Template (contingent to sub-team presence):
- the template elements (MSH options, header content, CPA references).
- the EAN instance.

(NOTE: 4a, 4b and 4c could be done in parallel)


Friday:
-------

Morning: (9am - 12)

5. Joint review of common issues from previous day
(both conformance and interop, test framework)

6a. MS conformance Test Suite: (continuation)
- Test Cases for the current set of Test Requirements.

6b. MS interoperability Test Suite: (continuation)
- set of Test Cases for interoperability profile(s)

6c. MS Deployment Template (contingent to sub-team presence):
- the template elements (MSH options, header content, CPA references).
- the EAN instance.

(NOTE: 6a 6b 6c could be done in parallel)


Afternoon: (1:30pm-3:30pm and 4pm-5pm)

7. Continuation of (6)

8. IIC work in the context of other initiatives, users perspective:
- 3rd party specific interop initiatives (DGI, ECOM, ...)
and role of IIC here, how that impacts our test definitions.