These are chat archives for linkeddata/dokieli

12th
Nov 2017
Silvio Peroni
@essepuntato
Nov 12 2017 06:46
Mhm... something I could try to think about is a property pso:atTime (sub property of tvc:aiTime) so as to relax such non-persistence feeling, at least for further usages. I’ll think about it, thanks for sharing your thoughts
Sarven Capadisli
@csarven
Nov 12 2017 09:56
@essepuntato That would great! I honestly think that others may have a similar impression. Besides that, there is the additional vocab being added for the time bits. That may be well justified but if it is a matter of just few properties being added, pso could handle it. Lastly, consider https://www.w3.org/TR/owl-time/
Silvio Peroni
@essepuntato
Nov 12 2017 10:28
@csarven, actually TVC is already reusing OWL time… let me figure out some plausible solution for that. I’ll let you know once it is implemented, ok?
Sarven Capadisli
@csarven
Nov 12 2017 10:29
Sounds good.
Is the time dimension particularly important here? Why not just 'pso:withStatus' ?
Where the domain is unspecified.
Like I said, initially I just wanted a way to indicate that the current status of the document - a property or a class on the article would've been fine.
Silvio Peroni
@essepuntato
Nov 12 2017 10:38
It is important because statuses may (and usually do) are defined within a specific time frame - e.g. you would like to know when a “published” status is valid on that document, for how long a document has been associated with the “under-review” status, etc. But I see your point of semplifying it for other, non-time related, statuses. Thanks for your input, I’ll see how to better handle it.