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

Versioning of Registry Entries #400

Open
egekorkan opened this issue Feb 4, 2025 · 3 comments
Open

Versioning of Registry Entries #400

egekorkan opened this issue Feb 4, 2025 · 3 comments
Labels
registry mechanism related to how the binding registry operates

Comments

@egekorkan
Copy link
Contributor

As part of #378 at https://github.com/w3c/wot-binding-templates/blob/a052686548bec6aed802e7e309fabe5232c1556e/registry-requirements.md#entry-format under point 8, we have agreed to put a version field in the entry. However, we did not decide on how that version entry should look other than requiring a string. If we do semantic versioning, what does MAJOR, MINOR, PATCH mean. Relates a bit to w3c/wot-thing-description#1969

@egekorkan egekorkan added the registry mechanism related to how the binding registry operates label Feb 5, 2025
@egekorkan
Copy link
Contributor Author

egekorkan commented Mar 12, 2025

Call of 12 March:

  • The dependencies of a binding can indicate versions as well
  • Some directions:
    • Specify a versioning scheme: No strong opinions or proposals on this so far.
    • Let the submitters manage it but require some basics like unique versions
    • Latest version should be indicated and at least a chronological ordering would be good, i.e. not random hash values.
  • We can wait and see how people are using the registry before deciding on a semantic versioning scheme. Until then, we can use a unique string/tag.
  • The previous versions etc. can be in the summary document
  • The date the entry is written, should be also in the document, thus a requirement.

@egekorkan
Copy link
Contributor Author

Proposal:

  • Each registry entry MUST have a unique version within its own versioning history. E.g., there can be a CoAP and an HTTP binding with the same version.
  • All documents associated to the registry MUST follow the same versioning, i.e. all documents should update their version when there is a change.
  • The version MUST be a string that is visible in all the documents.
  • The version SHOULD contain a UTC-based date in ISO 8601 format in the form of YYYY-MM-DD.
  • All the previous of the entry MUST be listed as links in the summary document.
  • Each versioned entry MUST contain a changelog in the entry itself.

Some discussion points:

  • Should there be time in the date?
  • Should the date be mandatory in the version?
  • Do we want a separate binding version and document version?

@relu91
Copy link
Member

relu91 commented Mar 25, 2025

I think is sufficient to require an "ordering" function between the versions, whether this is done with dates or simple increasing integers it should not matter.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
registry mechanism related to how the binding registry operates
Projects
None yet
Development

No branches or pull requests

2 participants