Hello there,
I like your standardization of recipes so far and have seen much potential for it. I do have some questions though:
How should a ORF file be identified? Say I have multiple yaml / json files with different contents (like other standards which also use JSON / YAML) or even multiple ORFs in one file, parsing each recipe to see if it is indeed of the format is slow.
Additionally, I don't see how versions of this Standard can be differentiated? Is backwards compatibility always kept, meaning for example there won't be made fields required which weren't before? A version or doc_type field for this purpose would be appreciated.
Another Problem I noticed, is that Text can be written in different languages. To localize recipes, a Language field would therefore be nice.
There also has not been any change to the spec in a lot of time. Will this standard be maintained in the future?
Thanks in advance,
Matthias
Hello there,
I like your standardization of recipes so far and have seen much potential for it. I do have some questions though:
How should a ORF file be identified? Say I have multiple yaml / json files with different contents (like other standards which also use JSON / YAML) or even multiple ORFs in one file, parsing each recipe to see if it is indeed of the format is slow.
Additionally, I don't see how versions of this Standard can be differentiated? Is backwards compatibility always kept, meaning for example there won't be made fields required which weren't before? A version or doc_type field for this purpose would be appreciated.
Another Problem I noticed, is that Text can be written in different languages. To localize recipes, a Language field would therefore be nice.
There also has not been any change to the spec in a lot of time. Will this standard be maintained in the future?
Thanks in advance,
Matthias