remodel-and/or-suppress subclasses of foaf:person by fully exploiting profiles instead

[spitxa]

as suggested by 1 reviewer, some classes recycled from the vivo ontology (i.e. student and subclasses) would be better modelled through profiles & roles. in a subsequent move, this might also be applied to the entire list of 'human resource' subclasses ('administrative personnel, teaching and research personnel', etc.), although some nuances regarding these subclasses must be taken into account, bearing in mind the alignment with the ad-hoc vertical module ('spanish university human resource').

[spitxa]

done: -classes already modelled and added to the core (also committed), including pivotal comments and also labels in english; object and data properties also determined & committed (including comments & labels in english).

to be done: -property "requires" conflicts the one exploitable already existing; domains and ranges conflict as well. -adapting/converting classes 'students' & 'human resource' to the new roles&profiles model

[spitxa]

done: -adapting/converting classes 'students' & 'human resource' to the new roles&profiles model

to be done: -property "requires" conflicts the one exploitable already existing; domains and ranges conflict as well. -removing HR as classes force us to create instances of class 'role' instead. these instances are not exactly testing 'individuals' but instances belonging to the ontology. this (good, bad?) practice must be checked out in the ontology desing patterns portal.

[spitxa]

to be done: -enriching the instances corrresponding to roles so to include the ones relevant to the competences questions (postdoc researcher, etc.)