Open Gastronomy Standardv0.6

Standard / Changelog

Changelog

All notable changes to the Open Gastronomy Standard. OGS follows Semantic Versioning; see OGS Core §3. OGS-Bench is versioned separately (OGS-Bench).

[0.6.0] — 2026-11-13

v0.6 is a review of every controlled vocabulary. Many definitions only repeated their term ("Crustaceans.", "A soup course."), named mechanisms that are not true, or left the boundary between neighboring terms unstated; aroma groups had no definitions at all, and the example documents had filed aromas inconsistently as a result. Two explanation codes contradicted established food-and-beverage interactions. The translation bundles claimed expert human translation but contained errors and covered under a third of the terms. New rules apply to documents that declare 0.6.0.

Changed

  • Definitions rewritten across all vocabularies. Each says what a term covers and, where terms are neighbors, where it ends. Labels are written as words rather than IDs ("pan-fried", "gluten-free", "amuse-bouche", "cereals containing gluten"). Labels and definitions use US English; a few older IDs keep British spelling (sulphites, molluscs, botrytised, dealcoholised), with the British forms kept as alternates.
  • Aroma groups are defined with typical items, which settles boundaries: cinnamon, clove and nutmeg are sweet_spice, cumin and cardamom warm_spice (now labeled "savory spice"); cedar is wood/oak; pastry is confection/baked, brioche cereal/yeast; hay is herbal/dried_herb.
  • STRUCT_UMAMI_ENHANCE now means umami meeting umami (sake, aged Champagne, fino sherry) and requires umami in the beverage. It claimed that umami improves a beverage's fruit and body; umami makes most beverages taste harder, as RISK_UMAMI_TANNIN already said.
  • RISK_ACID_CLASH is narrowed to a very sharp dish with a very acidic beverage (both 7 or more), default severity low. An acidic dish usually needs an acidic beverage; the common fault is the reverse, now RISK_ACID_FLATTENS.
  • STRUCT_ACIDITY_BALANCE requires the beverage to be at least as acidic as the dish, and stops where RISK_ACID_CLASH starts.
  • Codes no longer fire together on textbook pairings. RISK_SWEETNESS_SAVORY excludes salty and spicy dishes (Sauternes with Roquefort is CONTRAST_SWEET_SALTY, off-dry Riesling with chili STRUCT_SWEET_OFFSET). CONTRAST_SWEET_ACID declares conditions and needs the beverage at least as sweet as a sweet dish. CONTRAST_RICH_CRISP keeps only the rich-dish, crisp-beverage case. RISK_ALCOHOL_OVERPOWERS and RISK_OAK_MASKS require a dish less intense than the beverage.
  • Code conditions are version-gated. A pairing is checked against the conditions of the OGS version it declares (vocab/releases/<version>/), so these changes do not affect earlier documents.
  • RISK_TANNIN_FISH names the likely mechanism (iron in the wine reacting with fish oils) instead of tannin alone.
  • Flambéing no longer "burns off the alcohol"; much of it remains.
  • Allergen definitions follow EU Regulation 1169/2011, Annex II, including khorasan wheat (not the trademark "kamut") and total SO₂ for sulfites.
  • filter is a coffee method only; tea leaves are not filter-brewed.
  • Beverage methods list the types they apply to as an array.
  • Translation bundles (fr, sv, ja) rebuilt to cover every term, group and code, and relabeled method: "machine": the old bundles said human_expert, but contained errors such as Swedish "fetma" (obesity) for richness and French "mariné" (marinated) for pickled. They await review by native-speaking experts. (OGS Internationalization §8.1)
  • Specification tables of vocabulary terms are generated from vocab/*.json and checked by the test suite, so they can no longer drift.

Added

  • Ingredient categories have a vocabulary file with definitions, and meat, poultry, fish, seafood, egg, condiment and alcohol join the list; protein remains for tofu, tempeh and seitan and for earlier documents. (OGS Composition §7.2)
  • Diets exclude ingredient categories (excludes_categories), so a vegetarian claim on a meat ingredient is an L2 error and on a dish that contains one an L2 warning. The diet module no longer has to say "meat is not an allergen" and stop there.
  • lactose_free diet, and alcohol_free excludes the alcohol ingredient category.
  • Explanation codes RISK_ACID_FLATTENS (the dish is more acidic than the beverage) and RISK_SPICE_TANNIN (chili heat makes tannin harsh), both with conditions. 50 codes in total.
  • Aroma groups earth/petrol, savory/animal (leather, barnyard) and vegetal/olive, three classic wine descriptors with no home before.
  • Textures: elastic, gelatinous, sticky, crumbly, airy, melting, and the mouthfeel terms coarse and watery.
  • Cooking methods: barbecued, gratinated, glazed (36 in total).
  • Component role sweet_element, so a dessert's main element has a role.
  • Beverage types cocoa (hot chocolate) and milk (including lassi, kefir and plant milks).
  • 23 beverage methods (47 in total): tea processing (steamed, pan_fired, shaded, roasted), coffee processing and brewing (washed, dry_processed, honey_processed, immersion, decaffeinated), beer (top_fermented, bottom_fermented, bottle_conditioned, nitro), sake (junmai, unpasteurized), spirits (pot_still, column_still, cask_strength), and malolactic, amphora_aged, solera, spontaneous_fermentation, unfiltered.
  • Ten cuisines with endonyms: Korean, Vietnamese, Greek, Turkish, Peruvian, American, German, Portuguese, Moroccan and Ethiopian. Every cuisine now has an English definition.
  • tea_type: "herbal" gets a warning in 0.6 documents: herbal drinks are type infusion.

Examples

  • Aroma entries refiled to the defined groups; the saffron risotto and Chablis pairing claimed shared earth notes on the strength of hay filed as soil. It now names what the two share: floral notes.
  • Steak au poivre with young Barolo declares RISK_SPICE_TANNIN; sencha declares the steamed method; meat, poultry, egg and alcohol ingredients use the new categories.

Benchmark

  • No change. OGS-Bench pins the v0.2 schemas and v0.3 vocabulary; all 213 prompts are unchanged.

[0.5.0] — 2026-11-13

v0.5 broadens what OGS can describe. Beverages cover every kind of drink and can describe a style as well as a product; a pairing can be judged against a single ingredient or against one part of a dish; dishes can be built from sub-preparations such as sauces. New rules apply to documents that declare 0.5.0; earlier documents keep their conformance level.

Added

  • Beverage types. type now covers wine, beer, cider, mead, sake, spirit, cocktail, coffee, tea, infusion, juice, soft_drink, kombucha, water and other (vocab/beverage_types.json). A cocktail is described as a beverage; its recipe stays out of scope. (OGS Composition §8)
  • Products and styles. kind: "style" describes a category ("young Barolo", "Champagne Brut NV") rather than a bottle; validators warn when a style carries a producer or a numeric vintage.
  • Non-vintage wines. vintage accepts "NV".
  • Grape shares. grape_varieties entries may be {variety, share}.
  • Style attributes. A controlled style block: color, sweetness, sparkling dosage, production methods (vocab/beverage_methods.json, 24 methods such as traditional_method, oak_aged, skin_contact, cold_brew), tea type, roast level, IBU and base spirit. Attributes used on the wrong type of drink are reported. (OGS Composition §8.1)
  • Serving temperature. serve_temperature_c as a {min, max} range in °C on dishes and beverages.
  • Ingredient pairings. A pairing's food side is a dish (dish_ref) or a single ingredient (ingredient_ref); explanation-code conditions read the ingredient's profile. (OGS Matching §2)
  • Pairing focus. focus names the component, ingredient or sub-preparation a pairing is judged against: the wine for the sauce, not the steak. (OGS Matching §2.1)
  • Sub-preparations. A dish component references another dish with preparation_ref (a sauce, a stock, a dough). Validators reject cycles, and the allergen roll-up follows sub-preparations. Components may declare their share of the dish. (OGS Composition §6.3)
  • 13 cooking methods (33 in total): boiled, simmered, stewed, pan_fried, stir_fried, marinated, dry_aged, toasted, caramelized, flambeed, reduced, pressure_cooked, slow_cooked.
  • Courses. side, pre_dessert, snack and breakfast join the nine existing courses, which now have a vocabulary file with definitions (vocab/courses.json).
  • Reference examples: steak au poivre with its sauce as a sub-preparation, paired with a young Barolo style and focused on the sauce; Parmigiano Reggiano with Champagne Brut NV (an ingredient pairing); oyakodon with sencha (a non-alcoholic pairing). All 32 examples reach L3.

Changed

  • fried is defined as deep frying; shallow frying is pan_fried.
  • A beverage claiming the alcohol_free diet must not declare an ABV above 0.5% (0.5 documents).
  • New field names are now defined: kind and style on a beverage, serve_temperature_c on a dish, share and preparation_ref on a component, focus and ingredient_ref on a pairing. A v0.4 document that used one of them as its own unprefixed field must rename it (custom fields are best prefixed with x-, OGS Core §9).
  • Core scope: cocktail recipes stay out of scope; cocktails themselves are in.

Known gaps

  • The fr, sv and ja vocabulary translations do not yet cover the new cooking methods, courses, beverage types and beverage methods; consumers fall back to English (OGS Internationalization).

Benchmark

  • No change. OGS-Bench pins the v0.2 schemas and v0.3 vocabulary; all 213 prompts are unchanged.

[0.4.0] — 2026-11-13

v0.4 makes explanations checkable against the data. Profiles gain the properties pairings depend on, aroma groups become controlled, every explanation code declares when it is true, and pairings declare how they were scored. An optional module adds allergens and diets. Requirements added in v0.4 apply to documents that declare 0.4.0; earlier documents keep their conformance level.

Added

  • Fat, pungency and overall intensity. structural.fat and structural.pungency (chili, pepper, mustard heat, distinct from alcohol_heat), and a profile-level intensity. Codes such as STRUCT_TANNIN_FAT, RISK_SPICE_ALCOHOL and STRUCT_INTENSITY_MATCH previously referred to properties OGS could not record. (OGS Sensory §4)
  • Controlled aroma groups. Each aroma family lists its groups in vocab/aromatic_families.json; items stay open. New families: nut, roast (char, roast, toast, coffee, tar) and cereal (bread, grain, rice, malt, yeast). (OGS Sensory §5.1)
  • Beverage mouthfeel. A mouthfeel dimension in vocab/textures.json: silky, velvety, round, supple, grippy, chalky, crisp, flabby, austere, viscous, fine mousse, frothy. Food texture terms such as "crispy" no longer have to describe wine. (OGS Sensory §6.5)
  • Explanation code conditions. Codes declare requires conditions over the dish and beverage profiles, plus match_type and labels. A pairing whose codes contradict its profiles is reported. (OGS Matching §6.2)
  • 15 new explanation codes (48 in total). A shared-aroma code for every family (AROMA_SHARED_DAIRY, _SAVORY, _CONFECTION, _VEGETAL, _MARINE, _NUT, _ROAST, _CEREAL); HARMONY_SWEET_SWEET, HARMONY_SALINE, HARMONY_CLASSIC, STRUCT_SALT_SOFTENS; risks RISK_SWEETNESS_SAVORY, RISK_UMAMI_TANNIN, RISK_ARTICHOKE_ASPARAGUS.
  • Scoring declaration. Pairings declare scoring: method, version and aggregation (weighted_mean, weakest_dimension, holistic, other). Score band meanings are normative; the algorithm is not. (OGS Matching §4)
  • exclude risk severity. A known failure that should not be recommended; the overall score must be below 60.
  • Allergens and diet module (optional). dietary on ingredients, dishes and beverages: contains, may_contain, free_from, suitable_for. The 14 EU allergens and six diets, with diet claims checked against allergens. (OGS Allergens and Diet)
  • Reference examples: a hen's egg ingredient (oyakodon is chicken and egg; the egg was missing). All 20 examples target 0.4.0 and reach L3.

Changed

  • L3 for 0.4 documents requires fat, pungency and overall intensity in every profile, a scoring declaration, and intensity_alignment and structural_balance sub-scores on every pairing.
  • L2 for 0.4 documents requires aroma groups that belong to their family.
  • x- extension fields are allowed in nested objects (aroma entries, match types, explanation entries, risks, dietary), as the core specification always said.
  • RISK_SWEETNESS_CONFLICT now describes one direction: the dish is sweeter than the beverage. RISK_SWEETNESS_SAVORY covers a sweet beverage on a savory dish.
  • A negative code's vocabulary severity is its default; the severity on a pairing's risk entry is authoritative.
  • contrast and refresh are defined as distinct mechanisms.
  • New field names (intensity in a sensory profile; dietary; scoring) are now defined. v0.3 did not reserve these names, so a v0.3 document that used one of them as its own unprefixed field must rename it (custom fields are best prefixed with x-, OGS Core §9).
  • Core scope: allergens move from "not covered" to the optional module; nutrition and religious or certification-based classifications stay out.
  • i18n: removed references to a pairing motivation field and to market and unit modules that do not exist.
  • Example corrections found by the new checks: a misapplied RISK_ACID_CLASH (the dish was not acidic) and an unsupported intensity-mismatch risk were removed; mis-filed aromas moved to their groups (cooked rice to cereal/rice, hazelnut to nut/toasted_nut, green apple to fruit/orchard_fruit, cherry to fruit/red_fruit); the wines use mouthfeel terms.

Benchmark

  • OGS-Bench reads the vocabulary of the v0.3 release (vocab/releases/v0.3/) as it already reads released schemas, so the new codes do not change its prompts. All 213 prompts are unchanged.

[0.3.0] — 2026-11-13

v0.3 makes the three conformance levels (L1 Structural, L2 Vocabulary, L3 Semantic) precise and checkable, and fixes schema gaps that made L3 unreachable. v0.1 and v0.2 documents that followed the specification remain valid.

Added

  • Precise conformance rules. OGS Core §7 now states exactly what each level checks and where: L1 by the schemas, L2 against the vocabularies, L3 by completeness and provenance. §7.1 explains how to check a document.
  • common.schema.json. Shared definitions (sensory values and profiles, aromatics, provenance, metadata) referenced by every entity schema.
  • Profile-level provenance. A sensory profile may carry provenance (source, confidence, method) that applies to all its values; a value's own fields take precedence. (OGS Sensory §7.3)
  • textures.json vocabulary. The 26 texture terms from OGS Sensory §6 as a vocabulary file, so texture can be checked at L2.
  • user_submitted as a pairing evidence.method, matching the core provenance model.
  • human_native documented as a translation method (the schema already allowed it).
  • Eight reference ingredients that the example dishes referenced but did not exist: butter, carnaroli rice, chicken thigh, dashi, fleur de sel, Parmigiano-Reggiano, short-grain rice, dry white wine.
  • Stable schema URLs. Every schema is served at the URL in its $id (for example https://opengastronomy.org/schema/v0.3/dish.schema.json), including the v0.1 and v0.2 releases, and can be fetched cross-origin.
  • This changelog, published at /standard/changelog/.

Changed

  • The detailed sensory-value format is now valid. The specification has always defined {"value": …, "confidence": …, "method": …, "source": …}, but the schemas only accepted plain numbers, so L3 could not be reached.
  • Grade must match score. The schema rejects a pairing whose grade does not match its overall_score (OGS Matching §5).
  • Entity schemas use the shared LString schema. v0.2 pasted a simplified copy into each schema. Language tags are now validated with the full BCP 47 pattern, and translation provenance may only use the fields in OGS Internationalization §7. Documents that broke those rules now fail L1.
  • Field descriptions, removed in v0.2, are restored in the schemas.
  • L2 now explicitly covers texture terms, explanation codes, negative codes in risks, and cuisine references. L3 spells out which values need provenance and what counts as provenance on a pairing score. (OGS Core §7)
  • Dish cuisine is documented as a cuisine reference; free text remains valid at L1 for v0.1 compatibility but does not meet L2.
  • Translation provenance at L3 is a SHOULD everywhere. OGS Internationalization §7 said "REQUIRES", contradicting §12 and OGS Core §7.
  • All specification documents now carry the standard's version (v0.3); the sensory, composition and matching specs still said v0.1.
  • Reference examples target 0.3.0, declare primary_language, use cuisine references, and state their sensory provenance (estimated). All reach L3.

Benchmark

  • OGS-Bench prompts embed the schemas of the OGS v0.2 release rather than the current schemas, so changes to the standard no longer change benchmark prompts or scoring. All 213 prompts are unchanged.
  • Scoring fix. Two runs from 2026-05-16 scored structured-output answers without schema validation, so invalid answers received full marks. Every published run was re-scored from its stored responses: only minimax-m2.7-highspeed changed (80.17 → 78.97, two answers). The correction is recorded in its result document under corrections.

[0.2.0] — 2026-04

  • Cuisine entity type with endonym-first naming and sub-cuisine hierarchy.
  • Internationalization: LString, BCP 47 language tags, multilingual vocabularies with translation bundles (OGS Internationalization).
  • Controlled vocabularies split into vocab/*.json.

[0.1.0] — 2026-02

  • Initial specification: ingredients, dishes, beverages, pairings; sensory, composition and matching models; explanation codes; JSON Schemas; examples.