UMA 1.0 core protocol specification
- Latest version on Kantara site (nice formatting): http://docs.kantarainitiative.org/uma/draft-uma-core.html
- Latest version contributed as an IETF Internet-Draft: http://tools.ietf.org/html/draft-hardjono-oauth-umacore
...
- Direct link to open issues: https://github.com/xmlgrrl/UMA-Specifications/issues
Issue docket
Our main 2012Q1 spec goal is to revise the IETF I-D in time for consideration at the IETF 83 meeting 25-30 March 2012, incorporating resolutions to all known A- and B-priority issuesas many open issues as possible. We also know of several active implementers and want to resolve outstanding issues as quickly as possible to support interop activities in 2012H1.
We ask all UMAnitarians to do a thorough review of the spec, adding issues on GitHub as they come up. Eve and Thomas will assign priorities, ask people to take action items, and create weekly telecon agendas based on these priorities.
Priority | Goal |
|---|---|
A | Resolve through 43 by 12 Jan 2012. Immediately resolve any new A-priority items as they come up. (#10 is going to take a little longer.) |
B | Resolve through 42 by 9 Feb 2012. Resolve any new B-priority items by 15 Mar 2012. |
C | Resolve as many as possible by 15 Mar 2012. Publish I-D rev by 16 Mar 2012 for consideration at IETF 83. |
|
|
Here are the currently open issues and their statuses.
...
Priority
...
Issue
...
Status
...
A
...
...
Assigned to Eve
...
A
...
...
Discuss with group
...
A
...
...
Discuss with group
...
A
...
...
Assigned to Rich and George
...
B
...
...
Assign to Paul
...
B
...
...
Discuss with group
...
B
...
...
Discuss with group
...
B
...
...
Assign to Susan
...
B
...
...
Assign to Paul
...
C
...
...
Assign to Paul
...
C
...
...
Dependent on Paul's AI to standardize CRUD APIs
...
C
...
...
Discuss with group
...
C
...
...
Discuss with group
...
C
...
...
Following is a catalog of breaking changes made since the 18 Jan 2012 rev.
- The resolution to issue #19 involved a breaking change in the 2 Feb 2012 rev. The XRD-formatted AM metadata residing at /.well-known/host-meta is now JSON-formatted metadata residing at /.well-known/uma-configuration.