Refactor thinking on the IETF #130
Description
I've been reading the last · drafts · on the IETF site, and I felt sad whe I saw how outdated they are.
Is JSON Schema dead?, asked myself. Fortunately I ended up reading things that lead me here, to our beloved github 😄, and I see that it's not dead.
Reading the words of F. Galiege, It seems that was frustrating the path of writting, reviewing, and refactoring that drafts, specially for the bad - either unexistent - feedback. Am I wrong? If so, correct me please.
While comparing the text of the last core draft with other json-related drafts, I've found many things that, IMHO:
- could be refactored to meet the technical style of the IETF; and
- could be refactored to demonstrate the utility of such an spec;
It's clear enough for me, as I work everyday with node.js, that having a JSON based tool for data validation that I can reuse both on backend and frontend is for sure a good thing. I'm lucky cause such a tool already exist, so I wonder if it could be effectively adopted as standard because if it has been living - and growing - on the wild, is because the community likes it.
I like the work you are putting here, so I would like to help refactoring that IETF draft and see if together we can get over the red line of the internet standards experts, and build a standard spec together.
I don't know if this team has plan on continuing the path to that standard spec, so that's obviously the first question I need feedback from you 😆
Keep up the good work,
L.