Implementation Guidance: File Suffixes for JSON-LD Data Exports

[mrgarth]

Implementation Guidance: File Suffixes for JSON-LD Data Exports

For files adhering to the Common Impact Data Standard, which utilizes JSON-LD, both .jsonld and .json suffixes are technically valid, as JSON-LD is structurally compatible with and a superset of standard JSON, with the official W3C media type being application/ld+json. When implementing parsers and processors, developers must ensure the software accepts files with either the recommended .jsonld extension or the widely compatible .json extension. However, for exported files, we recommend using the .json suffix as the standard default to maximize interoperability with generic JSON tooling and environments that may not explicitly recognize or support the less common .jsonld identifier.

For maximum compatibility and ease of integration, here is our guidance on handling file extensions for Common Impact Data Standard files:

• Accept Both: Your ingestion and parsing routines must accept files with both the .jsonld and .json suffixes. Both are technically valid for JSON-LD content.
• Export Preference: When exporting or generating data files, prefer the .json suffix. This aligns with general ecosystem expectations and ensures the widest compatibility with existing JSON tooling, editors, and environments.
• W3C Context: Note that the W3C primarily defines JSON-LD via the media type application/ld+json, which is a more robust content identifier than the filename suffix.