job-listing-brainstorming - Revision history

Aaronpk: Replace with {{DISPLAYTITLE:}}

2020-07-18T16:28:37Z

Replace <entry-title> with {{DISPLAYTITLE:}}

← Older revision		Revision as of 16:28, 18 July 2020
Line 1:		Line 1:
	~~<entry-title>~~Job Listing Brainstorming~~</entry-title>~~		{{DISPLAYTITLE:Job Listing Brainstorming}}

	Per the [[process]], this page documents brainstorm proposals for publishing job listings as research towards the development of a [[job-listing]] microformat.		Per the [[process]], this page documents brainstorm proposals for publishing job listings as research towards the development of a [[job-listing]] microformat.

Tantek: header, footer

2012-04-17T15:54:17Z

header, footer

← Older revision		Revision as of 15:54, 17 April 2012
Line 1:		Line 1:
	= Job Listing Brainstorming =		<entry-title>Job Listing Brainstorming</entry-title>

	~~Ideas~~ for a ~~possible~~ [[job-listing]] microformat.		Per the [[process]], this page documents brainstorm proposals for publishing job listings as research towards the development of a [[job-listing]] microformat.

			All proposals should be based upon the research in:
			* [[job-listing-examples]]
			* [[job-listing-formats]]

	== Fields from examples ==		== Fields from examples ==
Line 170:		Line 174:
	I am sorry for my english. I am just pre-intermediate.		I am sorry for my english. I am just pre-intermediate.
	[[User:Juraj\|Juraj Sivak]]		[[User:Juraj\|Juraj Sivak]]

			== see also ==
			* [[job-listing]]
			* [[job-listing-examples]]
			* [[job-listing-formats]]
			* [[job-listing-brainstorming]]

Juraj: /* Juraj Sivak */

2012-03-26T13:08:03Z

Juraj Sivak

← Older revision		Revision as of 13:08, 26 March 2012
Line 158:		Line 158:
	** duration - duration of employment		** duration - duration of employment
	** last-modified - last update		** last-modified - last update
			** requirements
	** requirements ~~- this atribute is used only for clearer structure~~
	*** education-level - education level		*** education-level - education level
	**** scope - scope of education		**** scope - scope of education

Juraj: /* Juraj Sivak */

2012-03-26T12:59:14Z

Juraj Sivak

← Older revision		Revision as of 12:59, 26 March 2012
Line 145:		Line 145:

	== Juraj Sivak ==		== Juraj Sivak ==
	Hi, I am student of Technical University of Kosice, and my theme of final paper is Semantic web - Microformats. Part of my task is to design some kind of microformat. I began to evolve microformat for job offer, regardless of this brainstorming. My proposed scheme of this ~~microformats~~ is as follows:		Hi, I am student of Technical University of Kosice, and my theme of final paper is Semantic web - Microformats. Part of my task is to design some kind of microformat. I began to evolve microformat for job offer, regardless of this brainstorming. My proposed scheme of this microformat is as follows:
	* job-offer		* job-offer
	** employer - name of employer (hCard)		** employer - name of employer (hCard)

Juraj at 12:58, 26 March 2012

2012-03-26T12:58:23Z

← Older revision		Revision as of 12:58, 26 March 2012
Line 143:		Line 143:
	== Jeff Donner ==		== Jeff Donner ==
	For tech jobs at least, it'd be nice to have /graded/ requirements for skills, whether measured in years experience, general goodness, or how important to the position (1-5 say; 5 absolutely required, 1 lightly used, only nice-to-have). Also, Visa requirements (H1B, citizen, green card ...), security clearance, whether remote work is ok. And actually, all of these are applicable to general jobs as well. -- [[User:JeffDonner\|Jeff Donner]]		For tech jobs at least, it'd be nice to have /graded/ requirements for skills, whether measured in years experience, general goodness, or how important to the position (1-5 say; 5 absolutely required, 1 lightly used, only nice-to-have). Also, Visa requirements (H1B, citizen, green card ...), security clearance, whether remote work is ok. And actually, all of these are applicable to general jobs as well. -- [[User:JeffDonner\|Jeff Donner]]

			== Juraj Sivak ==
			Hi, I am student of Technical University of Kosice, and my theme of final paper is Semantic web - Microformats. Part of my task is to design some kind of microformat. I began to evolve microformat for job offer, regardless of this brainstorming. My proposed scheme of this microformats is as follows:
			* job-offer
			** employer - name of employer (hCard)
			** position - Type of job vacancy (ISCO)
			** description - scope of employment
			** salary/wage - sallary or wage
			*** currency
			** adr - locality of job
			** employment - type of employment
			** dtstart - start-date of employment
			** dtend - end-date of employment
			** duration - duration of employment
			** last-modified - last update

			** requirements - this atribute is used only for clearer structure
			*** education-level - education level
			**** scope - scope of education
			*** experience - experiences like PC experience, practice, driving license...
			**** duration/level - duration or level of experience
			*** skill
			**** assumption - assumption like flexibility, communicativeness...
			**** language - language skill
			***** level - level of language skill

			I am sorry for my english. I am just pre-intermediate.
			[[User:Juraj\|Juraj Sivak]]

