OASIS Static Analysis Results Interchange Format (SARIF) TC

 View Only
Back to discussions
Expand all | Collapse all

Editor's Report for Meeting 2025-06-12

  • 1.  Editor's Report for Meeting 2025-06-12

    Posted 06-11-2025 16:36
    Dear members,

    As usual the editor's report is available in the draft pull request for
    the meeting minutes, this month at:

    - https://github.com/oasis-tcs/sarif-spec/pull/698

    But, as a service I send that part in addition via this email to the TC mailing list:

    Editor's report

    1. Created change-set to Fix typo in messages with embedded links #696:
    - [Fixed typo in messages with embedded links #696](https://github.com/oasis-tcs/sarif-spec/pull/696)
    - the editors kindly request approval by the members of the TC to merge
    into the SARIF v2.2 spec editor-revision-2025-06-12.

    2. Created change-set to Enhance rationale for notification object #695:
    - [Enhanced rationale for notification object #695](https://github.com/oasis-tcs/sarif-spec/pull/695)
    - the editors kindly request approval by the members of the TC to merge
    into the SARIF v2.2 spec editor-revision-2025-06-12.

    3. Created change-set to Provide prose explaining the use of guids #694:
    - [Provided prose explaining the use of guids #694](https://github.com/oasis-tcs/sarif-spec/pull/694)
    - the editors kindly request approval by the members of the TC to merge
    into the SARIF v2.2 spec editor-revision-2025-06-12.

    4. Created change-set to Add normative statement on case rules for required keys #693:
    - [Added normative statement on case rules for required keys #693](https://github.com/oasis-tcs/sarif-spec/pull/693)
    - the editors kindly request approval by the members of the TC to merge
    into the SARIF v2.2 spec editor-revision-2025-06-12.

    5. Created draft change-set to Seed the editor revision 2025-06-12 #691:
    - [Seeded the editor revision 2025-06-12 #691](https://github.com/oasis-tcs/sarif-spec/pull/691)
    - the editors plan to have this change-set additionally receive the
    change-sets from PRs #693, #694, #695, and #696
    - the missing PDF generation capability will also be added to that change-set,
    before requesting approval by the members of the TC to merge
    that editor revision into the SARIF v2.2 spec main branch.
    - the editors propose to use an email motion for approval of that PR #691.

    6. Requested guidance on issue #657:
    - [Is any escaping of URIs within "3.11.6 Messages with embedded links" needed? #657](https://github.com/oasis-tcs/sarif-spec/issues/657)
    - plaese cf. comment https://github.com/oasis-tcs/sarif-spec/issues/657#issuecomment-2963928696


    PS: I also suggest we discuss the PR on the possible futures of SARIF (Future.md)
    I suggested some review comment changes and would love to have feedback on these.
    I applied them directly on top of the initial changes from Charles because either
    I or GitHub could not spawn off a PR branch from that PR branch. Sorry for that.

    PPS: I created a single character nit fix on the prior minutes (restoring
    the initial hash character indicating the first level 1 heading).

    All the best and looking forward to our meeting,
    Stefan.


Related Content