01.26.2007 F2F Agenda

Agenda for Higgins face-to-face meeting in Provo, Utah, January (23), 24-26, 2007.

Location Novell's office. 1800 South Novell Place, Provo, UT 84606, (801) 861-7000

The event will start Wednesday January 24th at 1:00 and end Friday, January 26th at mid day.

Hotel Several of us are staying at the Conference Center in Provo map.

There are also a few hotels within walking distance (may have to deal with snow though) The markers are off. From left to right,

• The La Quinta is across the street (west) and has a visible swimming pool.
• The Fairfield has a blue roof
• The Hampton is next to (east) of the Fairfield
• The Sleep Inn is next to (northeast) of the Hampton

Weather Dress warm. It may be cold.

Pre-meetings (build issues) Jan 23-24

• Working build clean-up meetings.
  • Tuesday, January 23rd 1:00 pm - 6:00 pm Building H 5th floor
  • Wednesday, January 24th 9:00 am - 12:00 pm Building H 1st floor
  • Novell team will escort from lobby. If late call 801 380 8760

Expected Attendees

• Dale Olds
• Jim Sermersheim
• Mary Ruddy
• Mike McIntosh
• Paul Trevithick
• Tom Doman
• Tony Nadalin
• Duane Buss
• Daniel Sanders
• Nataraj Nagaratnam
• George Stanchev

Preliminary agenda for build issues meeting

• Define user experiences (use cases). Something like:
  • Getting code from CVS:
    • Using Eclipse
    • Using other CVS tools
  • Build steps
    • Build prerequisites
      • Gathering dependencies
      • Setting up environment (incl. env variables)
    • Building in Eclipse
      • Using Eclipse build
      • Using ant inside eclipse
    • Building from the console

• Standards for consistent developer builds
  • Do we need to support all the use cases above?
  • Instructions for getting code
  • Instructions and/or scripts for build prerequisites
  • Instructions on building
  • Is the output the same as the nightly build? (Jar file naming, Jar file versioning, Javadoc copyright)

• Project Packaging and Terminology
  • Packages versus Projects
    • Should each different package be it's own project, or should a project contain multiple related package?
      • i.e. Why are there multiple IdAS projects?

• Dependencies
  • Delivery/Distribution (how do people get them?)
  • Placement for builds
    • Do we require additional Eclipse plugins?

• Review Nightly build needs
  • Jar file naming
  • Jar file versioning
  • Review Javadoc copyright

• Requirements for package-managed builds
  • RPMs
  • JPackage

Main Meeting Jan 24-26

Expected Attendees

1. Abhi Shelat (IBM)
2. Dale Olds (Novell)
3. Daniel Sanders (Novell)
4. Duane Buss (Novell)
5. Jim Sermersheim (Novell)
6. Igor Tsinman (Parity)
7. Mary Ruddy (SocialPhysics, Parity)
8. Maxim Kopeyka (Parity)
9. Mike McIntosh (IBM)
10. Nataraj Nagaratnam (IBM)
11. Paul Trevithick (SocialPhysics, Parity)
12. Pete Rowley (Red Hat)
13. Tom Doman (Novell)
14. Tony Nadalin (IBM)
15. <add your name>

Development Processes & Stds

• Component Owner responsibilities [Paul]
  • maintain automatic (nightly) builds
  • maintain all columns in your "row" here: Components (javadoc, psfs, etc)
  • maintain "to-do" list for each component
• Moving all Higgins interfaces/APIs back to JVM 1.4 [Tony]

Milestone 0.7 Progress/Review [Paul]

• Step through each component and get an update (even if the update is "stuck in IPzilla process")

HBX: I-Card/Identity Selector [Abhi]

• Additional local folks may join us for this segment
• Demo ????
• Discussion of threat model to running the card selector in the browser itself

ISS Client UI

• Bootstrapping option [Dale]
• Eclipse RCP vs. ??
• Platform/tool/runtime issues [Paul]
• Potential for collaboration with Ian Brown (developer of the Safari selector) [Paul]

OpenID Context Provider [Dale, Tom, Jim]

• Implementation options (alternative use cases we could support)
• Call in segment with Dave Recordon on West Coast?

SAML Context Provider [Dale, Tom, Jim]

• Interest in creating this?
• Help from OpenSSO project
• Resources?

IdAS [Jim: 4-5 hours]

• org.eclipse.higgins.idas.model refactoring (2 hours)
  • We're adding the APIs in 171295. Is there anything else we need them for (getMetadataModel)?
  • Should the interfaces in the model package be used to produce instances of context data (digital subjects, attributes, filters, modification lists, etc.)?
  • Adding matching rules to the model
    • This overlaps some of the Data Model discussions below
    • Attributes should list the comparators they support 171312
    • Comparators should specify the assertion value required

• IFilter refactoring (1 hour)
  • String representations of filters 171328
  • How to do substring and other matching rules which require non-standard attribute assertions 171331 and msg01394
  • Do comparators need to be represented as an interface?

• Update operation refactoring 167978 (1 hour)
  • API atomicity for joining providers 171296
  • Adding a new Digital Subject to the backing store
  • Creating new attributes and values for new and existing Digital Subject
  • Modifying existing Digital Subject
    • Adding, replacing, and removing attributes 171297

• Topics likely to be deferred (1 hour)
  • Import/Export issues 171298 and 171301
  • Relationship Issues 171304

Registry Issues [Jim, Tom: 2 hours]

• Status summary [IdAS_Registry_and_Configuration], 171291, and 164048

• General Registry thoughs msg01249

• IdAS and CP needs
  • Configuration
  • "Usable" Context Ref URI

• Other Registry needs?
  • Stackable CP's 171294

Data Model & Related Topics [Paul]

• Valery's Display Data Proposal and discussion
  • Motivation for "in-context" metadata vs. "external" metadata
  • Semantics of display metadata
• Relaxing the OWL-DL constraint
  • Allow us to define our own kinds of Classes (e.g. for LDAP AUX classes, etc.)
  • Allow us to better "type" attribute data values (e.g. phone number masks (xxx)-xxx-xxxx) using XML Schema (I think)
• "Well known Contexts"
  • Paul's unusual and possibly misguided ideas about how some kinds of identifiers (e.g. email, telephone numbers) should be modeled
• IdentitySchemas.org update

Higgins' and other Communities [Mary 60 min]

• A discussion whose proposed outcome is a wiki page characterizing the Higgins project's relationships with other communities.

Related Communities

Privacy/Data Policies [Duane,??]

• Develop the Higgins' roadmap in this area
• RP Security Policy
  • Is the goal Higgins policy = [MSFT CardSpace policy + Idemix]? More than this?
  • Relationship to other efforts (e.g. Liberty/CARML)?
• User's data privacy policy --not sure what the term for this is
  • e.g. Mary Rundle's ideas (from Berkman Center) based on international data protection law
• Identity Provider policy --not sure what the term for this is
  • Relationship to Liberty/AAPML

See Also

• Higgins Home
• Higgins Wiki Home