Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[sparkplug-dev] Eclipse Sparkplug Specification Project – Meeting Notes – 01 December 2020

Eclipse Sparkplug Specification Project – Meeting Notes – 01 December 2020

 

  • Attendees
    • Chad Kienle
    • Dominik Obermaier
    • Frederic Desbiens
    • Ilya Binshtok
    • Josh Wolf
    • Nathan Davenport
    • Travis Cox
    • Wes Johnson
  • Ian Craggs has been nominated to join the Project. He has a lot of experience and is active and contributing in other Eclipse IoT projects. He is the project lead for Eclipses Paho. Committers, please vote.
  • Update on Sparkplug specification work.
    • Majority of spec port completed.
    • Lots of cleanup to be done.
    • Missing:
      • Normative statements linked to source code
      • General cleanup, errata fixed,
    • New build infrastructure is in place.
      • Uses Maven
      • Reviewed root POM file
      • “mvn generate sources” will produce the final version of the spec (HTML, PDF)
    • Sparkplug_spec.adoc defines which chapters are consumed as part of the build process.
      • Allows for dynamic TOC building
      • TOC max level configuration
      • TOC linking still possible within the spec
    • Goal mid-summer 2021 release of initial version of the spec.
    • We are only getting half participation in our Sparkplug Specification Project meetings... hopefully as we bring more folks in we can accelerate work completed.
    • Where do the Sparkplug A & B payload definitions belong?
      • In the actual spec or as separate docs?
      • There will likely be a Sparkplug C in the future. Do implementers need to implement all versions to be “compatible”?
      • Will Sparkplug C (JSON) become the defacto standard payload format?
      • Proposal: Move the payload definitions to the appendix? They will still include normative statements, links within the spec to payload specifics when necessary.
        • Decision: Undecided. The group will continue to think on this.
      • Proposal: Drop the Sparkplug A definition all up and do not include in the spec.
        • Decision: Approved. We will include a footnote somewhere within the spec that acknowledges the Sparkplug A, but that will be it.
  • Goals for the next 2 weeks
    • Continue and hopefully finish the spec port.
    • One E2E example with TCK annotations/normative statements.
    • If Ian Craggs joins the team, what is the best way to leverage his skills and get him up to speed?

 

Thanks,

Nathan


Back to the top