5 ms·
That's not really a "universal format", though. That's an "English language format". Actually, it's an "American format" since I see it specifies "organization"
by freddie_mercury 5y ago
That's not really a "universal format", though. That's an "English language format". Actually, it's an "American format" since I see it specifies "organization" instead of "organisation".
Why should resumes in Vietnam or China be using English, after all.
- berkes 5y agoDoesn't that hold true for any standard though? 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.
- freddie_mercury 5y agoThat's fair point. But normal French people aren't interacting with HTTP directly in any meaningful way. (More snarkily: they're using browsers built by Americans to connect to webservers built by Americans.) But I imagine that 99% of people who use json-resume today are interacting directly with it. 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.
- CalRobert 5y agoThat's true of the fields in the JSON, but for what it's worth you can output your resume in templates for any language you like. I've updated mine to use Hiberno English for instance.