Architecture Working Group
Group Charter
| Title of Working Group | FpML Architecture Working Group | ||||||||||||||||
|
|
|||||||||||||||||
| Chair of Working Group | Andrew Jacobs (HandCoded Ltd.) | ||||||||||||||||
|
|
|||||||||||||||||
|
Mission:
To develop the FpML architecture specification. Where possible, appropriate standards developed by W3C and other such standards bodies should be reused |
|||||||||||||||||
|
|
|||||||||||||||||
|
Scope:
The Technical Architecture work group will examine four various issues including:
|
|||||||||||||||||
|
|
|||||||||||||||||
|
|||||||||||||||||
|
|
|||||||||||||||||
|
Meeting Schedule
The whole group should meet weekly by telephone (up to 2 hours). The architecture working group discussion list will be used to manage group communication. |
|||||||||||||||||
|
|
|||||||||||||||||
|
Rules of Operation
The working group will adopt the FpML Rules of Operation (Working Groups section). These outline best-practices for meetings, managing member participation, reaching group consensus and voting. |
|||||||||||||||||
|
|
|||||||||||||||||
|
Estimated time commitment from Participants:
Members should be prepared to commit a minimum of 1 day per week, and approximately 2 days per week on average. Full members must have the agreement and support of their management before signing up to the Working Group It is expected that participants will be signing up for action items and proposals, and will generally be participating in discussions during the week. Experience has shown that occasional face-to-face meetings can expedite the process so members should be aware that some travel and full-day meetings may be required |
|||||||||||||||||
|
|
|||||||||||||||||


