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.

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

Inconsistencies in wotsec ontology #1908

Closed
mahdanoura opened this issue Oct 25, 2023 · 3 comments · Fixed by #1909
Closed

Inconsistencies in wotsec ontology #1908

mahdanoura opened this issue Oct 25, 2023 · 3 comments · Fixed by #1909
Labels
ontology Security Semantics Semantics-related issues

Comments

@mahdanoura
Copy link
Contributor

mahdanoura commented Oct 25, 2023

The PoPSecurityScheme class in the wotsec.ttl is commented out, but still used for some DataProperties. This makes the figure in https://w3c.github.io/wot-thing-description/#td-security-model show wrong information.

@mahdanoura mahdanoura added Semantics Semantics-related issues ontology Security labels Oct 25, 2023
@github-actions github-actions bot added the needs-triage Automatically added to new issues. TF should triage them with proper labels label Oct 25, 2023
@egekorkan egekorkan removed the needs-triage Automatically added to new issues. TF should triage them with proper labels label Oct 25, 2023
@egekorkan
Copy link
Contributor

The wrong information is missing fields in OAuth2 right?

@mahdanoura
Copy link
Contributor Author

The wrong information is missing fields in OAuth2 right?
Not this issue, it's rather pointers to a class called PoPSecurityScheme, while it does not exist anymore and is commented out. But some resources still point to it. This issue suggests removing those references to this class.

@egekorkan
Copy link
Contributor

The errors can be seen at https://w3c.github.io/wot-thing-description/ontology/wotsec

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ontology Security Semantics Semantics-related issues
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants