[Openid-specs-heart] Mechanical spec reorganization

[Justin Richer]

I’ve just spent most of today going through the three mechanical specifications and reorganizing the existing text in terms of the different relationships between HEART components and what compliance means between them. I’ve been able to break them down as follows:


OAuth
 - Client to AS
 - Client to RS
 - AS to client
 - AS to RS
 - RS to client
 - RS to AS

OIDC
 - IdP to RP
 - RP to IdP

UMA
 - Client to AS
 - Client to RS
 - AS to client
 - AS to RS
 - RS to client
 - RS to AS


Not all of these categories are filled in right now, but a read through the rough edits I made today makes me feel like there are definitely some holes that we need to fill in terms of specifying things for interoperability. The goal of this reorganization is to let a developer pick up the spec and go to the section that affects them directly and have all of the information they’d need available. We’ll of course have redundant information, especially when describing requirements on either side of a transaction (say AS to RS vs. RS to AS), but I think with good internal cross references it should be manageable. 

The XML source is in the repository, but I haven’t published the rendered versions yet. I’d like to take at least one more round of edits before doing that, and I hope to have that together by the end of this week.

 — Justin