Hello SPDX Outreach team,

I’m Avraham Bregman, an independent developer working on AVI13.

I have started a small prototype called LicenseGuard13 whose purpose
is to stop an AI/research pipeline from accidentally exporting
artifacts that are usable for an experiment but not redistributable.
One motivating example is a licensed forensic disk/memory image:
analysis and public write-ups may be permitted while redistribution of
the source image is not.

Before creating our own rights vocabulary, I would like to understand
how much of this should be represented with SPDX 3.x and where SPDX
intentionally stops. In particular, I’m trying to distinguish
software/content license identity from additional contractual or
dataset-use restrictions without misusing SPDX license expressions.

Could you point me to the appropriate SPDX technical/legal discussion
or existing guidance for representing provenance plus redistribution
constraints on research/data artifacts?

Current code is an early local reference scaffold; it does not claim
SPDX compatibility yet.

Best regards,
Avraham Bregman
AVI13 / LicenseGuard13


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#1595): https://lists.spdx.org/g/Spdx-outreach/message/1595
Mute This Topic: https://lists.spdx.org/mt/121536301/21656
Group Owner: [email protected]
Unsubscribe: https://lists.spdx.org/g/Spdx-outreach/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-


  • SPDX routing question — Licen... אברהם ברגמן via lists . spdx . org

Reply via email to