Why would there? They're different (competing) schemas. I certainly like this one better since it's simpler and doesn't bog me down in all kinds over un-needed data typing nonsense.
sbwoodside@yahoo.com
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The network effects of something with widespread support should not be underestimated: nobody is ever going to accept XMLResume XML docs in SOAP over HTTP unless it seriously picks up momentum, but they just may accept the HR-XML docs if it gains enough momentum.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Jerimoth project is an open source HR-XML project.
I agree with the previous post about the network effects. IMHO, this is where a resume in xml ought to be fed. Who cares if I can save my resume in 6 formats if a potential employer or job board has to re-process it? Sure, you might put filters on it for different formats such as functional, chronological, or even a story format. But I think the bonus of having my resume in an industry standard format would be a catalyst for more attention. Think... rss icons, etc. Then put a hr-xml icon your resume via your homepage site. Then it might get picked up for some contract via a spider.
I predict a map will be needed between these formats.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It should be possible to write an XSL stylesheet to transform XMLResume into HR-XML. If HR-XML requires additional data, then the XSL would at least take care of most of the work (with some manual data entry required after running the XSL).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
Is there any planned support for the resume XML schema defined by the HR-XML Consortium?
Why would there? They're different (competing) schemas. I certainly like this one better since it's simpler and doesn't bog me down in all kinds over un-needed data typing nonsense.
sbwoodside@yahoo.com
The network effects of something with widespread support should not be underestimated: nobody is ever going to accept XMLResume XML docs in SOAP over HTTP unless it seriously picks up momentum, but they just may accept the HR-XML docs if it gains enough momentum.
Jerimoth project is an open source HR-XML project.
I agree with the previous post about the network effects. IMHO, this is where a resume in xml ought to be fed. Who cares if I can save my resume in 6 formats if a potential employer or job board has to re-process it? Sure, you might put filters on it for different formats such as functional, chronological, or even a story format. But I think the bonus of having my resume in an industry standard format would be a catalyst for more attention. Think... rss icons, etc. Then put a hr-xml icon your resume via your homepage site. Then it might get picked up for some contract via a spider.
I predict a map will be needed between these formats.
It should be possible to write an XSL stylesheet to transform XMLResume into HR-XML. If HR-XML requires additional data, then the XSL would at least take care of most of the work (with some manual data entry required after running the XSL).
"It should be possible to write an XSL stylesheet to transform XMLResume into HR-XML."
Yep, and I have done exactly that. I contributed the code to the HR-XSL project:
http://hr-xsl.sourceforge.net/
Documentation is here:
http://hr-xsl.sourceforge.net/doc/apa.html