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

Add tentative rec11 resources #1863

Merged
merged 4 commits into from
Sep 27, 2023
Merged

Add tentative rec11 resources #1863

merged 4 commits into from
Sep 27, 2023

Conversation

egekorkan
Copy link
Contributor

@egekorkan egekorkan commented Jul 31, 2023

This adds the following to the publication/ver11/7-rec folder

  • TD and TM JSON Schemas
  • TM Ontology
  • TD Context File

They are copied from the main branch and from the same folders

@egekorkan
Copy link
Contributor Author

Regarding JSON Schemas: Should we remove the date from the version field? What do you think @relu91 ?

@danielpeintner
Copy link
Contributor

Regarding JSON Schemas: Should we remove the date from the version field? What do you think @relu91 ?

FYI: In the scripting API we used the date in the version field to create according TS definititions and label them accordingly.
see https://www.npmjs.com/package/wot-thing-description-types and https://www.npmjs.com/package/wot-thing-model-types

@egekorkan
Copy link
Contributor Author

Call of 02.08:

  • Similar to Add tentative rec10 resources #1862, we should document the implications of such resources
  • versioning:
    • Cris: We use this due to scripting API and we can have a special type package with 1.1.0 version. Ege +1 to version name.
    • Luca: This is wrong semver. If we use date, it would be better to use ISO date format. For future versions, we can use _pre20231223 to be more aligned with common practices.

@egekorkan
Copy link
Contributor Author

Call of 23.08: The publication folder is only a tentative area and it should not be used for this purpose. A separate repo is desired whose name is not important but can be github.com/w3c/wot-resources . It will not be visible to anyone since we will redirect anyways. It can be used by multiple WoT specs and it should have a more restricted access than the usual wot repositories. Chairs and Team Contact can only merge PRs and no one can make a commit to main branch.

@egekorkan egekorkan added the Propose closing Problem will be closed shortly if there is no veto. label Aug 23, 2023
@egekorkan egekorkan changed the title Add rec11 resources Add tentative rec11 resources Sep 20, 2023
@egekorkan egekorkan removed the Propose closing Problem will be closed shortly if there is no veto. label Sep 20, 2023
@egekorkan
Copy link
Contributor Author

Call of 20.09: The WG does not have a consensus on where to put these resources. Keeping it open until then.

@egekorkan
Copy link
Contributor Author

Call of 27.09: Merging. They will be moved to wot-resources folder later on

@egekorkan egekorkan merged commit 2fa5394 into main Sep 27, 2023
1 check passed
@egekorkan egekorkan deleted the ege-rec11-resources branch September 27, 2023 15:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants