from the July 19th Higgins developers call.
Amies - IBM
Austel - IBM
Hodgkinson - Novell
Buss - Novell
Byrd - NCSU/IBM
Carrol - Serena
Doman - Novell
Kokhan - Parity Ukraine
Kuehr-Mclaren - IBM
McIntosh - IBM
Nagaratnam - IBM
Olds - Novell
Srinivasan - Oracle
Reed - Cordance
Ruddy - Parity/SocialPhysics
*Jim Sermersheim - Novell
*George Stanchev - Serena
Schelat - IBM
Trevithick - Parity/SocialPhysics
Tsinman - Parity
• IdAS Registry
o http://wiki.eclipse.org/ContextId - Paul
o http://wiki.eclipse.org/Context_Discovery - Drummond
o http://wiki.eclipse.org/ContextDiscoveryComponents - Markus
M0.9 action items http://wiki.eclipse.org/Milestone_0.9
Update on the build situation
Paul: A number of new wiki pages have been created.
The first is http://wiki.eclipse.org/ContextId
Has questions about how context URI will morph.
First new page defines ContextID name and contextualized subjectID, now we can
talk about what an r-card is.
Contextualized subject ID is a fully defined way to refer to a
subjectID. There are also...
The next link on the page is context discovery http://wiki.eclipse.org/Context_Discovery
Globally unique or just with respect to a system?
They are globally identified, with a caveat. There are several levels of
support depending on where/how the resolution service is running.
We need to work on the use cases. For example a context for my HR business
unit, or my Credit Card Partner, or I want my local wallet context.
We've done some examples, and we need to do a lot more.
The problem is the examples are technology specific, rather than implementation
specific, within an organization, or cross organizations, etc.
That is a good idea, to add a bigger section on use cases.
We do also have a context discovery page
We just put in a few examples so far. The first is consumer facing. The second
is a relationship card and the third is more technical.
So we should add Raj's use cases on this page rather than on the other one.
I'm happy. Is there a plan to have the IdAS registry proposal lay out more of
the mechanics than are included here?
There is a third link with more of that http://wiki.eclipse.org/ContextDiscoveryComponents.
These wiki pages are interlinked.)
This is basically an implementation of...
Reads data from an XML file. Just put your existing configuration into
an XRDS document.
You said replacement for. Do you mean alternative to?
It initializes from this local XRDS file.
Have a context type question. Would it be appropriate to name Context types
according to the class?
One reason to make it implicit: Different deployments could have different
Application developers should only need to know the ContextID. They should be
We could just pass the ContextID as a string to the IdAS registry and let it
construct what it needs.
We need to be concerned about what application developers need to be concerned
with and what infrastructure developers need to be concerned with.
There is a lot of interest in separating the ContextID from the other info???
There are use cases where you need to discover it.
Need to make things very consumable to app developers
We could just put a method on ContextRegistry. Pass it a string or ContextID to
This could be done.
If you just pass the ContextID as a string to the ContextFactory...
If GetContextFactory could take a string, then...
Autodetect is very carefully constructed now so that you know what you've got
We only have a few minutes left in the call.
Mary, shall we move to the next topic?
Mary: Yes. The next topic is the M0.9 items. See
wiki page provided on the agenda.
The M 0.9 goal is that we freeze the architecture for R1.0 at the end of July.
So we can focus on tidying up what we have.
Can we add new methods?? Etc??
Have qualified the freeze to be at the component level. Wiki has been updated.
If we lock down the functionality. We
need to review the API's for consumeability.
For milestone 1.0, I'm adding that.
Consumability is very important.
This is an important theme: consumability.
It was the major topic on our last call. There are many levels at which
we need to be consumable: Builds, API's,
Yes. We are making progress on doing the builds.
We also have three committers that are going through the voting process.