Re: [TalentSignal] proposal for Job Start Date

I am on board with this. I think it solves my original concerns.

Thanks,
Jason

From: Phil Barker <phil.barker@pjjk.co.uk>
Date: Monday, May 6, 2019 at 6:12 AM
To: "public-talent-signal@w3.org" <public-talent-signal@w3.org>
Subject: Re: [TalentSignal] proposal for Job Start Date
Resent-From: <public-talent-signal@w3.org>
Resent-Date: Monday, May 6, 2019 at 6:13 AM


Hello all.

Following the discussions last week and the suggestion from Anderw Cunsolo, I have redrafted the proposal on the wiki. It now reads:

jobStartDate
Definition: The date on which a successful applicant for this job would be expected to start work. Choose a specific date in the future or use the jobImmediateStart property to indicate the position is to be filled as soon as possible.
Expected type: ISO 8601 Date<https://schema.org/Date>

jobImmediateStart
Defintion: An indicator as to whether a position is available for an immediate start.
Expected type: Boolean<https://schema.org/Boolean>

(I added the hint to "use the jobImmediateStart property to indicate the position is to be filled as soon as possible" to steer people away from using text in what I think will be the most common scenario for that.)

Please think through how this would work for real-world examples and let me know of any comments. I will work up the pull request to submit via the schema.org github repo, hopefully at the end of this week.

Phil


On 02/05/2019 16:02, Phil Barker wrote:

Hello all, the second relatively simple issue that we prioritized, is that currently schema.org/JobPosting has no way to specify the expected start date for the job being advertised.

A simple way to fix this<https://www.w3.org/community/talent-signal/wiki/Provide_start_date_for_job> is a new property of JobPosting:

jobStartDate

Definition: The date on which a successful applicant for this job would be expected to start work. Text values such as "Immediately" or "As soon as possible" may be used when a specific date is not appropriate.

Expected type: ISO 8601 Date<https://schema.org/Date> or Text<https://schema.org/Text>



Please let me know if you wish to improve on this or have an alternative suggestion. In particular, is a text value to indicate an immediate start sufficient, or should this be handled more explicitly, for example as a separate property?

On that question, my own view (as exemplified in the proposal) is that, while an explicit indicator for immediate start may be useful for internal systems, a text value is adequate for advertising this on the web. If experience and demand show that this approach is not adequate, we would have evidence to provide to schema.org for a separate, explicit property.

Regards, Phil.
--

Phil Barker<http://people.pjjk.net/phil>. http://people.pjjk.net/phil

CETIS LLP<https://www.cetis.org.uk>: a cooperative consultancy for innovation in education technology.
PJJK Limited<https://www.pjjk.co.uk>: technology to enhance learning; information systems for education.

CETIS is a co-operative limited liability partnership, registered in England number OC399090
PJJK Limited is registered in Scotland as a private limited company, number SC569282.
--

Phil Barker<http://people.pjjk.net/phil>. http://people.pjjk.net/phil

CETIS LLP<https://www.cetis.org.uk>: a cooperative consultancy for innovation in education technology.
PJJK Limited<https://www.pjjk.co.uk>: technology to enhance learning; information systems for education.

CETIS is a co-operative limited liability partnership, registered in England number OC399090
PJJK Limited is registered in Scotland as a private limited company, number SC569282.