Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Oct 27-29 Boston F2F Agenda
Revision as of 11:12, 28 October 2008 by Paul.socialphysics.org (Talk | contribs) (→3:00 ALF SSO Code [Brian Carroll])
Higgins face-to-face meeting in Waltham, Massachusetts, October 27-29, 2008.
Contents
- 1 Logistics
- 2 Expected Attendees
- 3 Monday
- 4 Tuesday
- 4.1 9:00-noon Review of the Context Data Model [Paul]
- 4.2 noon-12:15 Higgins Data Model [Hank]
- 4.3 noon-1pm Lunch
- 4.4 1:30 UN/PW Cards [Brian]
- 4.5 2:00 Higgins AIR Selector Architecture [Jeesmon]
- 4.6 Access Control in IdAS [Paul]
- 4.7 Models as Entities [Jim]
- 4.8 OpenID Support in Higgins [Paul, John, others]
- 4.9 Architecture Harmonization [All]
- 4.10 Higgins Website Enhancements
- 4.11 Higgins Whitepaper
- 4.12 Higgins Process/Infrastructure Enhancements
- 4.13 DigitalMe [Jim/Andy]
- 4.14 4:00 R-Card Design Review [Paul, Markus, Drummond]
- 5 Wednesday
Logistics
- Location: The offices of Wilmer Hale, 1100 Winter Street in Waltham, Meeting Room(s): St. Clair - 0401
- Enter through the center door. The building is on a hill so you enter above ground level. Elevators are to your left.
- GoogleMaps directions [1]
- Reservations were made under Parity name
- Call Mary at 617-290-8591 if you have problems
- Wilmer Hale reception number is 781-966-2000
- Time: The event will start Monday at 9:00 AM and end Wednesday at noon. Note that Wednesday from 9:00 to 10:30 we will be meeting in a different room.
- Action Items are indicated by the presence of "(AI)" on a line and the owner of the action item is in bold.
Expected Attendees
- Jim Sermersheim - Novell
- Paul Trevithick - Parity
- Drummond Reed - Cordance/Parity
- Mary Ruddy - Meristic
- Hank Mauldin - Cisco
- Markus Sabedello - Parity
- John Bradley - Parity
- Tom Carroll - Parity
- Brian Walker - Parity
Attending by phone
Dial in number: (218) 339-4300
Participant Passcode: 1038511#
Attending on IRC
TBD
Monday
Note that once we have finalized the agenda, we will move items around to appropriate time slots. Please add your proposed agenda items
We will track at least the agenda on the #Higgins IRC channel. If you wish to call in for an agenda item, please let us know on the #higgins IRC channel
8:30- 9:30 Continental breakfast
- Breakfast pastries arrive at 8:30. Assortment of coffees and teas available all day.
9:00-9:30 Welcome, Introductions, Agenda
- Introductions
- Eclipse ground rules
- Agenda bashing
- Dinner planning
9:30-9:45 iPhone Selector [Markus]
- Proof of concept prototype demonstration of iPhone Selector
9:45-12:00 Higgins Positioning and Home Page Positioning [Mary]
Lunch noon-1pm
- Cafeteria downstairs
1pm IdAS REST [Jim]
- Where we are right now:
- Bandit Project has one implementation called OTIS [Jim can demo]
- Message body specs can be found at:
- http://code.bandit-project.org/trac/wiki/OTIS/Doc/Protocol
- example message bodies under cURL examples of each of http://code.bandit-project.org/trac/wiki/OTIS/Doc#OTISFunctionality
- If you want to try the rest.xml provider out, it's easiest to start here http://code.bandit-project.org/trac/wiki/OTIS/Doc/DeployingAnOTISServer#Quickstart Follow either the Standalone Glassfish, or Simple Pre-configured deployment instructions
- We can expose any IdAS context as XML
- The OTIS Server can also dynamically open different server-side-configured IdAS contexts and expose them
- See the 'ContextID' element of the message at http://code.bandit-project.org/trac/wiki/OTIS/Doc/Protocol/authenticatedSessionPOSTRequest#RequestMessageFormat
- A slim client with only the cp.rest.xml can therefore access any server-configured IdAS context via OTIS
- Message body specs can be found at:
- Markus can show/explain the IdAS XDI Engine & CP
- Message body specs can be found at:
- Demonstration and discussion of the XDI Engine
- We can expose any IdAS context as XDI
- The XDI Engine can also dynamically open new IdAS contexts and expose them
- A slim client with only the XDI CP can therefore access any IdAS context via the XDI Engine
- Bandit Project has one implementation called OTIS [Jim can demo]
- Where we want to go:
- Common Client and Server components
- Should it use ROA ot SOA? If ReST, how Fielding-friendly should we be?
- Alternatives: SOAP, JMS, others?
- Investigate using a JSR311 impl
- Standardization on one or more set of nouns and content types
- Assuming we want to standardize content, which is the most appropriate body? OASIS?
- Flexibility is good!
- Bandit quickly dumbed down XML to accommodate Pipes demo
- Would be nice to be able to support other ad-hoc standards like OpenSocial ReSTful http://www.opensocial.org/Technical-Resources/opensocial-spec-v081/restful-protocol
- Oasis XDI TC is standardizing what Markus has been using
- The XDI messages as they currently stand would be a very hard sell as being "ReSTful" as there is one noun and all actions are carried in the message.
- Diagram at end of mtg
Tuesday
9:00-noon Review of the Context Data Model [Paul]
- Working session going through the PPT and reviewing and updating it
- We have the ability to have attributes about a single entity-attribute-value
- We need to represent attributes about the set of all values of an attribute
- need to add Agent and Person, Org, Group to PPT
- add device examples to PPT
noon-12:15 Higgins Data Model [Hank]
- Today we have Person, Organization and Group as subclasses of Agent (as subclass of Entity)
- Proposal: we add "Device" as a new subclass of Agent
noon-1pm Lunch
1:30 UN/PW Cards [Brian]
- Adding support for login to existing sites using un/pw form filling
2:00 Higgins AIR Selector Architecture [Jeesmon]
- Review current architecture
- Review proposed changes
- LICS: Local I-Card Service
- Local IdAS
Access Control in IdAS [Paul]
- Working session where we go through use cases together
- Access Control in IdAS, Access Control Use Cases
Models as Entities [Jim]
- review IEntity EntityId decisions
- other discussion
OpenID Support in Higgins [Paul, John, others]
- Review our goals
Architecture Harmonization [All]
- Need to pull the three "1.1" Selectors (AIR, RCP and GTK/Cocoa) closer together architecturally
- Reuse of browser extensions
- Leveraging Selector Selector (on Windows, OSX, Linux)
- Common STS infrastructure (WS-Trust, SAML2, Kerberos, etc.)
Higgins Website Enhancements
- Home page structure & content [Mary, Paul]
- Downloads page proposal [Brian]
- Other content and functions [Mary]
Higgins Whitepaper
- Objectives, audience & content [Mary]
- Create an outline
Higgins Process/Infrastructure Enhancements
- Automated nightly testing
- Review status of internationalization
- Jim: people ask often: if I get a specific higgins project, how do I know what dependencies I need?
- breaking every jar into its own Eclipse project (relationship to Orbit)
- relationship to http://www.eclipse.org/buckminster/
DigitalMe [Jim/Andy]
- Demo
- Architectural overview
4:00 R-Card Design Review [Paul, Markus, Drummond]
- Review R-card XML data format
- Review UDI spex [Markus]
- Review status of access control issues related to r-cards
- Walk through a few r-card use cases (alice sharing an r-card with Bob)
Wednesday
I-Card next steps [Paul, Mary, etc.]
- FC2 needs [2]
- Information card ID-WSF interoperability
- Information card multi-card use cases
Co-Creating the Higgins Project Plan [Mary and all]
- New Eclipse format
- Alignment with other project/product releases (Eclipse, Higgins Contributors)
- Features
- Maturity (Internationalization, auto testing, etc..)
- Other alignments