search

openrif / vivo-isf-ontology

The "VIVO-ISF Ontology" is an OWL2 representation of the VIVO-ISF Data Standard
16 stars 9 forks source link

Consider sub classes for vivo:dateTimeValue #704

Open mconlon17 opened 6 years ago

mconlon17 commented 6 years ago

Several scenarios where a single dateTimeValue is either insufficient or non-informative to represent the reason for recording a date associated with an entity. Date time intervals obfuscated dates further by pushing a start and stop into a non-informatively labeled interval.

Project might have approvalDate, fundedDate, etc.

Publication might have datePublished, dateSubmitted, etc.

Grants might have dateSubmitted, dateAwarded, etc.

Patents might have dateFiled, dateApproved, etc.

Organizations might have dateEstablished

Or perhaps all these are simply dates of some action and we are not modeling the action

See https://jira.duraspace.org/browse/VIVO-1276

mconlon17 commented 6 years ago

Impact Medium

Additional analysis is needed. In some cases, the specific date type will be handled by the software correctly because it is a subClass of DateTimeValue. In other situations, specific software changes may be needed, and potentially data and query changes to differentiate between subClasses of DateTimeValue associated with a particular entity.