Discussion: Standardize spec/conventions?

[alex-c]

Hello, I recently discovered the .cook format and am integrating it into a tool I am building. I am runnint the server in Docker and interacting with the API. I love the whole concept but I came across a few difficulties because of the non-standardized parts, especially the meta data.

For example, according to the conventions, diet can be a single string or an array. Depending which it is, the API will also deliver either a string or an array, which is a problem for me when deserializing to a strongly typed language. The server UI itself also does not handle both, as the diet is displayed as a tag when it's a single string:

But not when it's an array (diet: [Vegan, Vegetrarian]):

There's also several other instances of these multiple possibilities to declare the same metadata: source/author, times, images, etc.

Wouldn't the spec profit from a standardization so that tools can reliably access the important, usualy met data?

Thanks for all the work on cooklang!