Why isn't there a universal data format for résumés?
21–30 of 472 posts
Re: Why isn't there a universal data format for résumés?
#22But 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.)
Re: Why isn't there a universal data format for résumés?
#23Re: Why isn't there a universal data format for résumés?
#24Does the author want the resume to be objectively judged? Maybe not
Re: Why isn't there a universal data format for résumés?
#25The reason the author is trapped long enough in meat grinder hiring to notice this "problem" is likely precisely because of some indistinguishable cookie cutter bullet point soup getting them nowhere. If you can capture it in a data structure, it's not a resume!
See also: why isn't there a universal UI for web sites?
Re: Why isn't there a universal data format for résumés?
#26Why should there be? Resumes have to be read by humans to judge if they match what is needed. Checking boxes and matching buzzwords only gets you so far.
It's not like people are managing dozens/hundreds of candidates with a pen/paper.
There is definitely a need for a standard format.
Re: Why isn't there a universal data format for résumés?
#27Re: Why isn't there a universal data format for résumés?
#28Re: Why isn't there a universal data format for résumés?
#29There is, thanks to the semantic web (the real web 3 :) ). See for example the FoaF ontology https://en.wikipedia.org/wiki/FOAF_(ontology)
Some of these old AAA XHTML 1.1+RDFa websites were well engineered and a joy for both man and machine to behold.