JeffDonner: Added bit advocating support for finer-grading of how much needed, individual 'skills' are.

2012-01-13T22:15:04Z

Added bit advocating support for finer-grading of how much needed, individual 'skills' are.

← Older revision		Revision as of 22:15, 13 January 2012
Line 140:		Line 140:

	I see the biggest issue with the hlisting format being how to handle: salary, skills, type, industry and application process.		I see the biggest issue with the hlisting format being how to handle: salary, skills, type, industry and application process.

			== Jeff Donner ==
			For tech jobs at least, it'd be nice to have /graded/ requirements for skills, whether measured in years experience, general goodness, or how important to the position (1-5 say; 5 absolutely required, 1 lightly used, only nice-to-have). Also, Visa requirements (H1B, citizen, green card ...), security clearance, whether remote work is ok. And actually, all of these are applicable to general jobs as well. -- [[User:JeffDonner\|Jeff Donner]]

JeffDonner: removed one 'required' entry - there were two.

2012-01-13T21:57:40Z

removed one 'required' entry - there were two.

← Older revision		Revision as of 21:57, 13 January 2012
Line 43:		Line 43:
	\|-		\|-
	\| years \|\| class \|\| \|\|		\| years \|\| class \|\| \|\|
	\|-
	~~\| required \|\| class \|\| \|\|~~
	\|-		\|-
	\| skill \|\| class \|\| management can fall under skill \|\|		\| skill \|\| class \|\| management can fall under skill \|\|

Mspecht: /* Andy Mabbett */

2009-05-16T06:36:16Z

Andy Mabbett

← Older revision		Revision as of 06:36, 16 May 2009
Line 100:		Line 100:
	**I disagree, "vacancy" has no context. It could refer to anything - eg "hotel vacancy". - Quint		**I disagree, "vacancy" has no context. It could refer to anything - eg "hotel vacancy". - Quint
	***In which case, "job-vacancy" or just "job"? [[User:AndyMabbett\|Andy Mabbett]]		***In which case, "job-vacancy" or just "job"? [[User:AndyMabbett\|Andy Mabbett]]
	**** A job is a offering to the market for someone to fill so using the 3 attributes from the hlisting spec Listing Type="Offer", Listing Action = "Announce" and Item Type ="Opening" describe a job opening. [[User:~~MichaelSpecht~~\|Michael Specht]]		**** A job is a offering to the market for someone to fill so using the 3 attributes from the hlisting spec Listing Type="Offer", Listing Action = "Announce" and Item Type ="Opening" describe a job opening. [[User:Mspecht\|Michael Specht]]


	==Christian Pfetzing==		==Christian Pfetzing==

Mspecht at 06:35, 16 May 2009

2009-05-16T06:35:23Z

← Older revision		Revision as of 06:35, 16 May 2009
Line 100:		Line 100:
	**I disagree, "vacancy" has no context. It could refer to anything - eg "hotel vacancy". - Quint		**I disagree, "vacancy" has no context. It could refer to anything - eg "hotel vacancy". - Quint
	***In which case, "job-vacancy" or just "job"? [[User:AndyMabbett\|Andy Mabbett]]		***In which case, "job-vacancy" or just "job"? [[User:AndyMabbett\|Andy Mabbett]]
			**** A job is a offering to the market for someone to fill so using the 3 attributes from the hlisting spec Listing Type="Offer", Listing Action = "Announce" and Item Type ="Opening" describe a job opening. [[User:MichaelSpecht\|Michael Specht]]


Line 137:		Line 138:
	* One last suggestion is to add "experience" to the list Filip posted above		* One last suggestion is to add "experience" to the list Filip posted above
	** While many job listers search for skills and education level, number of years experience are also used at least as often		** While many job listers search for skills and education level, number of years experience are also used at least as often

			==Michael Specht==
			Agree the hlisting format looks like it could easily be extended to meet the initial needs of a job posting, assuming we look at a job posting as a classified ad not from the view point of a recruiter. One of the issues that limited the take up of HRXML in the early days was it's complexity, experienced gained here in Australia trying to get vendors to support the format. The list of elements above seems to describe a job from an HR/recruitment point of view not a classifieds point of view.

			I see the biggest issue with the hlisting format being how to handle: salary, skills, type, industry and application process.

Brian: Reverted edits by AceloLodom (Talk) to last version by Brian

2009-01-03T19:25:03Z

Reverted edits by AceloLodom (Talk) to last version by Brian

← Older revision		Revision as of 19:25, 3 January 2009
Line 1:		Line 1:
	~~cororolletoa~~
	= Job Listing Brainstorming =		= Job Listing Brainstorming =