Difference between revisions of "Talk:PropertyUsageSorted"

From Openresearch
Jump to: navigation, search
(Venue: new section)
 
(13 intermediate revisions by 3 users not shown)
Line 2: Line 2:
 
==Goal==
 
==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
 
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==
+
==To Discuss==
 
* all the one we need are tagged with [[Priority_Milestone::iteration 2]]
 
* all the one we need are tagged with [[Priority_Milestone::iteration 2]]
* meta-properties are tagged with [[isA::Meta-Property|meta-property]] instead of just [[isA::Property]] is this ok? (e.g. https://www.openresearch.org/wiki/Property:Usage_obligation)
+
** this might need to be stored in a different property as iteration 2 is not  really appropriate
 +
* meta-properties are tagged with [[isA::Meta-Property|meta-property]] instead of just [[isA::Property]] (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
 
* 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
+
** we shouldn't keep superproperties --> we need a technical descision wrt that
 +
*** flatten out properties (e.g. the venue of an event)
 +
* 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
 
** Event type ist tagged with iteration 1 the other with iteration 2 so far
*** this might need
+
*** Event Type will be dealt with see ticket... - it will probably only show up in the Form/Template but might not be reflected in the data for the presentation
* we shouldn't keep superproperties --> we need a technical descision wrt that
+
* venue should be an entity just like city, region and country
** flatten out properties (e.g. the venue of an event)
+
** we can thus define the range of [[Property:Has_coordinates]] & [[Property:Has_location_address]] to the [[Concept:Venue]]
 +
 
 +
== TODO ==
 +
Create OpenRefine Project with iteration 1 and iteration2 properties.
  
 
== Venue ==
 
== Venue ==
Line 20: Line 26:
  
 
https://www.rsc.org/events/detail/42460/acs-medi-37th-national-medicinal-chemistry-symposium
 
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: http://diagrams.bitplan.com/render/png/0xe944df63.png
 +
=== inheritance ===
 +
inheritance example: http://diagrams.bitplan.com/render/png/0xb823fb19.png
 +
 +
== 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.
 +
 +
Currently all red links can be found here: https://www.openresearch.org/wiki/Special:WantedPages
 +
 +
== IDs versus Entities ==
 +
 +
Person related data shall not be stored visibily in the OPENRSEARCH LTS.
 +
Ids (ORCIDs) and links/urls might be used instead.

Latest revision as of 12:43, 19 March 2021

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
    • this might need to be stored in a different property as iteration 2 is not really appropriate
  • meta-properties are tagged with meta-property instead of just Property (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
    • we shouldn't keep superproperties --> we need a technical descision wrt that
      • flatten out properties (e.g. the venue of an event)
  • 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
      • Event Type will be dealt with see ticket... - it will probably only show up in the Form/Template but might not be reflected in the data for the presentation
  • venue should be an entity just like city, region and country

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: 0xe944df63.png

inheritance

inheritance example: 0xb823fb19.png

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.

Currently all red links can be found here: https://www.openresearch.org/wiki/Special:WantedPages

IDs versus Entities

Person related data shall not be stored visibily in the OPENRSEARCH LTS. Ids (ORCIDs) and links/urls might be used instead.