[XML-DEV Mailing List Archive Home]
[Reply To This Message]
- From: "=?utf-8?B?UmFuZCBNY1JhbmRlcnNvbg==?=" <firstname.lastname@example.org>
- To: "=?utf-8?B?RGF2aWQgTGVl?=" <email@example.com>,stephengreenubl@g...,"=?utf-8?B?J0xlY2ggUnplZHppY2tpJw==?=" <xchaotic@g...>
- Date: Sat, 25 Jun 2011 12:20:37 -0400
|Let me throw out a use case from myself as an applicant. When I search for a job I load up a shotgun and apply everywhere. |
However, this means filling out dozens of online forms asking for the same things. Job search sites, recruiting firms and large corporations all want machine-readable personal information, job history, and a skill list for their database. Some sites I know are willing to let you copy and paste into a form your resume and then try to parse it by guessing the format.
It would be beautiful to fill out a form once, download the xml and then upload it everywhere and know for sure that the information is correctly proccessed.
I'm not sure firms would necessarily need this (except perhaps very large organizations where different divisions that need to exchange personnel info have different technology stacks (like the US government), or during a firm's data migration). Those two uses aren't irrelevant, data migration is always a nightmare and technology stacks do change, but they are somewhat rare cases.
However, for recruiting companies/large corporations I would think making it easier for applicants to apply is its own reward. Monster.com doesn't advertise because it dislikes people making accounts, and the chore of filling out forms has actively discouraged me from creating a profile at some sites before.
I've been a recruiter (in my dark past) and worked with many recruiters and companies.
Not once has anyone ever asked for or been willing to accept XML formatted resumes from candidates.
The current standard is Doc , PDF and HTML.
Each shop tends to have its own database format (there's lots ...) ... in the dark past resumes were scanned or faxed then OCR'd into the DB. Later they started being able to import text formats (which is why even today Doc or HTML is preferable to PDF because it can import more easily into whatever format the recruiter/HR is using internally).
If you want a resume in XML as the source (great !) pick or invent a schema that can format to one of the above easily. I would then ask the recipient on a case by case basis what format they prefer and send them that format. The less work they have to do, the more you are in charge of conversion and less chance of errors. Plus it puts HR in a better mood if they don't have to work to convert your "strange" format.
David A. Lee
From: Stephen D Green [mailto:stephengreenubl@g...]
Sent: Friday, June 24, 2011 8:45 AM
To: Lech Rzedzicki
Subject: Re: getting started with HR-XML
I reckon XML is proven to be useful between businesses for transferring lots
of data, frequently, but I cannot think of any cases where it has proven to be
worth the overheads for small, one-off documents or messages between, say,
an individual and a business (even one individual many businesses, when
for each business the is just one transfer). i.e. XML seems to be great B2B
(or application to application) but perhaps is unproven for B2C.
On 24 June 2011 04:20, Lech Rzedzicki <xchaotic@g...> wrote:
I am having another look at status quo in keeping ones professional/career information and revisiting the schemas after a few years.
XMLResume, while more lightweight seems pretty dead to me and in a way it's not only bad as it's better to have one standard in a given area of expertise.
The winner, HR-XML leaves a lot to be desired when it comes to openness and community support, but the schemas themselves are free.
Over the years the schemas have grown a lot in complexity and include transaction and all the backend specific to HR.
I am, for now set on converting my resume to HR-XML, but I am a bit puzzled as to how to approach it, the schema, as you download it, contains a mere 5600 files.
Still, I am guessing that I might want to use /HR-XML-3_1_1/org_hr-xml/3_1_1/Developer/Nouns/Candidate.xsd
I tried a simple instance and it validates, but now I am a bit puzzled.
Is it really going to be that useful as an interchange standard? I have yet to see a end worker facing job site that accepts CVs in HR-XML (all 7 of them).
If all I get is an ability to publish cross-media (PDF, HTML, doc), I was doing just fine with Word, to be honest.
Does anyone here have any recent experience with the standard or is involved with hr-xml community?
If so is this the right approach that one should take towards writing a resume?
Are there any plans to release a simplified schema, just to cover the needs of the end users who need to write/update their CV/resume?
| [Thread Prev]
| [Thread Next]
| [Date Next]
| [Thread Index]
PURCHASE STYLUS STUDIO ONLINE TODAY!
Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!
Download The World's Best XML IDE!
Accelerate XML development with our award-winning XML IDE - Download a free trial today!
Subscribe in XML format
Stylus Studio has published XML-DEV in RSS and ATOM formats,
enabling users to easily subcribe to the list from their preferred news reader application.
Stylus Studio Sponsored Links are added links designed to provide related and additional information to the visitors of this website.
they were not included by the author in the initial post. To view the content without the Sponsor Links please