[sparkplug-spec.committee] Sparkplug TCK process

[Frédéric Desbiens <frederic.desbiens@xxxxxxxxxxxxxxxxxxxxxx>]

Hi everyone.

One of the processes owned by the specification committee is the TCK process, which governs the following aspects of the TCK:

• Materials a TCK MUST possess to be considered suitable for delivering portability
• Ratifying a Final TCK
• Process for challenging tests and how these challenges are resolved
• Means of excluding released TCK tests from certification requirements
• Policy on improving TCK tests for released specifications
• Process for self-certification
• Process for (TCK) service release (x.y.z) to resolve a TCK challenge

Usually, it is the responsibility of the specification committee to elaborate on this process.

For your convenience, the Foundation's staff created an initial version of the process. This version is directly derived from the TCK process used by the Jakarta EE working group. You will find it in this document:

https://docs.google.com/document/d/1NuhACX1evbmT4kTPGuagTchAsNSM1NnUFRwnbIkwem4/

Please review and provide your feedback by COB on Thursday, November 3. I am letting you know that some links are missing and I will add them once obtained from members of the specification project.

The specification committee can alter the process at any time. So, once the ratified TCK is made available to Sparkplug implementers and the compatibility program is launched, you can tweak the process in response to implementer feedback.

Do not hesitate to contact me if you have questions about the process. Please add comments to the document if you want to discuss specific points or make suggestions.

Best Regards,

Frédéric DESBIENS

Program Manager — IoT and Edge Computing | Eclipse Foundation

Twitter: @BlueberryCoder

Eclipse Foundation: The Community for Open Innovation and Collaboration