fair.md v0.3.1

fair.md v0.3.1 — community-readiness release

v0.3.1 packages the governance, citation, examples, and review-readiness work
accepted through pull request #3.
It is a backward-compatible patch release of the v0.3 proposed convention.

Highlights

• The canonical FAIR.md records the stable Zenodo concept DOI separately from
  version-specific citation identifiers.
• Contribution guidance, change-approval governance, a Code of Conduct, and a
  formal community-review process are now part of the repository.
• Complete v0.3 packages demonstrate a generic dataset and an illustrative
  ISA-Tab Investigation–Study–Assay project.
• Default validation includes nested examples/**/FAIR.md packages and their
  root-relative resources and evidence.
• Validator tests use the same recursive example discovery behavior.
• The ISA example consistently declares ENVO for environmental material and UO
  for degree Celsius.

Persistent identifiers

• All-version concept DOI:
  10.5281/zenodo.20793968
• Exact v0.3.1 DOI:
  10.5281/zenodo.21622631

Use the version DOI for reproducible citation of this release and the concept
DOI when referring to the evolving fair.md project across releases.

Scope and limitations

fair.md remains a proposed convention, not a certification scheme or an
endorsed community standard. Structural conformance does not certify that a
digital object is FAIR. Maintainer-authored assessment results require
target-specific evidence and independent scrutiny.

The ISA example is marked aligned, not adopted; it does not claim an
external ISA validator result or ISA community endorsement.

Community review

Formal review remains open to GO FAIR/FIP practitioners, FAIRsharing curators,
RDA FAIR assessment specialists, RO-Crate maintainers, ISA Tools experts,
research data stewards, and working scientists:

• Formal community-review issue #4
• Review request

Changes and validation

• Full changelog
• Compare v0.3.0…v0.3.1

fair.md v0.3.0

fair.md v0.3.0 — evidence before assertion

v0.3.0 is a major integrity and FAIR-logic revision of the fair.md convention: a portable FAIR.md front door that connects human-readable declarations, machine validation, implementation choices, and evidence-backed assessment.

Highlights

• Evidence objects replace unsupported scalar FAIR claims.
• RDA FAIR Data Maturity Model metric identifiers can be attached to results.
• Structured vocabulary, profile, resource, license, and conformance declarations make implementation choices explicit.
• FAIR and openness are assessed separately using an Open Definition posture.
• The fair-documented/ source pack records authoritative sources, standards mappings, evidence and checksum policies, an optional ISA profile, and RO-Crate metadata.
• The validator checks JSON Schema conformance plus cross-field integrity, exact-case local references, ORCID checksums, DOI syntax, and other semantic rules.

Persistent identifiers

• Exact v0.3.0 citation: 10.5281/zenodo.21621349
• All-version concept DOI: 10.5281/zenodo.20793968

Use the version DOI for reproducible citation of this release and the concept DOI when referring to the evolving fair.md project.

Scope and limitations

fair.md v0.3.0 is a proposed convention, not a certification scheme or an endorsed community standard. A conforming file demonstrates structural validity; FAIR assessment results still require target-specific evidence and independent scrutiny. This release does not claim endorsement by GO FAIR, FAIRsharing, RDA, RO-Crate, ISA Tools, or any other community.

Community review

Formal review is requested from GO FAIR/FIP practitioners, FAIRsharing curators, RDA FAIR assessment specialists, RO-Crate maintainers, ISA Tools experts, research data stewards, and working scientists.

• Public formal-review issue #4
• Community-readiness draft PR #3

The PR adds DOI clarity, governance and contribution controls, a Code of Conduct, complete generic-dataset and ISA-Tab v0.3 examples, recursive example validation, and structured review materials. Those additions are proposed after the archived v0.3.0 tag and are not silently represented as part of its immutable source archive.

Documentation

• Specification
• Changelog
• Full comparison: v0.2…v0.3.0

v0.2

Bump fair.md convention to v0.2 (#2)

Minor, backward-compatible release. companions may now be absolute http(s) URLs (additive, shipped in #1); fair_md_version accepts "0.2" with "0.1" still valid. SPEC, schema, README, manifests, template, CITATION.cff, and CHANGELOG bumped to 0.2.

doi release

Bump fair.md convention to v0.2 (#2)

Minor, backward-compatible release. companions may now be absolute http(s) URLs (additive, shipped in #1); fair_md_version accepts "0.2" with "0.1" still valid. SPEC, schema, README, manifests, template, CITATION.cff, and CHANGELOG bumped to 0.2.