Awesome idea. I could imagine a marketplace for resume themes that is based on this. Would be easy to switch between different designs to see consistent details.
Isn't the look of your resume one of your competitive advantages as job-seeker?
Sorry I really don't understand the use-case. Having an API is good for styling (as you say), or doing some soft of programmatic transformation to data. I am having trouble understanding the need to do either for a resume.
Maybe it would help as metadata for a search engine, but in that case I think a plain text search would be just as effective?
I think json schema is a really nice thing to have and I'd like to see more people adopt it, but I'm having trouble coming up with the point for this use.
Came here to say this. I feel the same way — even about the schema. Having a poorly-organized or thought out resume should be an immediate signal to employers. This eliminates that.
Of course, this is not to imply that having a really well-done resume is really worth much either.
I've actually written my resume in markup for a while just so that I could put it on a nice dynamically driven site. Sort of a fun weekend project (no, it's not hosted anywhere).
While I strongly doubt that this will ever be a standard, I think it's nifty, and potentially useful. It opens up easy, pretty resumes, which the world really needs (Note: I'm not being sarcastic. The number of mountains-of-text word document resumes I've gotten in the past few weeks is too high).
> It opens up easy, pretty resumes, which the world really needs
People have been doing XML+XSLT for their resumes for a long time, yet it really hasn't taken off in a standard way for whatever reason. Not sure this being JSON-based will change that. I guess I'm wondering what this solution brings to the table that previous attempts didn't.
Well done.