I still need to investigate if this approach makes sense, but given that YAPP's JSON output is mainly used for MODAQ and not on a standard, it seems like we can change the format to support new features
Ideas that will be in a new version:
Versioning: old YAPP JSON files will implicitly be version 1. New ones will have a version or v numeric field that represents the version of the format
Scoped pronunciation guides
I'm leaning towards something like [words to pronounce](were-dis to pro-now-ounce) to mark which words are scoped to a pronunciation guide
Parsed answerlines - break down what is accepted, what is promptable and not promptable
Could replace the answer field with an object for each type (accepted, prompt, do_not_prompt, anti_prompt etc.)
Other possibilities:
Changing field names to be 1-2 characters to save space
Tossup question text is split into arrays of parts for packets that use powers
This could either replace the standard question or be in addition to it, though the latter means that there's some duplication of data
Use Markdown style formatting instead of HTML: ** for bold, _ for italics, etc. This saves some space since it's 2-4 characters for formatting instead of 7.
This needs more details before it can be implemented.
I still need to investigate if this approach makes sense, but given that YAPP's JSON output is mainly used for MODAQ and not on a standard, it seems like we can change the format to support new features
Ideas that will be in a new version:
versionorvnumeric field that represents the version of the format[words to pronounce](were-dis to pro-now-ounce)to mark which words are scoped to a pronunciation guideanswerfield with an object for each type (accepted, prompt, do_not_prompt, anti_prompt etc.)Other possibilities:
This needs more details before it can be implemented.