(sourcelume-spec) branch common-corpus-stress-test updated: Clean up spec/0.0.1/index.md: trim field table, move license IRI conventions to a subsection, remove stress-test references

[an...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

ANierbeck pushed a commit to branch common-corpus-stress-test
in repository https://gitbox.apache.org/repos/asf/sourcelume-spec.git


The following commit(s) were added to refs/heads/common-corpus-stress-test by this push:
     new dd8b372  Clean up spec/0.0.1/index.md: trim field table, move license IRI conventions to a subsection, remove stress-test references
dd8b372 is described below

commit dd8b37281f4031ea90aad851a8ec9264f68c20bd
Author: anierbeck <ac...@codecentric.de>
AuthorDate: Sat Sep 12 15:52:20 2026 +0000

    Clean up spec/0.0.1/index.md: trim field table, move license IRI conventions to a subsection, remove stress-test references
    
    The field table had grown verbose: the `license` row carried a long
    parenthetical about two interim IRI conventions, and the four new license
    fields (licenseScope, licenseNote, licenseCategory, licenseHistory) each
    trailed a "Surfaced by the X stress test…" provenance note that belongs in
    notes/, not in normative spec prose.
    
    - Trim the four new field rows to their essential semantics (drop the
      "Surfaced by…" trailers and the redundant leading "Optional." since the
      Required column already says "no").
    - Move the two interim license-IRI conventions (CC Public Domain Mark for
      copyright-expiration PD; sourcelume agreement-supplied for agreement-gated
      data) out of the `license` cell into a dedicated "License IRI conventions"
      subsection below the table.
    - Remove the three remaining references to notes/stress-test-dfm-mimir.md
      (in the Status, Non-goals, and See-also sections) so the spec prose stands
      on its own without pointing at stress-test documentation.
    
    No schema, SHACL, context, or record changes. Validation: 30/30 PASS.
    
    Apache-ai: Yes
    Generated-by: pi (anthropic/claude-opus-4-1)
    Reviewed-by: anierbeck
---
 spec/0.0.1/index.md | 31 +++++++++++++++++++++----------
 1 file changed, 21 insertions(+), 10 deletions(-)

diff --git a/spec/0.0.1/index.md b/spec/0.0.1/index.md
index a8f4300..d9ed1a5 100644
--- a/spec/0.0.1/index.md
+++ b/spec/0.0.1/index.md
@@ -7,7 +7,7 @@ the minimal viable shape: enough to publish a checkable claim about one dataset'
 or more role-tagged creators, its license, its origin, and an ordered custody chain. It
 intentionally leaves out cryptographic attestation and downstream usage/audit metadata — those
 are planned for later, once Sourcelume Attest exists and once the dataset-vs-model-usage scope
-question is settled (see `notes/stress-test-dfm-mimir.md`).
+question is settled.
 
 ## Purpose
 
@@ -25,11 +25,11 @@ claim's accuracy — it gives the claim a consistent shape so it *can* be verifi
 | `identifier` | yes | string (IRI or DOI) | Identifier for the dataset being described. |
 | `name` | yes | string | Human-readable dataset name. |
 | `version` | no | string | Dataset version, if versioned. |
-| `license` | yes | IRI | License under which the dataset is claimed to be distributed (e.g. an SPDX license URL). Two interim conventions are documented for cases SPDX has no direct term: (a) for a public-domain-by-copyright-expiration claim, use the CC Public Domain Mark IRI (`https://creativecommons.org/publicdomain/mark/1.0/`); (b) for agreement-supplied data whose licensing does not permit public sharing, use `https://sourcelume.apache.org/ns#agreement-supplied`. Both are best-effor [...]
-| `licenseScope` | no | string | Optional. Jurisdiction or scope in which the claimed `license` applies, for cases where a license (especially a public-domain claim) is jurisdiction-scoped rather than global. For example: `US` for US judicial-work-product public domain, or a longer clause for a copyright-expiration public-domain claim whose term depends on jurisdiction. Omit for licenses that apply globally (e.g. CC0, MIT). Added after the Common Corpus stress test surfaced that the CC P [...]
-| `licenseNote` | no | string | Optional. Free-text qualifier for the claimed `license` IRI, for cases where the IRI alone is materially misleading. The classic case is a `license` IRI that reflects a processing artifact rather than an intended selection (e.g. a GitHub-code subset that filters to GPL-only by a bug, so the license IRI reads "GPL" even though the intent was permissively-licensed code). Use this field to flag the discrepancy so an auditor does not take the bare IRI at face  [...]
-| `licenseCategory` | no | enum | Optional. Category of the claimed `license`, so the license's licensing *model* is checkable at a glance rather than only by reading the IRI. Values: `open-source` (standard permissive OSS, e.g. Apache 2.0, MIT), `open-data` (standard permissive data license, e.g. ODC-By, CC0), `public-domain` (CC Public Domain Mark or equivalent), `agreement-supplied` (data shared under a bilateral agreement whose terms do not permit public sharing), `use-restricted` (o [...]
-| `licenseHistory` | no | array (min 1) | Optional. Record of prior licenses the dataset was distributed under, earliest first, when the dataset's own dataset-level license changed over time. The current license remains in the `license` field; this array records the superseded ones with their effective dates. Each entry: `iri` (prior license IRI) and `effectiveDate` (xsd:dateTime). Omit for datasets whose license has been stable since release. Surfaced by the OLMo/Dolma stress test (Dolm [...]
+| `license` | yes | IRI | License under which the dataset is claimed to be distributed (e.g. an SPDX license URL). See [License IRI conventions](#license-iri-conventions) below for public-domain and agreement-supplied cases. |
+| `licenseScope` | no | string | Jurisdiction or scope in which the claimed `license` applies, for cases where a license (especially a public-domain claim) is jurisdiction-scoped rather than global. For example: `US` for US judicial-work-product public domain, or a longer clause for a copyright-expiration public-domain claim whose term depends on jurisdiction. Omit for licenses that apply globally (e.g. CC0, MIT). |
+| `licenseNote` | no | string | Free-text qualifier for the claimed `license` IRI, for cases where the IRI alone is materially misleading. The classic case is a `license` IRI that reflects a processing artifact rather than an intended selection (e.g. a GitHub-code subset that filters to GPL-only by a bug, so the license IRI reads "GPL" even though the intent was permissively-licensed code). Omit when the IRI faithfully represents the licensing situation. |
+| `licenseCategory` | no | enum | Category of the claimed `license`, so its licensing *model* is checkable at a glance rather than only by reading the IRI. Values: `open-source` (standard permissive OSS, e.g. Apache 2.0, MIT), `open-data` (standard permissive data license, e.g. ODC-By, CC0), `public-domain` (CC Public Domain Mark or equivalent), `agreement-supplied` (data shared under a bilateral agreement whose terms do not permit public sharing), `use-restricted` (open IP grants but wi [...]
+| `licenseHistory` | no | array (min 1) | Prior licenses the dataset was distributed under, earliest first, when the dataset's own dataset-level license changed over time. The current license remains in the `license` field; this array records the superseded ones. Each entry: `iri` (prior license IRI) and `effectiveDate` (xsd:dateTime). Omit for datasets whose license has been stable since release. |
 | `creator` | yes | array (min 1) | One or more parties involved in producing this dataset — each a `schema:Organization` or `schema:Person` with a `name`, and an optional `role` (`originator`, `curator`, or `distributor`) to distinguish who made the underlying data from who aggregated or redistributed it. Omit `role` for a single, undifferentiated creator. |
 | `created` | yes | xsd:dateTime | When this provenance record was authored (record metadata, not content provenance). Distinct from `added` and `contentCreated` below. |
 | `added` | yes | xsd:dateTime | When the dataset was added to the collection being described (e.g. when a source was incorporated into dynaword). Mirrors the `added` field in dynaword datasheets. |
@@ -37,6 +37,20 @@ claim's accuracy — it gives the claim a consistent shape so it *can* be verifi
 | `origin` | yes | string | Free-text description of where the dataset's underlying data came from. |
 | `custodyChain` | yes | array (min 1) | Ordered chain of custody events, earliest first. Each entry: `agent` (IRI), `action` (string, e.g. `"collected"`, `"ingested"`, `"transformed"`), `startTime` (xsd:dateTime). A single-hop dataset has exactly one entry. |
 
+## License IRI conventions
+
+Two interim conventions for cases SPDX has no direct term. Both are best-effort placeholders
+pending a more precise term if/when the dev list takes it up.
+
+(a) **Public domain by copyright expiration.** Use the CC Public Domain Mark IRI,
+`https://creativecommons.org/publicdomain/mark/1.0/`. Pair with `licenseScope` when the PD
+status is jurisdiction-scoped (e.g. US case law, Gutenberg books whose PD term depends on
+jurisdiction) rather than a worldwide claim.
+
+(b) **Agreement-supplied data.** For data shared under a bilateral agreement whose terms do
+not permit public sharing (e.g. a data donation gated by a usage agreement), use
+`https://sourcelume.apache.org/ns#agreement-supplied`.
+
 ## Non-goals for 0.0.1
 
 - **No signature block.** Cryptographic signing is Sourcelume Attest's responsibility; this
@@ -46,7 +60,7 @@ claim's accuracy — it gives the claim a consistent shape so it *can* be verifi
 - **No usage/audit metadata.** `ProvenanceRecord` is deliberately dataset-centric. A model
   producer's downstream usage claims about a dataset (e.g. a memorisation audit) belong to a
   separate, later record type, not to this one — this is a scope decision worth raising on the
-  dev list rather than a settled fact, see `notes/stress-test-dfm-mimir.md`.
+  dev list rather than a settled fact.
 
 ## See also
 
@@ -55,6 +69,3 @@ claim's accuracy — it gives the claim a consistent shape so it *can* be verifi
 - [`schema/0.0.1/sourcelume.shacl.ttl`](../../schema/0.0.1/sourcelume.shacl.ttl) — RDF-level validation.
 - [`examples/minimal-record.jsonld`](../../examples/minimal-record.jsonld) — a conformant example.
 - `mappings/` — crosswalks to Croissant, the SPDX AI Profile, and OTDI (draft).
-- [`notes/stress-test-dfm-mimir.md`](../../notes/stress-test-dfm-mimir.md) — real-dataset stress
-  test that motivated the `creator`/`custodyChain` shape above and raises the still-open
-  usage/audit scope question.


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@sourcelume.apache.org
For additional commands, e-mail: commits-help@sourcelume.apache.org