- From: Bert Van Nuffelen via GitHub <sysbot+gh@w3.org>
- Date: Mon, 31 May 2021 11:54:21 +0000
- To: public-sdwig@w3.org
@dr-shorthair > > Your points are all valid. But I would suggest that some of this is just modeling choices. In particular, an event could legitimately be modeled in two ways: > > * it _is_ a (kind of) temporal-entity, or > > * it _is associated with_ a temporal-entity > > For me the above modelings are different. When modeling real world entities I would use the second case, because it allows to express the temporal dimension semantics. The first I would use in the context of temporal reasoning, after selecting the temporal dimension semantics. These are different use-cases, and unfortunately when reading quickly the examples one get the impression that the first case is the desired usage. It took me a while and (re)reading to understand what was happening in the examples. That is the motivation for this comment. So an example where an event/business entity is modeled with 2 or more temporal dimensions illustrating the second case would be helpful. ``` ex:dataset1 dct:issued ex:time1 dct:modified ex:time2 ``` -- GitHub Notification of comment by bertvannuffelen Please view or discuss this issue at https://github.com/w3c/sdw/issues/1263#issuecomment-851438155 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 31 May 2021 11:54:59 UTC