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

Reflecting on Sparkplug Birth Messages #305

Open
egekorkan opened this issue Oct 13, 2023 · 0 comments
Open

Reflecting on Sparkplug Birth Messages #305

egekorkan opened this issue Oct 13, 2023 · 0 comments
Labels
Has Use Case Potential The use case can be extracted and explained mqtt related to mqtt protocol binding Selected for Use Case

Comments

@egekorkan
Copy link
Contributor

egekorkan commented Oct 13, 2023

In Sparkplug specification at https://sparkplug.eclipse.org/specification/version/3.0/documents/sparkplug-specification-3.0.0.pdf, chapter 6.4.19, the payloads of birth messages are defined. These include information on what the Edge node will publish to the broker. This makes me think that TDs can be useful in such situations. Instead or in addition to this structure, TDs can be used which would have additional benefits such as:

  • More semantic information about the messages
  • Option to indicate which topics the device will subscribe to

We cannot change the standard ourselves but it is something to think about for sure (also for discovery). Probably relevant for other protocols with such features.

@egekorkan egekorkan added the mqtt related to mqtt protocol binding label Nov 28, 2023
@egekorkan egekorkan added the Has Use Case Potential The use case can be extracted and explained label Jan 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Has Use Case Potential The use case can be extracted and explained mqtt related to mqtt protocol binding Selected for Use Case
Projects
None yet
Development

No branches or pull requests

2 participants