search

solid / data-interoperability-panel

Repository for the Solid Data Interoperability Panel
MIT License
51 stars 19 forks source link

Consider referencing notifications subscription from an agent registration #241

Closed elf-pavlik closed 1 year ago

elf-pavlik commented 2 years ago

Thinking of discussion in #238. New Solid Notifications spec could represent each subscription as a resource. This subscription could be referenced in a similar way as interop:reciprocalRegistration, for example with interop:subscriptionToReciprocal. This way the agent this registration was created for (interop:registeredAgent) would have a way to tell that subscription exists and automatically terminate sending any further access receipts.

EDIT: The 'other' agent will have a way know about this subscription anyway based on the topic of the subscription would be the (reciprocal) agent registration. Still, the authorization agent may not have an implementation-independent way to discover that subscription.

elf-pavlik commented 2 years ago

Actually, the 'other' agent can just check social agent registration, which was created for them, for interop:reciprcalRegistration. If it links to the social agent registration, which they created, they don't need to deliver access receipts anymore to that agent.

We should just recommend (SHOULD) that the authorization agent subscribes to notifications from all the reciprocal registrations. And leave the responsibility of following updates to the agent for who registration was created.