We should stick with Employee. The actual and planned employee should be handled by dated effectivity on the person org assignment. Otherwise we would have to change the underlying data everytime the empoyee changed job.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Employee is probably a subclass of person but isn't it employment that is the interesting concept.
Employment is likely a valid classification of the relationship between a person and (a position in) an organization (i.e. the 'person-in-organization-assignment'). It is the employment that has a start and a end date (i.e. a dated effectivity.
Från: Rob Bodington [mailto:robbod@users.sf.net]
Skickat: den 10 oktober 2016 18:24
Till: [plcslib:plcs-ref-data]
Ämne: [plcslib:plcs-ref-data] Re: #459 plcs-psm-en.owl Employee
We should stick with Employee. The actual and planned employee should be handled by dated effectivity on the person org assignment. Otherwise we would have to change the underlying data everytime the empoyee changed job.
Status: open
Group: plcs-plcslib-v1.0-csprd02
Created: Wed Mar 05, 2014 04:31 PM UTC by willliam bowland
Last Updated: Fri Aug 22, 2014 01:55 PM UTC
Owner: nobody
Employee should be added as a subclass of PersonInOrganization.
Agree - the proposal is to classify PersonInOrganization - the relationship between a person and an organization so we should call the class Employment
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Please suggest a definition for the class, and possibly comments and examples.
Regards,
Mats
Perhaps that should be Actual_employee and Planned_employee.
The OED definition is:
A person who works for an employer; spec. a person employed for wages or a salary under an employment contract,
We should stick with Employee. The actual and planned employee should be handled by dated effectivity on the person org assignment. Otherwise we would have to change the underlying data everytime the empoyee changed job.
Employee is probably a subclass of person but isn't it employment that is the interesting concept.
Employment is likely a valid classification of the relationship between a person and (a position in) an organization (i.e. the 'person-in-organization-assignment'). It is the employment that has a start and a end date (i.e. a dated effectivity.
Från: Rob Bodington [mailto:robbod@users.sf.net]
Skickat: den 10 oktober 2016 18:24
Till: [plcslib:plcs-ref-data]
Ämne: [plcslib:plcs-ref-data] Re: #459 plcs-psm-en.owl Employee
We should stick with Employee. The actual and planned employee should be handled by dated effectivity on the person org assignment. Otherwise we would have to change the underlying data everytime the empoyee changed job.
[plcs-ref-data:#459]https://sourceforge.net/p/plcslib/plcs-ref-data/459/ plcs-psm-en.owl Employee
Status: open
Group: plcs-plcslib-v1.0-csprd02
Created: Wed Mar 05, 2014 04:31 PM UTC by willliam bowland
Last Updated: Fri Aug 22, 2014 01:55 PM UTC
Owner: nobody
Employee should be added as a subclass of PersonInOrganization.
Sent from sourceforge.net because you indicated interest in https://sourceforge.net/p/plcslib/plcs-ref-data/459/
To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/
Related
PLCS Ref. data: #459
Agree - the proposal is to classify PersonInOrganization - the relationship between a person and an organization so we should call the class Employment
added to:
plcslib/data/contexts/OASIS/refdata/plcs-rdl-en-v1_1.owl revision: 1.32