Centralize schema license metadata

Author: christabone

LICENSE-DATA.md

@@ -23,6 +23,10 @@ The authoritative FlyBase licensing statement is maintained on the
 manifest accompanying a release controls the included-source and attribution
 details for that release.
 
+Each graph release points to this complete notice once through
+`DatasetRelease.license_notice_uri`. License metadata is not copied onto
+biological entities, assertions, relationships, predicates, or properties.
+
 ## No stable dataset yet
 
 This repository is pre-release. The presence of a schema draft, example, or

README.md

@@ -44,11 +44,11 @@ configuration must never be committed.
 
 ## Licensing and citation
 
-Repository software is licensed under the [MIT License](LICENSE). FlyBase-
-produced data and annotations are licensed under
-[CC BY 4.0](LICENSE-DATA.md). A release manifest will identify source and
-license information for each included data family; third-party material is not
-automatically covered by the FlyBase data license.
+See [LICENSE](LICENSE) for repository software and
+[LICENSE-DATA.md](LICENSE-DATA.md) for data and release-component notices.
+Each published graph records that notice once through
+`DatasetRelease.license_notice_uri`; license metadata is not repeated on
+biological records or schema members.
 
 When using a release, cite both FlyBase and the exact graph release identifier.
 See [CITATION.cff](CITATION.cff) and FlyBase's

docs/data-dictionary.md

@@ -36,6 +36,10 @@ not a stable data release.
   `go_source_bundle_approved`. The active registry therefore contains exactly
   59 of 69 declared contracts for H1. Negated, relationless, incomplete, and
   text-derived annotations cannot support a positive traversal edge.
+- Release licensing is centralized: `DatasetRelease.license_notice_uri` is the
+  sole graph-level carrier and points to the complete release notice.
+  Per-member license fields and the redundant `LicenseDeclaration` type are
+  removed; `LICENSE-DATA.md` remains the repository notice.
 
 ## What did not change
 

docs/rc1-to-rc2.md

@@ -3,5 +3,6 @@
 No stable FlyBase Knowledge Graph release has been published yet.
 
 Every future release page will identify the FlyBase release, schema version,
-dataset revision, formats, counts, checksums, source/license inventory, known
-exclusions, compatibility, and migration notes.
+dataset revision, formats, counts, checksums, the release-level license notice,
+source inclusion inventory, known exclusions, compatibility, and migration
+notes.

docs/releases.md

@@ -11,12 +11,16 @@ It does not connect to production Neo4j or expose FlyBase instance data.
 2. Narrow the view by biological domain or member kind.
 3. Select a type or relationship in the graph, matching-results list, or table.
 4. Read its definition, identifier rule, source basis, evidence/provenance role,
-   cardinality, license status, disposition, and known limitations. Direct
+   cardinality, disposition, and known limitations. Direct
    traversal relationships also show their Neo4j type, predicate contract,
    exact source predicate identities, direction transform, external-mapping
    classification, and fail-closed exclusions.
 5. Copy the resulting URL to share a direct link to the selected member.
 
+Licensing is deliberately not repeated on every browser member. The
+`DatasetRelease` type defines the single `license_notice_uri` for a published
+graph release; the repository notice is `LICENSE-DATA.md`.
+
 Use **Show full graph** to leave a focused neighborhood and **Reset filters** to
 restore the complete candidate. Blue solid arrows are generated biological
 traversal projections. Gray dashed arrows are structural assertion paths. The

docs/schema-browser.md

@@ -32,6 +32,16 @@
   - A future versioned curator-approved mapping assertion may map raw labels.
   - No lexical or model-generated mapping is accepted as evidence.
 
