Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 13 Next »

This page gathers information about implementation efforts and interest, along with interoperability testing plans. We have a goal to develop a hosted validator that can exercise implementors' AM, Host, Requester, and User Agent endpoints to increase interoperability, roughly in the March timeframe. To this end, we have secured a commitment from the Kantara Initiative to encourage validator development by offering a bounty (details to be announced).

Maciej Machulak is the UMA group's implementation coordinator. Several efforts are gearing up in earnest now.

Interest and effort mentioned so far (no obligation implied!):

Who

Protocol: AM

Protocol: Host

Protocol: Requester

UX: "relationship manager"

Notes

Maciej/Newcastle

(tick)

(tick)

(tick)

(tick)

SMART project UMA/j framework; see project overview and blog. Developed in Java; to be open-sourced. (The OAuth portion, named leeloo, has been open-sourced already.)

Christian Scholz/COMlounge.net

(tick)

(tick)

(tick)

(tick)

Prototype and demo in Python.

Iain/Mydex

(tick)

(tick)

 

(tick)

Intends to do an UMA-compliant implementation. Currently the Mydex work is built on ID-WSF and information cards.

PaulT/Azigo

(tick)

(tick)

 

(tick)

Intends to do an UMA-compliant implementation. Currently the Azigo work is built on Higgins and includes information card support.

Peter/Neustar

(tick)

(question)

 

 

Intends to do a mobile-based AM prototype, likely to be ready for testing by the July timeframe.

Paul Bryan

 

(question)

 

 

A module that assists websites in becoming "UMAnized" (able to have their resources UMA-protected).

Mario/Fraunhofer

(question)

(question)

(question)

(question)

Working on a mobile location scenario.

  • No labels