Informational guide. Not legal advice. Verify against primary source →
Spec contract — food v1.0
Two files, one schema.
Both artefacts render from a single schema definition, so they cannot disagree. One is for citation and linked-data tooling; the other is for validators.
spec.json
application/ld+json
JSON-LD. The citation-grade artefact. Extends schema.org with a vocabulary for the fields this standard adds.
Vocabulary: https://standards.flintmere.com/food/v1.0/vocab#
spec.schema.json
application/schema+json
JSON Schema. What tooling validates a product record against.
Dialect: https://json-schema.org/draft/2020-12/schema
Fetching it.
No key, no rate limit, no attribution required.
Both files are CC0 and served with a permissive CORS header, so they can be fetched from a browser as well as a server.
curl -H 'Accept: application/ld+json' \ https://standards.flintmere.com/food/v1.0/spec.json
Field types.
Shape and cardinality.
| Field | Type | Required |
|---|---|---|
| gtin | string | yes |
| allergen | string[] | yes |
| ingredient | object[] | yes |
| country_of_origin | string | yes |
| net_content | object | yes |
| lifecycle | object | no |
| dietary_certifications | string[] | no |
Stability contract.
What can change under a URL, and what cannot.
- A pinned URL (/food/v1.0/) never changes meaning. Its artefacts are byte-stable except where a patch release explicitly says otherwise.
- A patch (v1.0.1) fixes a typo or a citation URL without changing meaning, and publishes at its own URL.
- A minor (v1.1) adds an optional field. Records valid against v1.0 stay valid.
- A major (v2) redefines something. Old pinned URLs stay live indefinitely.
- The rolling alias /food/v1/ tracks the current v1.x and will change. Do not cite it.