Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Ensure that the rest of the specification is editorially aligned and consistent with the DC API section #453

Open
awoie opened this issue Mar 12, 2025 · 2 comments
Open

Ensure that the rest of the specification is editorially aligned and consistent with the DC API section #453

awoie opened this issue Mar 12, 2025 · 2 comments
Assignees
@awoie
Labels
ready-for-PR
Milestone
Final 1.0

Comments

@awoie
Copy link
Contributor

awoie commented Mar 12, 2025 •
edited
Loading

There are several sections in the current specification that were written before the DC API was added as an annex. Some of these sections are not applicable, while others were drafted without considering DC API. This especially relates to sections referring to OAuth/OIDC.

An editorial cleanup PR might be needed to update the relevant sections and clarify which ones do not apply to DC API in the current version of the specification.
@bc-pi
Copy link
Member

bc-pi commented Mar 12, 2025 •
edited
Loading

A pass at such editorial alignment seems like a good idea.

@Sakurann
Copy link
Collaborator

co-chairs discussed and agree that what is described in the PR needs to be addressed. marking ready-for-PR

@Sakurann Sakurann added this to the Final 1.0 milestone Mar 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@awoie awoie

Labels
ready-for-PR
Projects
None yet
Milestone
Final 1.0
Development

No branches or pull requests
3 participants
@awoie @Sakurann @bc-pi