[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[higgins-dev] Re: Simplifying Attribute Services
|
I think it should be kept. It's important to illustrate the difference between the IdAS Solution and the Attribute Service (i.e. direct access to Contexts vs. exposing them at a network endpoint).
Also, I think the ordering should be
1. IdAS Solution 1.1
2. Attribute Service 1.1
3. IdAS Proxy Service 1.1
4. XDI4j
.. because the first three incrementally build on each other.
Markus
On Wed, Jul 22, 2009 at 5:22 AM, Paul Trevithick
<ptrevithick@xxxxxxxxx> wrote:
Markus,
At the highest level (door #3 here: http://higgins-project.org) we have the Attributes Services (plural) solution category. For H1.1 we plan these three top level solutions:
- Attribute Service 1.1
- IdAS Solution 1.1
- XDI4J
1) Since we now want to add the new IdAS Proxy Service to H1.1, should we modify [1] to look like this?:
- IdAS Proxy Service 1.1
- Attribute Service 1.1
- IdAS Solution 1.1
- XDI4J
2) Since I know you are working on 1, 2, and 4, I’m wondering if you have the cycles to also maintain #3. If it would be too much work, perhaps we could just drop it from H1.1? It is a “nice to have”, whereas 1, 2, and 4 are “must haves.”
Your thoughts?
--Paul
[1] http://wiki.eclipse.org/Higgins_1.1_Plan#Attribute_Services
