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

Wot-sec ontology #1978

Open
mahdanoura opened this issue Oct 4, 2023 · 4 comments
Open

Wot-sec ontology #1978

mahdanoura opened this issue Oct 4, 2023 · 4 comments

Comments

@mahdanoura
Copy link
Contributor

Many of the defined owl:DatatypeProperty in wot-sec.ttl ontology do not provide a rdfs:range.

@mmccool
Copy link
Contributor

mmccool commented Jan 15, 2024

This affects various downstream tasks, like knowledge graphs and HTML rendering. Other things are also missing, e.g. rdfs:domain. Should also make sure there is a comment for every definition so the documentation is reasonable (and not missing).
In some cases may have to define some other classes, but most are easy. If we only add data object properties to existing classes will be backward compatible, but other changes may not be.

@mmccool
Copy link
Contributor

mmccool commented Feb 26, 2024

This is the ontology in the TD repo. There is also some refactoring work that needs to go on. Should this issue be moved to the TD repo?

@mmccool
Copy link
Contributor

mmccool commented Feb 26, 2024

To clarify, we are talking about this file, right? https://github.com/w3c/wot-thing-description/blob/main/ontology/wotsec.ttl

@mmccool mmccool transferred this issue from w3c/wot-security Feb 26, 2024
@github-actions github-actions bot added the needs-triage Automatically added to new issues. TF should triage them with proper labels label Feb 26, 2024
@mmccool
Copy link
Contributor

mmccool commented Feb 26, 2024

Note that this refers to this resource: https://github.com/w3c/wot-thing-description/blob/main/ontology/wotsec.ttl
Assume some refactoring of this is also needed (e.g. to break into separate files for each concrete security scheme, move to appropriate bindings, etc) - but the domain thing needs to be fixed either way, may as well do it first, so the 1.1 version of the TD spec works properly.

@egekorkan egekorkan removed the needs-triage Automatically added to new issues. TF should triage them with proper labels label Mar 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants