|Re: [jakartaee-platform-dev] Fair rules for "optional" TCKcompliance tests|
I thought so, but it will be interesting to see how the two other mentioned users of the EFSP use that because both SparkPlug and Asciidoc are more protocol definitions and not API centric. Especially Asciidoc describes itself as a text document format, so it’s like JSON or XML and has no similarity with e.g. the JAXB, JSONB or JSONP specs under Jakarta EE.
Some of these definitions were pretty much carbon-copied from the Java EE stack and JCP and now we see other standards use them that have more in common with those defined at OASIS or W3C than the JCP or Jakarta specs.
We are getting off topic here, but I can say "so far, so good"
with respect to Sparkplug's adoption of the EFSP. Too early to
tell with AsciiDoc at this point.
Executive Director | Eclipse Foundation, Inc.
Back to the top