This page lists every file the platform crosswalk adds, so maintainers can see the new data structures at a glance. Field meanings and the standards they map to are on the crosswalk page.

Path What it holds Format and schema Edited by License
_data/crosswalk/<identifier>.json One foundation’s accounts on code hosts and registries, its packages (purls), and the evidence for each link JSON, validated by _data/crosswalk-schema.json People, with suggestions from fdncrosswalk probe Apache-2.0 (repository data)
_data/crosswalk-schema.json Rules for the crosswalk files, with a $comment link to the standard behind each field JSON Schema draft-07 People Apache-2.0
_data/attestors.json People whose human-attested evidence counts as confirmed JSON, validated by _data/attestors-schema.json People, by reviewed pull request Apache-2.0
_data/attestors-schema.json Rules for the attestors file JSON Schema draft-07 People Apache-2.0
_data/projects-<identifier>.csv (existing) Two new columns, purl and codeRepository: each hosted project’s main package and source repository CSV Generated by fdncrosswalk sync-csv from the crosswalk; other columns unchanged Apache-2.0
api/v1/crosswalk/<identifier>.json One foundation’s crosswalk as JSON-LD, with computed confidence and ecosyste.ms links JSON-LD Generated by fdncrosswalk export CC0-1.0
api/v1/crosswalk/context.jsonld JSON-LD context mapping every key to Schema.org, Dublin Core, PROV-O or fdn: terms JSON-LD Generated CC0-1.0
api/v1/crosswalk/vocab.jsonld Definitions of the fdn: terms no standard covers, such as fdn:steward JSON-LD (RDFS) Generated CC0-1.0
api/v1/crosswalk/stewards.jsonl One line per confirmed or probable link, keyed as ecosyste.ms names things, for bulk joins JSON Lines Generated CC0-1.0
assets/python/fdncrosswalk/ The tool that validates, scores, probes, exports and syncs Python 3.12 package managed with uv People Apache-2.0
_pages/crosswalk.md, _pages/crosswalk-files.md Documentation Markdown People Apache-2.0

How the directories and file names were chosen

  • _data/ holds every dataset Jekyll loads as site.data, next to the existing foundations-schema.json, projects-*.csv and sponsorships/.
  • _data/crosswalk/<identifier>.json: one file per foundation, named with the same identifier as _foundations/<identifier>.md, so a foundation’s crosswalk is easy to find and the tool can check the two match. It is kept apart from the foundation record so the record stays short and tools can rewrite the crosswalk without touching it.
  • <name>-schema.json sits beside the data it checks, following foundations-schema.json and sponsorships-schema.json.
  • _data/attestors.json is a single small list, since it names people rather than foundations.
  • api/v1/crosswalk/ holds only generated files. It is published as static files at fossfoundation.info/api/v1/crosswalk/, and the v1 leaves room for a later incompatible version, as openapi/v1/ does.
  • assets/python/fdncrosswalk/ follows AGENTS.md: new tools use Python with uv, beside the existing assets/ruby/ scripts.
  • Exports are CC0-1.0 because they are factual data points gathered largely automatically; code and human-written text stay Apache-2.0.