Difference between revisions of "Talk:PropertyUsageSorted"
(→TO Discuss) |
|||
Line 11: | Line 11: | ||
* we shouldn't keep superproperties --> we need a technical descision wrt that | * we shouldn't keep superproperties --> we need a technical descision wrt that | ||
** flatten out properties (e.g. the venue of an event) | ** flatten out properties (e.g. the venue of an event) | ||
+ | * venue should be an entity just like city, region and country | ||
+ | ** we can thus define the range of [[Has_coordinates]] to the [[Concept:Venue]] | ||
+ | |||
== TODO == | == TODO == | ||
Create OpenRefine Project with iteration 1 and iteration2 properties. | Create OpenRefine Project with iteration 1 and iteration2 properties. |
Revision as of 11:55, 19 March 2021
Contents
Meeting notes 19.3.2021
Goal
Decision on which properties are also needed for the migration to OR LTS based on https://www.openresearch.org/wiki/PropertyUsageSorted & https://www.openresearch.org/wiki/Iteration1_Property_Mapping
TO Discuss
- all the one we need are tagged with iteration 2
- meta-properties are tagged with meta-property instead of just Property is this ok? (e.g. https://www.openresearch.org/wiki/Property:Usage_obligation)
- Property:Has person = superproperty of board members etc → do we take this one or only the fine grained ones
- how to deal with the ones I set up (e.g. Event type) that are not used yet but needed for DOI registration or ConfIDent
- Event type ist tagged with iteration 1 the other with iteration 2 so far
- this might need
- Event type ist tagged with iteration 1 the other with iteration 2 so far
- we shouldn't keep superproperties --> we need a technical descision wrt that
- flatten out properties (e.g. the venue of an event)
- venue should be an entity just like city, region and country
- we can thus define the range of Has_coordinates to the Concept:Venue
TODO
Create OpenRefine Project with iteration 1 and iteration2 properties.
Venue
Example: A venue is a location of an event and it basically consists of what https://www.openresearch.org/wiki/Property:Located_in currently has except that the address should be made more specific and e.g. point to an organization:
e.g. Mariott Hotel, Downtown New York, NY, USA
https://www.rsc.org/events/detail/42460/acs-medi-37th-national-medicinal-chemistry-symposium
Inheritance and N:M
The complexity of inheritance and n:M should be avoided if this is motivated by special and exotic cases
N:M
n:m example:
inheritance
inheritance example:
usage versus red links
red links are problematic e.g. for finding out which contributors are organizations and which ones are natural persons. see https://www.openresearch.org/wiki/Property:Has_person There would be an NLP problem for making that decision.
IDs versus Entities
Person related data shall not be stored visibily in the OPENRSEARCH LTS. Ids (ORCIDs) and links/urls might be used instead.