...
I suggest we use this model/ requirements listing that we initially evolved in the VPI Special Interest Group. It is already on the wiki, and starts off with a listing of the capabilities that would need to be built on the side of the individual in order to operate in the customer-supplier engagement framework (in Sally's position). As these were put together in mid 2009 we need to sense-check whether these need to be updated. We can discuss them, update them, and start to then use the rest of that sheet/ other columns to get into what existing tech might support the build/ deployment of these capabilities.
...
This is a good starting point, needs to be updated.
http://kantarainitiative.org/confluence/display/infosharing/VPI+Technology+Options+Draft+0.3
...
Joe and Iain have agreed on the requirement for the proposed funding work and communicated that to Brett. The ball is with Brett to respond on whether this approach remains acceptable, and if so then we need to identify resource options that could undertake the work (building out the work currently being driven by volunteer effort).
...
Iain Henderson to follow-up with Brett McDowell
- Joe will create draft of charter and sandbox on wiki, will keep on same mailing list. Agreements Sub-Committee.-
All to provide input to charter and sandbox on the wiki. The group will use the same the same mailing list.
...
The group will use the same bridge.
- Iain: ref. 10 vendor scenarios, after 1/22/10, Iain to schedule a realtime conversation to share the draft review when received from Mark Lizar.
3. New Business
- -
4. Lexicon
5. Action Item Review
...
- The Standard Agreement Subgroup - assume using use the same bridge details for the group. Dervla to double-check if there are any conflicts.
- After 1/22/10, Iain to schedule a realtime conversation regarding 10 vendor scenarios to share the draft review when received from Mark Lizar.
...