Re: [TalentSignal] total job openings

Hi, PhilThis is great and simple, quick win as you mentioned in the other thread. A few comments/questions:
- Do we need to be even tighter on the expected range? Will we expect or allow negative numbers? Is a value of 0 acceptable or must it be >=1 if the property is used? - Do we need to add to the definition what to do if the actual number is unknown? i.e. "totalJobOpenings: Number of positions open for this job posting. If the number of positions is unclear or not known, do not include this property."
Best regardsAndrew.


Andrew CunsoloVP Product Management, Talemetry Inc.

    On Thursday, August 22, 2019, 11:15:25 a.m. EDT, Phil Barker <phil.barker@pjjk.co.uk> wrote:  
 
   
Hello all, new topic: total job openings, I am hoping that this is straightforward.
 
JDX JobSchema+ has a property for when a JobPosting has more than one vacancy/opening, schema.org JobPosting doesn't [1]. This seems significant, it's often worth knowing whether there are 50 new vacancies or just one. So I think we should suggest to schema.org that they add the property :
 
totalJobOpenings: Number of positions open for this job posting.
 
expected domain: JobPosting
 
expected range: Integer [don't use fractions to describe part-time openings; two 50%FTE does not equal one opening!]
 
 
OK?
 
 
Phil
 
 

 
 
1. https://www.w3.org/community/talent-signal/wiki/Comparison_of_JDX_JobSchema%2B_with_schema.org
 -- 
 
Phil Barker. http://people.pjjk.net/phil
 CETIS LLP: a cooperative consultancy for innovation in education technology.
 PJJK Limited: 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.