+## D-004 — Where is release licensing represented?
+
+- Status: **resolved in rc2**
+- Evidence: License and attribution metadata describe the published release and its component notices; repeating them on every schema type, property, predicate, relationship, and source record adds noise without changing the biological contract.
+- Impact: Consumers need one authoritative notice location without mistaking license metadata for biological data.
+- Recommendation: Store exactly one license_notice_uri on DatasetRelease, keep the complete repository notice in LICENSE-DATA.md, and do not materialize per-member LicenseDeclaration records or license fields.
+- Alternatives:
+  - Repeat license metadata on every member (rejected as redundant).
+  - Keep a source-to-license graph (deferred unless a future release has a demonstrated query requirement).
+
 ## H1-001 — Which canonical GO annotation source should public v1 use?
 
 - Status: **H1 decision required**
@@ -147,7 +157,7 @@
 | `IsoformDomainResidueInterval` | type | No bounded current-polypeptide domain/residue coordinate source rows were found. | No domain/residue claims. | A new approved coordinate source is audited. |
 | `OMIMFields` | property | Redistribution basis was not established. | All OMIM IDs, names, and content are absent. | Explicit terms are documented and approved. |
 | `PhysicalInteraction` | type | Physical-interaction participant/experiment grain was not integrated by the bounded WP2 reports. | Physical interactions are absent; raw allele genetic-interaction statements remain. | A bounded source audit covers interaction, participant, experiment, and publication rows. |
-| `PublicationPropertyAssertion` | type | Chado pubprop types have not been allowlisted field by field. | Publication properties beyond identifier/type subset are absent. | Property-type source/license inventory is complete. |
+| `PublicationPropertyAssertion` | type | Chado pubprop types have not been allowlisted field by field. | Publication properties beyond identifier/type subset are absent. | Property-type source and redistribution inventory is complete. |
 | `PublicationRelationshipAssertion` | type | Relationship semantics and publication-field licensing need a bounded source audit. | PUBLISHED_IN is not public in rc2. | Source predicate/direction and field terms are approved. |
 | `PublicationText` | property | Title/author origin is pending and abstract/personal communication/comments lack an approved blanket redistribution basis. | Publication records are identifier-only. | Field-origin and redistribution classifications are complete. |
 | `ReportScopedModelModifierRescue` | type | Approved source inventory proves this structured grain unavailable for this build. | No report narrative or adjacency can create these claims. | A new approved structured source is audited. |

docs/schema-decision-log.md

@@ -1,7 +1,8 @@
 # FlyBase source documentation mappings
 
 The generated source-to-schema inventory is
-`../../schema/generated/source-license-matrix.md`. Every public member in the
+`../../schema/generated/source-inclusion-matrix.md`. Every public member in the
 canonical schema names its exact source product and fields, evidence role,
-provenance behavior, null behavior, and redistribution license. Unresolved or
-unlicensed fields are explicit exclusions rather than inferred mappings.
+provenance behavior, and null behavior. Sources with unresolved redistribution
+status remain explicit exclusions rather than inferred mappings. The release's
+single license notice pointer is `DatasetRelease.license_notice_uri`.

mappings/flybase-source-documentation/README.md

@@ -51,5 +51,5 @@ contract.
 A later release may promote one or more profiles only after all public members
 are covered, exact and lossy mappings are mechanically distinguishable,
 canonical-to-profile-to-canonical round trips preserve meaning and nulls, and
-the profile passes the same source/license and negative-boundary validation as
+the profile passes the same source inclusion and negative-boundary validation as
 the native schema.

mappings/interoperability/spike-decisions.md

@@ -15,10 +15,11 @@ The generator rejects duplicate members, invalid relationship endpoints,
 unclassified current production members, unsafe Neo4j relationship names,
 predicate/endpoint collisions, incomplete assertion or projection registries,
 identity-vector drift, support-table drift, public fields with excluded sources
-or licenses, and mismatches between canonical membership and browser JSON. It
+or unresolved redistribution status, and mismatches between canonical
+membership and browser JSON. It
 expands the 69 reviewed predicate contracts into endpoint-specific traversal
 relationships and produces the data dictionary, decision log, diagrams,
-projection registry, identity contracts, change table, source/license matrix,
+projection registry, identity contracts, change table, source inclusion matrix,
 negative fixtures, JSON Schema, schema summary, Biolink crosswalk, and browser
 data under `generated/` and `../docs/`.