ABCDEFGHIJKLMNOPQRSTUVWXYZAA
1
IssueDescriptionPriorityDifficultyCommentExamplesResponsibleResponsible2Priority2Difficulty2Comment2Examples2
2
Relationship should be an occurrent -- a relationship occurs or happens over time. It is currently a specifically dependent continuant. As an occurrent, Relationship can be bounded in time and standard BFO predicates such as “participates in” can be used. Relates and relatedBy can be replaced. See Early Thoughts on Representing Roles and Relationships in VIVO. Relationships involve 2 or more entities, each entity having one or more roles in the relationship. These “mutually dependent” roles are being discussed in the BFO community. The thought is that these roles depend on the relationship. Should the relationship end, the roles end as well.Rolf02 Aug Meetingvery high for implementersImplementers may not be able to migrate their existing customizations and data ingest tooling without
3
Languages are generically dependent continuants. They depend on the collective history and use by human beings for their existence.Rolf
4
Rolf
5
Instants or Intervals are temporal regions as they are now.Rolf
6
Project is an occurrentRolf
7
Event can be a VIVO term. The Event ontology can be retired.High
Should be solved with the Academic Event Ontology - https://github.com/tibonto/aeon
Rolf
8
Service can be a VIVO term. A service is a process. Service as defined in ERO can be retired.Rolf
9
Position is correct as is, a subClass of Relationship. But with the change of Relationship to an Occurrent, Position is an occurrent. A position is a particular type of relationship between a person and an organization.Rolf
10
Grant is an occurrent, a relationship between a research organization and a funder. Typically has a contract and funds one or more projects.Rolf
11
Membership is a relationship between a person and an organization. Typically the person has a member role and the organization has a grantor role.Brian
12
Instrument is piece of equipment used in researchBrian
13
Building is a Material Entity. It is currently a bfo:Site (Immaterial entity). The inside of a building is an immaterial entity. We can consider whether VIVO needs to make this distinction.lowBrian
14
Note: The term “Facility” is not reflected in this early figure. Facility is currently defined as a Site, an Immaterial Entity. Facility appears to be unclear -- is it an organization, a collection of services, a physical building, a collection of instruments? Perhaps all these other things are already represented.Brian
15
Person and Organization are modeled as VIVO terms, not foaf. Foaf can be retired. There may be no need in the ontology for the te “Agent”. Entities either have functions and dispositions reflective of agency, or they do not. In OBI, Person and Organization are material entities.Brian
16
Note: The term “Group” is not reflected in this early figure. Perhaps it is not needed. Groups are informal organizations of people.Brian
17
Document Status and Datetime Precision are Qualities of entities (documents and datetimes respectively).Brian
18
Performance is an occurrent, a subClass of Event. This is new to VIVO, and an important addition. The recording of a performance is a digital artifact, an Information Content Entity. It is about the performance.Brian
19
Course is also an occurrent, a subClass of Event. We typically think of each class period as an event, and the course as a collection of these events. Course here is used to describe a specific collection, as in “Dr. Spangler’s class on medieval art, taught in the fall of 2002.” The course that appears in the course catalog is something quite different. When one says “While on sabbatical in 1998, I developed a new course” one is referring to an information content entity as a work product of the sabbatical, not an event such as the teaching of the course. VIVO does not currently represent this distinction. But it can following analysis.Brian
20
Degree granting process is a document act that results in an academic degree document, and in a new quality for the person awarded the degree.Brian
21
A country is a legally-defined spatial region. We can say things such as “this event occurred in France”. This is distinct from the government of a country.Rolf
22
Location is a site. It may have a postal address, a name, a geolocation (latitude and longitude)
23
Software is an information content entity. See the Software Ontology.
24
Textual entities include Postal address and email address.
25
Document status is a quality of a document. Some qualities are of related processes, such as completion of a peer review process, which might result in a “peer reviewed” quality for a document that is the output of such a process.
26
Datetime precision is a quality of a date time.
27
An Academic Degree is a document. It is the output of a degree granting process. The representation of academic degree in VIVO currently will require substantial revision. See Early Thoughts on Representing Academic Degrees in VIVO
28
A postal address is a textual entity. It has data properties to hold address parts, and a relationship to the person or organization that has the address. See Early Thoughts About Addresses
29
OrcidID is a centrally registered identifier, as defined in IAO. This is consistent with the formulation for identifiers found here: Early Thoughts on Representing Identifiers in VIVOHigh
30
Funder is a disposition of some organizations, and some people. An organization that has a funder disposition funds things. See Early Thoughts: Representing Organizations in VIVO
31
Faculty member is a role, not a type as it is now in VIVO. People have the role FacultyMember in a Position in an Organization. We should not need position types, or person types. People have the role Author in an Contributorship in a Paper. We can represent any contribution to a paper as a role in a contributorship. Since each contributorship is an occurrent, each can be time limited as needed.
32
From CERIF mapping: cfProj_Fund.cfFraction, Fraction in the complete cost of the project; Consider for future versions: IRI: http://purl.org/cerif/frapo/providesFractionOfTotalFunding An object property linking funding to a budget, specifying what fraction of the total budget is provided by that source of funding.
33
From CERIF mapping, cfPers.cfBirthdate, Date of birth of a person; reviewer comment: Since it could be useful to have this data, it makes sense to extend the VIVO ontology with a new property or reuse the existing one. foaf:birthdate hasn't been used so far in the VIVO data model -- It is a question whether this property should be part of exchange process between different system due to GDPR. Therefore, I am not sure mapping of this property is important and needed at all.mediumlow
34
From CERIF mapping, cfPers.cfGender, Gender of a person, it is a char, f or m; Reviewer comments: I'm not sure, that male or female would be enough nowdays ... ; In many communities the decision has been made to not use gender at all. See: https://www.loc.gov/aba/pcc/documents/gender-in-NARs-revised-report.pdf; The same as above, we can discuss ommiting/droping this and the line above [birth date]
35
From CERIF mapping, cfPersName_Pers, Variation of Person names, for instance it might be name in different alphabet, etc. Reviewer comment: rdfs:label can not represent the variation of names. vcard:Name could be used for it. But there is no option to specify which kind of name (preferred / alternative / alias / maiden name) it is. There is an extension needed.High
36
From CERIF mapping, cfPers_OrgUnit.cfFraction, Fraction of the employment, for instance someone can have a part-time position in an organization, or even can be administrator with 30% of its time, and a software developer with 70% of its time; Reviewer comment: There are no properties in Position that relate to cfFraction; We probably need here a new property.
37
From CERIF mapping, cfResProdAltName, Alternative name of the product; Reviewer comment: We need an extension for being able to add an aternative name or title
38
From CERIF mapping, cfResPat.cfCountryCode, 2-letters code of the country in which patent has been registered; Reviewer comment: Probably we should implement country codes as well as a new datatype property for them and add the codes to the country profiles; Maybe as an object property? It's not necessarily a string value and we may want express things about this code
39
From CERIF mapping, cfResPatVersInfo, A free-text description of a version of patent; Reviewer comment: Probably we need here a new datatype property - _:patent_version or something like this ...
40
From CERIF mapping, cfFacilName, Facility name; Reviewer comment: Probably we need a new structure for assigning names to entities, since rdfs:label is not sufficient for this purpose; It is the same problem in all other cases, we should resolve it for all cases, or just continue using rdfs:label (for cfResPubl -> Document, it is also defined to use rdfs label for publication title). If rdfs:label is used for title or name, why rdfs:comment is not used for description instead of introducting vivo:description?
41
From CERIF mapping: cfProj_Fund.cfFraction, cfFacil_Equip.cfClassId=" eda2da07-34c5-11e1-b86c-0800200c9a66["Provision"]"; cfClassSchemeId="4c2f217d-98ad-4c49-bbb0-399e28d7a8c9["Research Infrastructure Relations"]", This is used for establishing relation between equipment provisioned for the needs of a facility. Reviewer comment: Is there a class for Facility and seperated class for Equipment in VIVO, and is there an object property linked those two classes instances? Can we change hasEquipment and equipmentFor domain and range to support establishing link between facility and equipment.
42
From CERIF mapping: cfOrgUnitResAct, Free-form description of the organization research activities; Reviewer comment: Possible to open up domain for #ReserchOverview? Currently person only
43
From CERIF mapping: cfFacil_Equip.cfFraction, Fraction of equipment capacity used for a facility; Reviewer comment: Here we need a new datatype property.
44
From CERIF mapping: cfOrgUnit_Equip.cfEndDate, End date when organization stopped to be an owner of the equipment (or shared owner); Reviewer comment: Do you have a specific property from Eagle-I in mind? Probably we need here a new sub-property of vivo:dateTimeInterval?
45
From CERIF mapping: cfOrgUnit_Equip.cfFraction, There might be more than one owner (shared equipment), in that case multiple records of cfOrgUnit_Equip linked with the same equipment should exists, and each of them should use cfOrgUnit_Equip.cfFraction for preserving fraction of ownership.; Suggestion: Ontology Eagle-i; Reviewer comment: Probably we should have a new property for it.
46
From CERIF mapping: cfOrgUnit_Equip.cfAvailability, Not a flag with binary value, it is a free text providing availability of equipment; Suggestion: Ontology Eagle-i; Reviewer comment: Probably we should have a new property for it.
47
From CERIF mapping: cfOrgUnit_Equip.cfConditions, Under which conditions the equipment might be used over the organization unit; Suggestion: Ontology Eagle-i; Reviewer comment: Probably we should have a new property for it.
48
From CERIF mapping: cfOrgUnit_Equip.cfCurrCode, Currency code (see the next line); Suggestion: Ontology Eagle-i; Reviewer comment: Probably we should have a new property for it.
49
From CERIF mapping: cfOrgUnit_Equip.cfPrice; Suggestion: Ontology Eagle-i; Reviewer comment: Probably we should have a new property for it.Christian
50
From CERIF mapping: cfOrgUnit_Srv.cfStartDate, Start date when organization became owner of service (or shared owner); suggestion: eagle-i resource ontology; Reviewer comment: Probably we need here a new sub-property of vivo:dateTimeInterval?Christian
51
From CERIF mapping: cfOrgUnit_Srv.cfEndDate, End date when organization stopped to be an owner of service (or shared owner); suggestion: eagle-i resource ontology; Reviewer comment: Probably we need here a new sub-property of vivo:dateTimeInterval?Christian
52
From CERIF mapping: cfOrgUnit_Srv.cfFraction, There might be more than one owner (shared service), in that case multiple records of cfOrgUnit_Srv linked with the same service should exists, and each of them should use cfOrgUnit_Srv.cfFraction for defining fraction of ownership. suggestion: eagle-i resource ontology; Reviewer comment: Probably we should have a new property for it.Christian
53
From CERIF mapping: cfOrgUnit_Srv.cfAvailability, Not a flag with binary value, it is a free text providing availability of service; suggestion: eagle-i resource ontology; Reviewer comment: Probably we should have a new property for it.Christian
54
From CERIF mapping: cfOrgUnit_Srv.cfConditions, Under which conditions the service might be used over the organization unit; suggestion: eagle-i resource ontology; Reviewer comment: Do you have a specific property from Eagle-I in mind? Probably we should have a new property for it.Christian
55
From CERIF mapping: cfOrgUnit_Srv.cfCurrCode, Currency code (see the next line); suggestion: eagle-i resource ontology; Reviewer comment: Do you have a specific property from Eagle-I in mind? Probably we should have a new property for it.Christian
56
From CERIF mapping: cfOrgUnit_Srv.cfPrice, price for using service; suggestion: eagle-i resource ontology; Reviewer comment: Do you have a specific property from Eagle-I in mind? Probably we should have a new property for it.Christian
57
From CERIF mapping: cfSrv_Class.cfClassId="eda2d9fb-34c5-11e1-b86c-0800200c9a66["Virtual"]";cfClassSchemeId="759af93d-34ae-11e1-b86c-0800200c9a66["Research Infrastructure Types"]", Type of facility. The list of available types available at https://github.com/EuroCRIS/CERIF-Vocabularies/blob/master/ResearchInfrastructureTypes.xml ; Reviewer comment: obo:ERO_0000005 (Service) doesn't match indeed with any type of research infrastructure in https://github.com/EuroCRIS/CERIF-Vocabularies/blob/master/ResearchInfrastructureTypes.xml. We need here new classes.Christian
58
From CERIF mapping: cfEvent.cfFeeOrFree, A flag whether event if free or there is a fee; Reviewer comment: Probably we need here a new property.High
Should be solved with the Academic Event Ontology - https://github.com/tibonto/aeon
Christian
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100