OASIS Static Analysis Results Interchange Format (SARIF) TC

Dear members,

I requested an action on me w.r.t. showing how the
OASIS Technical Report format looks by providing an
example.

Please find below the (1) announcement and links
to the pull request inside the Data Provenance Standards TC
repository for inspecting the format and how the mix of
marketing and technical content in that format might
spin out for our purposes.

Esp. the delivery item format PDF is of interest I guess:

https://github.com/oasis-tcs/dps/blob/technical-report-bootstrap/work-products/tech-report/tr-oasis-data-provenance.pdf

The OpenEoX Technical Report (using the marketing term
"white paper") as an additional example has been (2) announced on OASIS-Open site
here:

https://www.oasis-open.org/2025/04/29/oasis-openeox-white-paper-to-advance-global-framework-for-coordinated-product-end-of-life-security-disclosures/

and the PDF link is:

https://docs.oasis-open.org/openeox/standardization-framework/openeox-standardization-framework-technical-report.pdf

Here is the original DPS TC internal announcement of (1):

- - - - - - -

I prepared the first draft of the
technical report on data provenance standards.

You can find the change-set as pull request at:

https://github.com/oasis-tcs/dps/pull/83

You can read the markdown rendered as HTML by GitHub
in the feature branch at:

https://github.com/oasis-tcs/dps/blob/technical-report-bootstrap/work-products/tech-report/tr-oasis-data-provenance.md

and the PDF rendition (as it would look when
published via the OASIS tool chain) at:

https://github.com/oasis-tcs/dps/blob/technical-report-bootstrap/work-products/tech-report/tr-oasis-data-provenance.pdf

Finally the README.md documentation provides some minimal
information on the folder content (we target a subfolder
of our work proudcts).

Please let me know what ysou think!

- - - - - - - - - - - - -
End of insert.

What do you think?

Cheers,
Stefan.