Community effort to improve JSON Logic compatibility and provide a formal specification #47
Description
Hey folks!
I'm opening an issue here to draw attention to a community effort to consolidate behaviors in JSON Logic and improve library compatibility, as well as address common complications folks encounter when using JSON Logic.
A GitHub Organization has been created here - https://github.com/json-logic with some information about the objective of the initiative
To get folks caught up, here are links to some of the outreach efforts:
A ton of conversation took place here:
(And thanks for your response @jwadhams!)
Some of the other conversations:
- Checking on Maintenance / Would you be interested in contributing to a spec? panzi/panzi-json-logic#1 (Python + C)
- Would you be interested in collaborating to develop a JSON Logic Specification? Viicos/jsonlogic#34 (Python)
- Discrepency compared to https://jsonlogic.com/play.html json-everything/json-everything#820 (C# -- I kinda hijacked an issue to discuss the possibility of working together)
- Some Non-Standard Recommendations & Request to Collaborate GoPlasmatic/datalogic-rs#3 (Rust)
No response (at the time of linking):
- Checking on Maintenance / Would you be interested in contributing to a spec? allegro/json-logic-kmp#127 (JVM + Swift, written in Kotlin Multiplatform)
- Checking on Maintenance / Would you be interested in contributing to a spec? useful-libs/json_logic_ruby#22 (Ruby)
All are encouraged to be participate in the initiative. I'll try to follow up with other JSON Logic project maintainers.
If I've missed your project, or you're interested in potentially adopting an unmaintained project / contributing to this effort, please feel free to either add a comment to this issue or post a discussion on the org.