[WG-UMA] Issue #3: should policy-uri be returned at Read, Update & List resource-set registration.

[Thomas Hardjono]

Dear UMAnitarians,

I've been reading (and re-reading) Issue#3:  Should the AM return info
about how the host can redirect the user to the policy definition page
(sharing setting screen) on the AM once the user says they want to
share something?

Maciej has kindly posted a SMART AM example, where the upon successful
registration by the Host, the AM returns a policy URI to the Host.

I think there is general consensus that this is a good optional
feature to include in the core spec. Returning a policy redirect URI
to the Host allows the Host to provide the User with an opportunity to
set policies for the resources that was just registered at the AM.


My question: 

(a) Should this policy redirect URI be returned to the Host (and shown
to the User) at resource registration events only?  (ie. solely at
Create Resource events)

(b) Or should the User be able to adjust the policies for existing
registered resources anytime the Host does a READ, UPDATE and LIST
resource-set descriptions?  In other words, should the policy URI be
optionally returned by the AM to the Host whenever these 3 commands
successfully execute.


Thoughts?


Thanks.

/thomas/