Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "XDI Endpoint Backlog"

(New page: As discussed in the previous Austin F2F in October 2007, the Higgins project has decided that an IdAS web service is in scope for the future of Higgins. Parity will be developing and contr...)
 
m (logo, category, left menu)
Line 1: Line 1:
 +
{{#eclipseproject:technology.higgins}}
 +
[[Image:Higgins_logo_76Wx100H.jpg|right]]
 
As discussed in the previous Austin F2F in October 2007, the Higgins project has decided that an IdAS web service is in scope for the future of Higgins. Parity will be developing and contributing an XDI endpoint.
 
As discussed in the previous Austin F2F in October 2007, the Higgins project has decided that an IdAS web service is in scope for the future of Higgins. Parity will be developing and contributing an XDI endpoint.
 
* Can only be implemented as a layer over IdAS, not as a Context Provider
 
* Can only be implemented as a layer over IdAS, not as a Context Provider
Line 4: Line 6:
 
== See Also ==
 
== See Also ==
 
* [[Backlog]]
 
* [[Backlog]]
 +
 +
[[Category:Higgins IdAS]]

Revision as of 14:58, 18 March 2008

{{#eclipseproject:technology.higgins}}

Higgins logo 76Wx100H.jpg

As discussed in the previous Austin F2F in October 2007, the Higgins project has decided that an IdAS web service is in scope for the future of Higgins. Parity will be developing and contributing an XDI endpoint.

  • Can only be implemented as a layer over IdAS, not as a Context Provider

See Also

Back to the top