W3C home > Mailing lists > Public > public-vocabs@w3.org > September 2014

Re: Person job proposal (was Re: Schema.org proposal: Financial information)

From: Jarno van Driel <jarnovandriel@gmail.com>
Date: Wed, 17 Sep 2014 18:52:55 +0200
Message-ID: <CADK2AU0kX72Une4QTjuSyj0z-1SejSjt-qYEu-hq+24cdjWkXg@mail.gmail.com>
To: Vicki Tardif Holland <vtardif@google.com>
Cc: ☮ elf Pavlik ☮ <perpetual-tripper@wwelves.org>, PublicVocabs <public-vocabs@w3.org>
eh, is this thread of a different nature than the one I already started?
(http://lists.w3.org/Archives/Public/public-vocabs/2014Sep/0126.html)

2014-09-17 18:33 GMT+02:00 Vicki Tardif Holland <vtardif@google.com>:

> I propose 5 properties and the mailing list goes nuts! ;-)
>
> I am starting to lose track of the discussion, which has forked between
> personal financial info and corporate information, so I am going to reply
> to the comments regarding Person here and start another thread for
> organizations.
>
> As some have pointed out, Occupation and Job are slightly different. My
> occupation may be the same across employers, where as my job is not.
>
> I like the idea of having a "EmployeeRole" to model salary, title,
> employer, and tenure. Authors would then use the worksFor property to link
> this information to a Person.
>
>
> - Vicki
>
> Vicki Tardif Holland | Ontologist | vtardif@google.com
>
>
> On Tue, Sep 16, 2014 at 3:08 PM, ☮ elf Pavlik ☮ <
> perpetual-tripper@wwelves.org> wrote:
>
>> On 09/16/2014 08:04 PM, Vicki Tardif Holland wrote:
>> > Please see the attached proposal for describing financial information
>> > for individuals and organizations. I am aware that financial information
>> > can get very complex very fast. I am hoping to add the following
>> properties:
>> [...]
>> > And extend the domain for:
>> > baseSalary
>> > salaryCurrency
>>
>> IMO those two properties pollute already bloated schema:Person
>>
>> how about reusing 'Qualified Relation' pattern[1] used for schema:Role ?
>> http://blog.schema.org/2014/06/introducing-role.html
>>
>> Person --{worksFor}--> Role --{worksFor}--> Organization
>>                             --{baseSalary}-->PriceSpecification
>>
>>
>> i see it much more realistic while more and more people work on various
>> projects (or have jobs) in parallel and modeling proposed in attached
>> pdf seems not accounting for it and assuming that person has only one
>> job or one 'main job'
>>
>> [1] http://patterns.dataincubator.org/book/qualified-relation.html
>>
>
>
Received on Wednesday, 17 September 2014 16:53:22 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:29:44 UTC