...
- 6 out 9 voting members on the call, mainly due to a call conflict arising from the OASIS/RSA interop prep call.
- Quorum not reached.
2. Approve December and January Minutes
- No Quorum so Minutes could not be approved
- Agreed to circulate previous minutes Minutes on list for vote. [If Quorum still not reached 'Minutes' will be relabelled 'Notes' to indicate their status]
2. Topic 2
The following officers were agreed upon by unanimous consensus:
Summary:
- List Items
- Bold
- Italicized
3. Topic 3
Summary:
- List Items
- Bold
- Italicized
4. Topic 4
...
3. Review status of Action Items Summary
Summary:
- Colin's action to send December (and January) Minutes to list for electronic vote - closed
- Joni's action to introduce JIRA is proceeding. Will liaise with Scott on config - open
- Colin's action on finding a room for the BoF at RSA (is Marriott 2nd floor) - closed
- Colin's action to flesh out Portland eGov agenda - closed
4. Review of SPOCS (Simple Procedures Online for Cross - border Services) EU Project
- Fulup provided a comprehensive review of SPOC activities and challenges and opportunities as he saw them
- SPOCS at a higher level than STORK project that denmark is associated with. [Mention made of concern that STORK's LoAs are different from NIST/KI IAF
- Significant MS influence angling towards a product solution rather than a specification
- Significant focus on Adobe's dynamic PDF (XML)
- Audience not highly technical, not aware of Liberty/KI protocols and trying to invent their own
- Difficult to communicate with given the static nature of the website
- Fulup suggests a liaison: 2 from them to us, and 1 of us to them. Agreed. Action 2010-02-01-1: Colin to provide Liaison process to Fulup to progress
- FEDICT project in Belgium doing SAML 2. There could be mutual benefits in them joining this KI eGov WG
5. Consideration of Liaison with OASIS eGov
- Bob spoke in support of this, to use the OASIS eGov Member Section as a conduit to feed back comments on OASIS specs in general. A specific example was the lack of <language> in SAML, so that dual or multi language secure messaging had to be done in HTTP with some attendant problems
- It was agreed to progress this liaison. Action 2010-02-01-2: Colin to progress with the L/C.
Next Meeting
...