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

Better validate/describe "variant records", eg in SecurityScheme and OAuth2 scheme #954

Open
mmccool opened this issue Aug 17, 2020 · 2 comments
Open

Better validate/describe "variant records", eg in SecurityScheme and OAuth2 scheme #954

mmccool opened this issue Aug 17, 2020 · 2 comments
Assignees
@mmccool
Labels
Defer to TD 2.0 Needed by other TF An issue or UC from another TF to fullfill a requirement in their spec or gap PR needed

Comments

@mmccool
Copy link
Contributor

mmccool commented Aug 17, 2020

In security schemes and inside the OAuth2 schemes, "variant records" are used where which other fields are valid depend on other data fields. This is not described very well in the tables and also we should discuss how/whether these are validated properly. There is an editor's note in the OAuth2 section.

This has also been discussed in Scripting (link to issue pending).
@mmccool mmccool self-assigned this Aug 17, 2020
@relu91
Copy link
Member

relu91 commented Aug 17, 2020

Here is the link to the relevant Scription API issue: w3c/wot-scripting-api#238.

@egekorkan egekorkan added PR needed V1.1 should be resolved in v1.1 labels Oct 26, 2021
@danielpeintner danielpeintner added the Needed by other TF An issue or UC from another TF to fullfill a requirement in their spec or gap label Feb 20, 2024
@danielpeintner
Copy link
Contributor

This issue has been scheduled for TD 1.1. Maybe we should move it to TD2 ?

@danielpeintner danielpeintner mentioned this issue Feb 20, 2024
Open
@egekorkan egekorkan added Defer to TD 2.0 and removed V1.1 should be resolved in v1.1 labels Feb 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mmccool mmccool

Labels
Defer to TD 2.0 Needed by other TF An issue or UC from another TF to fullfill a requirement in their spec or gap PR needed
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@relu91 @mmccool @danielpeintner @egekorkan