John Teeter

Full support for the UsageSummary Resource

4

focus only on the webAPI, not the UX

DataCustodian Custodian Token Management Screen

1

/DataCustodian/custodian/oauth/tokens seems to not be displaying anything or (in the case of the management menus) causing any action to be performed.

Breaking down of the dynamic registration association b/t DC and TP

The additional CIM elements of UsagePoint and Retail Customer need to be supported.

The form /Subscription/{SubscriptionId}/CustomerResource .... needs to have the ability to reference both the UsagePoint and RetailCustomer top level structures.

UsageSummary Resource Support

2

Full support for the UsageSummary Resource

For example: 1 - clientId is Read-Only 2 - Secret is allowed to change 3 - GrantType is Read-Only etc.

Consider Splitting OAuth/Security stuff to separate services

1

To overcome the java 7 anchor.

Two forms LAP is a pNode that must be a child of an aNode. (see notes)