-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Signed-off-by: Wouter Termont <[email protected]>
- Loading branch information
1 parent
e77c536
commit b5cd25b
Showing
1 changed file
with
40 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,40 @@ | ||
|
||
[LOGO] | ||
|
||
# Authorization for Data Spaces | ||
|
||
This is the repository of the **Authorization for Data Spaces** (A4DS) specification, managed by [IDLab](https://idlab.ugent.be)'s [KNoWS](https://knows.idlab.ugent.be) group. | ||
|
||
The A4DS specification defines a profile for the **User-Managed Access** (UMA) specifications published by the [Kantara Initiative](https://kantarainitiative.org), specifically: | ||
|
||
- [User-Managed Access (UMA) 2.0 Grant for OAuth 2.0 Authorization](https://docs.kantarainitiative.org/uma/wg/rec-oauth-uma-grant-2.0.html) | ||
|
||
- [Federated Authorization for User-Managed Access (UMA) 2.0](https://docs.kantarainitiative.org/uma/wg/rec-oauth-uma-federated-authz-2.0.html) | ||
|
||
A rendered HTML version of the specification can be read [here](https://solidlabresearch.github.io/authz-spec/). | ||
|
||
|
||
## Status | ||
|
||
The A4DS specification is currently under exploratory drafting, and consists of working documents, that have NOT been publically reviewed, but represent active research at their time of publication. As such, the documents may be subject to changes, and other documents may supersede them at any time. | ||
|
||
The specification is being drafted in multiple stages, each of which introduces extra requirements to tackle additional (and more complex) use cases: | ||
|
||
- **Level 0** describes the interfaces and protocols of the final prototype implementation presented in the white paper _From Resource Control to Digital Trust with User-Managed Access_ (cf. [SolidLab's white papers](https://solidlab.be/white-papers/)). It lays the groundwork for the general flow of the protocol. | ||
|
||
- **Level 1** will build on Level 0, to address some minor shortcomings discussed in the white paper, and optimise alignment with existing standards. | ||
|
||
- **Level 2** and higher will build on Level 1, to cover the more extensive questions left open in the white paper. | ||
|
||
|
||
## Contributing | ||
|
||
The editors welcome feedback, so don't hesitate to create an issue, or contact us via other channels. This goes for feedback regarding the content, but also for editorial changes that improve the readability or correct spelling/grammar mistakes. The editors cannot guarantee that all feedback will be processed, or when. | ||
|
||
To propose concrete changes — addressing a specific issue! — fork this repository and create a pull request to the relevant branch. The specification is built using [Bikeshed](https://speced.github.io/bikeshed/). Please make sure the build succeeds without errors or warnings before making a PR; and make the branch name, PR title, and PR description informative (incl. issue number, reasoning etc.) | ||
|
||
## Acknowledgements | ||
|
||
The [Knowledge on Web Scale](https://knows.idlab.ugent.be) (KNoWS) group is part of [imec](https://www.imec-int.com/en)'s [Internet Technology and Data Science Lab](https://idlab.ugent.be) (IDLab) at [Ghent University](https://www.ugent.be/en). | ||
|
||
Work on this specification is funded by [SolidLab Flanders](https://solidlab.be). |