But nobody really uses it for data interchange. I use it to render my resume in new layouts now and then.
Although, it does let style dictate content sometimes (some templates force you to have dates down to the day for job start and end dates, etc.)
I think over 3k+ people use the new Gist hosting. (In our old hosting we had around 10k resumes. Not including those who by pass the free community hosting)
===
On a personal note, I've loved having my resume in a standard;
- Depending on what type of company/person I am applying to I will change my theme on the fly. (Startup vibes I will make it look hipster, if it's a more formal role I will use a simple black and white theme)
- I use to lose my most recent resume constantly, having it in a Gist called resume.json that I just edit seems to have solved that for me.
- Hopefully one day a standard will get integration adoption so I can just upload my resume.json and not have to fill out the same form fields a hundred times.
I think we wanted JSON at the time because it just relied on less extra packages when working inside of the JS ecosystem.
So yeah, if anyone wants to make a resume.yaml, we only need to add an extra step to convert it to json for them to use any of the tooling.
As you can imagine, I felt like a clown trying to explain that I didn't have a word document because my resume was generated from a JSON file.
I did, however, have a PDF on a USB drive I always kept on me but they refused to accept USBs out of fear that I was trying to give them a virus. Eventually the lady processing my application gave up and printed the PDF off that was hosted on my website but also scolded me for not having a word doc.
The whole ordeal was pointless anyway since they said they can give me 70% of my rent.
Even if there were a turn-key software platform they all used, which natively supported a standard data format, they'd still find a way to screw it up.
A challenge I see is -- resumes change wildly by industry.
a tech resume is totallly different from an actor's resume.
but I think this complexity can be handled.
I totally support json resumes.
Why should resumes in Vietnam or China be using English, after all.
In HTTP we have Get, Put, Post, Delete, Patch or Options and not obtenir, mettre, poster, supprimer, corriger, options. Yet the French use the web all the time, as do Chinese or Maui.
It would not be about how the fields are named, but about localised concepts. Maybe there are societies that have some educational concept which western Americans cannot fathom, but which is crucial on a CV there.
This,implies the standard needs to be flexible, extensible and localised. Which kindof defeats having a standard.
So I suppose that parallel suggests it depends on whether there's a realistic expectation of WYSIWYG editors for any kind of universal resume format. Which I think seems incredibly unlikely.