[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Meeting Minutes for FFM TC call (Aug 22)
1. Roll Call & Agenda Review
Roll call results are available in the following document.
http://www.oasis-open.org/committees/download.php/43288/FFMTC%20roster_roll_call.xlsx
Quorum is present.
Agenda was agreed unanimously.
2. Volunteer for minutes
- Aug 22: Johannes
- Sept 5: Juha
- Sept 19: Israel
3. Approval of minutes from last meetings
FFM TC, Aug 16, Meeting Minutes
http://www.oasis-open.org/committees/download.php/43232/FFM-TC-meeting-minutes-2011-08-16.txt
Meeting Minutes were approved.
4. Action Items
Closed Action Items:
Israel: Provide a definition and semantics for each of the status codes.
Johannes: Provide refined text for sections 6.2.2.3 and 6.2.4.2.
New Action Items on Aug 22:
Jiri and Israel: Propose solutions to Section 6 issues (see comments under 6 FFMII Specification).
Due by next FFM TC (Sep 5)
Johannes: Check domain model material against the new Work Request status model and propose required changes.
Due by next FFM TC (Sep 5)
Missing foundation material to be produced and proposed:
5.1.3 Schedule: Israel
5.3 Work Request Status Change Notification: Thinh
5.4 Field-Initiated Requests: Jiri
Due by next FFM TC (Sep 5)
Jiri and Johannes:
Initial draft material for Core Data Model
Due by next FFM TC (Sep 5)
5. FFMII Requirements
5a) FFMII-BusinessUseCasesFeaturesREQ-v1.0-wd01-07252011 following discussionof 16-Aug-11.docx (Israel)
Document had been updated to reflect discussions of the last meeting. Document was noted.
5b) Status code explanations - IB 17-Aug-11.docx (Israel)
Document was noted.
5c) Proposed refinements on features doc regarding Activity state model and status reporting (Johannes)
http://lists.oasis-open.org/archives/ffm/201108/msg00016.html
Johannes presented the proposal.
The proposed changes will be merged into the draft requirements document.
5d) FFMII-BusinessUseCasesFeaturesREQ-v1.0-wd01-08182011.docx (Thinh)
Document was noted.
6. FFMII Specification
6a) FFMII Foundation Specification: NSN, Rossum, Aalto University
http://www.oasis-open.org/committees/download.php/42939/FFMIISpecification-Foundation20110720-D.docx
Section 6 was presented by Jiri. The following comments were noted.
For generic functional layers, such as transport and security layers, the intent is to specify which existing standards and technology to use (not to devise new mechanisms).
First figure in 6.1 Overview (and later detailed sections):
"Message Queue" is a bit misleading term because the intent is not to specify a particular message queueing technology but instead to specify general high level policies on handling particular types of errors. It was proposed that "Message Queue" could be removed altogether and resending policies to be specified as part of "Error Handling".
Second figure in 6.1 Overview:
Work Requests are related to Change Notification Management only indirectly via referrals (thus, the dashed box). Work Requests are also related to Field Request Management that covers the use case of querying for unassigned Work Requests available for an Assignee.
7: Next FFM TC meeting planning
Next conference calls: Sept 5, Sept 19
8. Any other business
No other business.[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]