Re: Please add property="skill" to the typeOf="Person"

I agree there's a need to be able to represent skills in schema.org.  To
make the implementation serve the needs of many, I suggest considering the
following:

-- Don't tie skills with job titles.  People can have active skills that
aren't used in their current position (e.g., they are a native speaker of a
language when in a job that doesn't require that language.)  People may
have skills developed or available for volunteer experiences that aren't
formal jobs.
-- People may also have multiple, concurrent, overlapping jobs, rather than
serial jobs with clearly defined start and end dates. Job titles can be a
poor indication of what someone is doing when people are doing multiple
roles at once.  For people with portfolio careers, it makes more sense to
speak of "projects" rather than job titles, with the project involving one
or more roles.
-- Consider a broader category of "expertise" to capture less task-oriented
knowledge.  An academic might have expertise on bond markets or privacy
law, even though they are not a bond trader or a practicing lawyer.

Michael



On Wed, May 3, 2017 at 5:58 AM, Thad Guidry <thadguidry@gmail.com> wrote:

> Please consider...
>
> Lost skills.  Historical skills.  I used to be an aerospace mechanic, I no
> longer have those skills (well a few but many I have forgotten). I am now a
> Data Architect.
> We want to allow for time-mediation of skills as well. And a way for
> someone to say what their "CURRENT" skills are.
>
> "CURRENT" against any particular skill needs to be captured.  This can be
> done with a property called "currentSkills" on Person.
>
> For everything else...What we need is to finish the effort of the existing
> CV/Resume proposal here https://github.com/schemaorg/schemaorg/issues/603
>
> jobTitle
> worksFor
> workLocation
>
> are for "CURRENT" status of a Person.  And I would argue that those need
> to be prefixed with "current" such as "currentJobTitle", etc.
>
> But we also want time-mediation for all of those, not just current...I.E.,
> a history of a persons employment.  That is captured in the proposal above.
> And with that proposal, there would be a "cv/resume" property that expects
> a type of CV/RESUME that can allow for much more flexibility and
> time-mediation.
>
> In fact, time-mediation is needed in a lot of areas of Schema.org.  We
> might even consider some higher level abstraction of time-mediation against
> any particular property when it is needed..  Just as Wikidata and others do.
> But this will need Guha's deep thought processes :)
>
> -Thad
> +ThadGuidry <https://www.google.com/+ThadGuidry>
>
>
> On Wed, May 3, 2017 at 7:54 AM Nicolas Torzec <torzecn@yahoo-inc.com>
> wrote:
>
>> Hi Maxim,
>> I like the idea of adding a 'skill' property to schema.org/Person for
>> capturing Resumes.
>>
>> In addition, you probably want to use a reified version of 'affiliation'
>> and 'alumniOf' so you can use them as *roles* with *startDate* and
>> *endDate*.
>>
>> See http://blog.schema.org/2014/06/introducing-role.html
>>
>> Cheers.
>> N.
>>
>>
>> On Monday, May 1, 2017, 5:24:14 AM PDT, Maxim Angel <
>> maxim_angel@live.co.uk> wrote:
>> Please add property "skill" to "Person" type, so many people want to use
>> schema.org/Person for creating CV
>>
>