Skip to main content

Contributing to SESM

Contribution Goals​

SESM welcomes review focused on:

  • metadata vocabulary clarity;
  • safe-profile rules;
  • validator behavior;
  • privacy considerations;
  • examples and fixtures;
  • interoperability with SVG, JSON-LD, archives, crawlers, and design systems.

Before Proposing Changes​

Read:

  1. Explainer
  2. Safe Profile
  3. Threat Model
  4. Privacy
  5. Conformance
  6. Validator Rules

Change Expectations​

Proposed changes should:

  • preserve the non-executable metadata boundary;
  • avoid granting authority to agents, crawlers, or renderers;
  • avoid embedding sensitive or private data;
  • include tests or fixtures when behavior changes;
  • update schema, examples, and validator rules together when vocabulary changes;
  • update the changelog for public-facing changes.

Running Tests​

Run:

python SESM\tests\run_tests.py
python SESM\Validate-SESM-Safe.py SESM\fixtures\valid\basic-safe.svg --safe-profile

Security and Privacy​

Security issues should follow the Security Policy.

Privacy-impacting changes should update the Privacy page and should explain how the change avoids covert tracking, accidental personal data exposure, and unauthorized agent behavior.

Standards Venue Notes​

If SESM moves into a formal community venue, contributor license or patent policy requirements from that venue may apply. Until then, this local suite uses the license on the License page.