maha research · governed federation

Evidence Graph — Source Contract

Evidence Graph — Source Contract is implemented as a source-bounded source contract guide.

Active canonical release · fedrelease_7bb9be573611a0bc8874ea65a66938b1 · exact revision sha256:d88aaa859bea94a0803e05e6c38b44eb3d9d8ebf3f8989eb1b5700d1bfa33870

answer

Direct answer

Evidence Graph — Source Contract is implemented as a source-bounded source contract guide.

method

Answer contract

Apply the source contract lens only to the exact inspected source scope; do not infer authority from adjacent topics.

evidence

Evidence and exact locators

w3c-prov-o-evidence-graph-t9 — https://www.w3.org/TR/prov-o/ — Recommendation, 30 April 2013; Entities, Activities and Agents; used; wasGeneratedBy; wasDerivedFrom; wasAssociatedWith; wasAttributedTo. Supports: PROV-O can represent typed provenance between entities, activities, agents, inputs, outputs, derivations, associations, and attributions.

datacite-schema-evidence-graph-t9 — https://datacite-metadata-schema.readthedocs.io/en/4.6/ — version 4.6; Identifier; Creator; Contributor; Version; RelatedIdentifier; Rights. Supports: Versioned metadata can name research objects, contributors, versions, typed relations, and rights statements.

limitations

What the evidence does not establish

PROV represents asserted provenance; it does not verify truth, completeness, authentication, rights, causal validity, or passage-level claim support.

Metadata fields do not establish source quality, lawful collection, relationship truth, or that one object supports another object’s claim.

rights

Rights and reuse

Publicly accessible source; link and bounded paraphrase only. No source text is redistributed.

relationships

Dependencies and related concepts

applies-to: urn:maha:concept:evidence:evidence-graph

governed-by: urn:maha:concept:governance

evidence-for: urn:maha:concept:evidence

required-by-specification

Source or implementation

This source or implementation section is constrained to the same inspected scope: PROV-O can represent typed provenance between entities, activities, agents, inputs, outputs, derivations, associations, and attributions. Versioned metadata can name research objects, contributors, versions, typed relations, and rights statements.

It must preserve the recorded boundary: PROV represents asserted provenance; it does not verify truth, completeness, authentication, rights, causal validity, or passage-level claim support. Metadata fields do not establish source quality, lawful collection, relationship truth, or that one object supports another object’s claim.

required-by-specification

Method

This method section is constrained to the same inspected scope: PROV-O can represent typed provenance between entities, activities, agents, inputs, outputs, derivations, associations, and attributions. Versioned metadata can name research objects, contributors, versions, typed relations, and rights statements.

It must preserve the recorded boundary: PROV represents asserted provenance; it does not verify truth, completeness, authentication, rights, causal validity, or passage-level claim support. Metadata fields do not establish source quality, lawful collection, relationship truth, or that one object supports another object’s claim.

required-by-specification

Limits and uncertainty

This limits and uncertainty section is constrained to the same inspected scope: PROV-O can represent typed provenance between entities, activities, agents, inputs, outputs, derivations, associations, and attributions. Versioned metadata can name research objects, contributors, versions, typed relations, and rights statements.

It must preserve the recorded boundary: PROV represents asserted provenance; it does not verify truth, completeness, authentication, rights, causal validity, or passage-level claim support. Metadata fields do not establish source quality, lawful collection, relationship truth, or that one object supports another object’s claim.

required-by-specification

Dependencies

This dependencies section is constrained to the same inspected scope: PROV-O can represent typed provenance between entities, activities, agents, inputs, outputs, derivations, associations, and attributions. Versioned metadata can name research objects, contributors, versions, typed relations, and rights statements.

It must preserve the recorded boundary: PROV represents asserted provenance; it does not verify truth, completeness, authentication, rights, causal validity, or passage-level claim support. Metadata fields do not establish source quality, lawful collection, relationship truth, or that one object supports another object’s claim.

bounded answers

Questions this page can answer

What is established?

Evidence Graph — Source Contract is implemented as a source-bounded source contract guide.

Which exact source establishes it?

w3c-prov-o-evidence-graph-t9, https://www.w3.org/TR/prov-o/ — Recommendation, 30 April 2013; Entities, Activities and Agents; used; wasGeneratedBy; wasDerivedFrom; wasAssociatedWith; wasAttributedTo; datacite-schema-evidence-graph-t9, https://datacite-metadata-schema.readthedocs.io/en/4.6/ — version 4.6; Identifier; Creator; Contributor; Version; RelatedIdentifier; Rights

What dependency remains separate?

PROV represents asserted provenance; it does not verify truth, completeness, authentication, rights, causal validity, or passage-level claim support. Metadata fields do not establish source quality, lawful collection, relationship truth, or that one object supports another object’s claim.

What uncertainty remains?

applies-to: urn:maha:concept:evidence:evidence-graph governed-by: urn:maha:concept:governance evidence-for: urn:maha:concept:evidence

What must not be inferred?

A source, locator, rights, scope, boundary, dependency, implementation, or release change requires a new exact-revision review.