Add JSON Schema for more universal spec

[SelfhostedPro]

Hey, currently the way the spec is defined, it makes it difficult to work with automated tooling outside of PHP.

It would be a very nice plus if there was a JSON Schema as it's widely used and there are lots of tools for using it:
Docs: https://json-schema.org/overview/what-is-jsonschema
Tools: https://json-schema.org/tools

I would be happy to help if needed, just let me know. I am really appreciative that there are any docs at all on this.

[SelfhostedPro]

I was also looking and don’t see anything about which type of program the meeting belongs to in the spec. (ie. AA, NA, CA, etc. ) I definitely understand the primary focus of this being AA but was wondering if there are any proposals floating around for a field like that so it could be utilized by other 12 step programs?

My main use case is building a website for an Alano Club (ideally a reusable nuxt template any club can use).

If you would like to communicate about this elsewhere please let me know as I have a discord for my other projects and am working on joining the AA tech forum.

[joshreisner]

hello, if i'm understanding this correctly, a JSON schema would define the spec in a specific JSON format?

i don't see a reason we can't do that, especially if we can use it to generate the Field Definitions section of our README. would that document live here in this repository?

this spec is sometimes used by programs other than AA when they use our WordPress plugin. we don't have a use-case where we mix program meetings in the same feed, but if you wanted to do that you could add a program key for that?

we could also add a program key as part of the formal definition - i think our reluctance has been not wanting to also define all the types for those programs, but it's something we can discuss internally. if you'd like to join us our next meeting will be on December 14 - send an email to info@code4recovery.org

[SelfhostedPro]

Yeah, it essentially would allow specifying it once in this format as a source of truth and then generating from that wherever else you’d want to use it. (Kind of like an OpenAI spec if you’ve used them before)
(ie. For PHP: https://dev.to/robertobutti/validating-json-with-json-schema-and-php-2b4i)

It would likely fit best here.

I don’t think it’s super necessary to add a program key yet, just makes my one specific use case easier. I definitely understand not wanting to step on their toes about it.

I’ll shoot an email over shortly. Thanks for getting back to me!

In the meantime, is there a specific file that has a full overview of the current spec that’s typed or should I piece it together from the readme?

[joshreisner]

the readme section called Field Definitions is a complete definition, so it should have what you need