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

unwanted any type for title #1972

Open
egekorkan opened this issue Feb 11, 2024 · 3 comments
Open

unwanted any type for title #1972

egekorkan opened this issue Feb 11, 2024 · 3 comments
Assignees
Labels

Comments

@egekorkan
Copy link
Contributor

In #1966 , an unwanted change has appeared. As seen in comment https://github.com/w3c/wot-thing-description/pull/1966/files#r1485593582 , now the title is typed with "any type" in our spec in the table at https://w3c.github.io/wot-thing-description/#thing . @mahdanoura do you know why? The shacl shape looks correct.

@egekorkan egekorkan added the bug label Feb 11, 2024
@github-actions github-actions bot added the needs-triage Automatically added to new issues. TF should triage them with proper labels label Feb 11, 2024
@egekorkan egekorkan removed the needs-triage Automatically added to new issues. TF should triage them with proper labels label Feb 11, 2024
@egekorkan
Copy link
Contributor Author

egekorkan commented May 22, 2024

TD Call 22.05:

@mahdanoura
Copy link
Contributor

@relu91 did you have some time to look at this?

@egekorkan
Copy link
Contributor Author

Ideally, we should have:

  • Human-readable strings should be rdf:langString
  • All other strings should be xsd:string
  • The default language of the TD (in @language) should be only applied to rdf:langString

JSON-LD converter has the issue and not uRDF.js tool. So this needs to be addressed in JSON-LD and needs discussions with them. One related issue is w3c/json-ld-api#545 but there can be others we will add here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants