Brief notes from last weeks Higgins Developers call:
Attendees: - Elmar Eperiesi-Beck - Corisecio
- John Bradley
- Jeesmon Jacob - Azigo
- Paul Trevithick - Azigo
- Brian Walker - Azigo
- Mary Ruddy - Meristic
- Valery Kokhan - Azigo
- Alexander Yuhimenko - Azigo
1) [Brian] HIGGINS 1.1M7 TRACKING - We have moved the target date to 7-Aug.
- The main reason of the move was to (a) complete development of Cardsynch protocol and local cache and (b) finish deployment of new solutions download page and associated clean up/code check-ins.
- Getting nightly build status integrated into this new solutions download page will take some time beyond M7.
2) [Paul] WEB&WIKI DOCUMENTATION
- Paul reviewed cleaned up version of the web and wiki documentation.
- Updated the “diagram key” [7] to organizing solutions, services, packages, components, projects and sub-components. [7]
- Introduced the concept of Packages and “Higgins Packages” wiki category (if you want a list of them). There is not digital artifact of a package - just a set of components.
- See Selector Overview [2], CardSync Service [3], RPPS package [4]...etc noted below
3) [Paul] PERSONA DATA MODEL 1.1 [6]
- Paul has started work on documenting a new model for run-time user data. It is a concrete application of the Context Data Model 1.1 and layers over it (see diagram below).
- Within the RPPS Package [4] are components that persist data objects on behalf of the user. These include I-Card Registry and others (not counting temporary caches). These include user account data, the users set of cards, and other data. Some components use IdAS 1.1 Package to persist their data while others manage their own local data stores "above" IdAS. The overall data model has never been documented in one place and it didn't have a name. As of now we are calling it the Persona Data Model 1.0 (PDM 1.0).
- PDM 1.0 has evolved over the past few years as we've piled on more and more requirements. At this point, we need to evolve it still further, but before we do so, we'd like to document the new model Persona Data Model 1.1 so that it can be peer reviewed, combed through and made as self-consistent, simple and powerful as possible. The new model will have more generality and be easier to implement than what we have today. This page, when complete, will document Persona Data Model 1.1.
- I’ve repeated the picture on [6] here:
4) [Elmar Eperiesi-Beck (Corisecio) & Jeesmon] HIGGINS SELECTOR SWITCH UPDATES
- Corisecio is working on Invoking mobile phones based applications.
- The desire is to have Corisecio to help with the HSS solution in support of this. We would continue to keep the old solution (http connection) and offer the alternate solution.
- Coresecio ran into some technical issues with current version of HSS checked in Higgins and will summarize those issue in a separate email, such that we can offer him the assistance necessary to correct these in follow up emails/discussion.
- Over the weekend Azigo checked in a newer version was committed in Higgins svn -https://dev.eclipse.org/svnroot/technology/org.eclipse.higgins/trunk/app/org.eclipse.higgins.tcpserver/
Also, there is some quick build guide in \src\build folder. - We also ran into some issues with certificates on Higgins that expired - working on renewing these with Eclipse.
- Mary will also support Coresecio with any code check-in's that need to do to Higgins in the future.
5) [Paul, Brian] AUTOMATED SOLUTION LEVEL BUILDS [8]
- Discuss/review requirements as noted in [8]
- Alexander Y is working on some experimentation, assessment to try different build solution options (Hudson, Buckminster, Maven) to see which solution options would work effectively. Hope to have first round assessment done by the end of next week or early the week after.
6) [John B] Information Card claims - Issue with RP's getting attributes in different name spaces. Currently these cases are not covered in IMI spec.
- Discussed various aspects of how namespaces, attribute name and URI's, and to what level we are supporting SAML.
- John will further iterate on this with others and updates to follow.
Brian Walker VP of Engineering Azigo
|
