Skip to content
This repository has been archived by the owner on Mar 19, 2019. It is now read-only.

Refactor thinking on the IETF #130

Closed
lorenzogrv opened this issue May 28, 2014 · 6 comments
Closed

Refactor thinking on the IETF #130

lorenzogrv opened this issue May 28, 2014 · 6 comments

Comments

@lorenzogrv
Copy link

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.

@geraintluff
Copy link
Member

We are indeed hoping to head towards IETF standardisation.

I've been seeking guidance from someone I work with, who is very involved with IETF process (chairing groups, organising BOFs, etc.) as to how JSON Schema can most effectively head towards standardisation.

I have some WIP drafts for the v5 spec, but was going through a busy period so they didn't get close enough to start reviewing them. Francis has kindly returned, so (hopefully soon) I can send him what I have and we can move forward from there.

@gjermundgaraba
Copy link

Year later. Has much happened?

@akuckartz
Copy link

Meanwhile JSON-LD has become a (W3C-) standard...

@hugovincent
Copy link

@geraintluff how is draft-5 coming along?

@handrews
Copy link

@laconbass @bjaanes @akuckartz @hugovincent
New IETF drafts have been submitted by @awwright
New spec work is going on here: https://github.com/json-schema-org/json-schema-spec
Could you please close this issue? We no longer have permissions to this repo.

https://tools.ietf.org/html/draft-wright-json-schema-00
https://tools.ietf.org/html/draft-wright-json-schema-validation-00
https://tools.ietf.org/html/draft-wright-json-schema-hyperschema-00

(minor revision to Draft 04, with a more substantial update in active discussion at the new repo)

@lorenzogrv
Copy link
Author

Closing this issue as requested by @handrews, future readers: please follow to https://github.com/json-schema-org/

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants