Adding more keys to recipe.json?

[norm]

I've started experimenting with publishing my recipes on my site — http://marknormanfrancis.com/recipes/chicken-and-chorizo-gumbo

I don't use JSON to store posts, and was pleasantly surprised that just saving the gumbo JSON as TOML worked fine (assert json_object == toml_object). Anyway. If you look at the TOML I'm using for the page you'll see that I am using more keys than were in the original gumbo JSON as part of the recipe, and then some more for the metadata of my publishing system.

Questions:

1. Is Dr Syntax concerned about keys in the data that are unknown?
2. Would Dr Syntax like to adopt prep/cooking time? (now issue Recipe timing #3)
3. Would Dr Syntax like to adopt an introduction/description key? (and maybe footer/postscript) (now issue Recipe descriptions #4)
4. Dr Syntax states "Media files are referenced..." but is silent about how. Would Dr Syntax care to elaborate? (now issue Media files #5)
5. Was Dr Syntax planning on making a real URL for the schema at all? (nb I am now listening to the Dr Horrible soundtrack, so that's fine) (now issue Schema #6)

[norm]

I have moved Qs 2 through 5 into separate issues.

[jaylett]

I have consulted Dr. Syntax, and he would have me convey that:

1. Dr. Syntax be henceforth the name of the object model and related recommendations;
2. syntax.json be the name of the serialisation to JSON; syntax.toml likewise for TOML; and so on and so forth in that fashion;
3. the object model never discuss unknown keys, so they should be considered a free for all with a warning that future revisions of Dr. Syntax might standardise the use of one or more of them in a way that doesn't match private use, but that this is other people's problems — there is no explicit extension model;
4. he welcomes pull requests.

[norm]

I shall endeavour to author a pull request or two on Monday then. 😀