@@ -52,7 +52,7 @@ The Registry Set can be discovered from a social agent's WebID Profile using `in
5252While WebID Profile is readable to the public, Registry Set should only be readable by its owner
5353and their Authorization Agent.
5454
55- <img class="flowchart-diagram" src="diagrams/registry-set.flow.mmd.png" / >
55+ <img class="flowchart-diagram" src="diagrams/registry-set.flow.mmd.png">
5656
5757<figure>
5858 <pre class=include-code>
@@ -86,7 +86,7 @@ In a Data Registry, there can be at most one Data Registration for any given sha
8686Data Registration is a container, which contains Data Instances. Each of those Data Instances conforms to one specific
8787shape tree assigned to the Data Registration.
8888
89- <img class="flowchart-diagram" src="diagrams/pro.alice.example.flow.mmd.png" / >
89+ <img class="flowchart-diagram" src="diagrams/pro.alice.example.flow.mmd.png">
9090
9191<figure>
9292 <pre class=include-code>
@@ -110,8 +110,6 @@ An Authorization Agent is not responsible for modifying data instances. Sometime
110110during [[#gathering-authorizations]] if the user wants to select specific data instances.
111111
112112
113- Issue(186):
114-
115113# Authorization Registry # {#authorization-registry}
116114
117115Authorization Registry is a container, which contains Access Authorizations.
@@ -200,7 +198,7 @@ from another Social Agent and performing [[#agent-registration-discovery]]
200198In the case of Social Agent Registration for ACME, created in Alice's Agent Registry. The reciprocal registration
201199will be the Social Agent Reigstration for Alice, created in ACME's Agent Registry.
202200
203- <img class="flowchart-diagram" src="diagrams/reciprocal-registration.flow.mmd.png" / >
201+ <img class="flowchart-diagram" src="diagrams/reciprocal-registration.flow.mmd.png">
204202
205203## Application Registration
206204
@@ -255,9 +253,9 @@ another's social agent Authorization Agent. The response will include a link to
255253
256254## Access Grant ## {#access-grant}
257255
258- An Access Grant grups together all the Data Grants provided for specific agent.
256+ An Access Grant groups together all the Data Grants provided for a specific agent.
259257
260- An Access Grant is immutable, it never gets updated, instead it can be only replaced with a newer Access Grant.
258+ An Access Grant is immutable — it never gets updated; it can only be replaced, by a newer Access Grant.
261259
262260<pre class=include> path: data-grant.bs</pre>
263261
@@ -292,11 +290,17 @@ It should also assist the user in composing new Access Authorization, taking int
292290* Data Registries with Data Registrations and Data Instances
293291* [[#access-grant]] with [[#data-grant]] others issued to them (available via all the [[#reciprocal-registration]] )
294292
295- <img src="images/authorization-screen.svg" width="100%" />
293+ <img src="images/authorization-screen.svg" width="100%">
294+
295+ <pre class=include> path: app-authorization-flow.bs</pre>
296+
297+ # Sharing resources indicated by the application # {#resource-indication}
296298
297- Issue(186):
299+ When the application has already been registered, and the user wants to
300+ initiate a sharing-specific [[#data-instance]] , an authorization flow with resource
301+ indication is available.
298302
299- Issue(138):
303+ <pre class=include> path: resource-indication-flow.bs </pre>
300304
301305# Generating Access Grant from Access Authorization # {#generating-grants-from-authorizations}
302306
0 commit comments