If I may try to summarize, it is saying that neither reification
Not exactly, please note the difference between RDF reification and
conceptual reification. IMHO, the last mentioned is the way to go.
Best,
Krzysztof
On 10/16/2014 08:15 AM, Frans Knibbe | Geodan wrote:
On 2014-10-14 19:24, Carsten Keßler wrote:
Dear all,
here’s another paper that discusses different approaches:
http://carsten.io/trame-kessler-kuhn-cosit2013.pdf
Thank you! Yes, that paper is also a good read. Now my head is
spinning even more :-)
If I may try to summarize, it is saying that neither reification nor
named graphs are satisfactory solutions, but turning/events/ into
first class citizens and making them explicit /is/.
Do you think this approach in recommendable in all cases where
resources have properties that can undergo change? Wouldn't it
obfuscate direct relationships between things in much the same way as
turning a property into a class would?
Regards,
Frans
Best,
Carsten
---
Carsten Kessler – http://carsten.io
Center for Advanced Research of Spatial Information
Department of Geography
Hunter College – CUNY
695 Park Avenue
New York, NY-10065
On Monday, October 13, 2014 at 8:32, Anisa Rula wrote:
Hi,
our paper [1] surveys all the possible approaches for representing
temporal information in the context of Linked Data. You may find it
useful for your work.
Best regards,
Anisa
1. http://iswc2012.semanticweb.org/sites/default/files/76490481.pdf
On 13 Oct 2014, at 14:16, Sarven Capadisli <[email protected]
<mailto:[email protected]>> wrote:
On 2014-10-13 13:54, Frans Knibbe | Geodan wrote:
Hello!
I wonder if a way of recording changes in properties of resources
can be
recommended. Many resources in real life have properties that have a
time range of being valid. In some datasets, only the current (or most
recent) state of a resource is stored, but in many cases it is
important
to keep track of the history of development of a resource.
An example:
:john_smith
a foaf:person ;
foaf:name "John Smith" ;
Let's say that on 2013-09-27 John Smith marries Betty Jones. John
Smith
is still the same person, so it makes sense to extend the same
resource,
not create a new version:
:john_smith
a foaf:person ;
foaf:name “John Smith” ;
ex:marriedTo :betty_jones ;
How could I efficiently express the fact that the statement
:john_smith
ex:marriedTo :betty_jones is valid from 2013-09-27? And if the couple
divorces, that the property has expired after a certain date? It would
be nice if the way of modelling makes it easy to request the most
recent
state of a resource, any historical state, or a list of changes
during a
time period.
A quick web scan on the subject revealed some interesting research
papers, but as far as I can tell all solutions need extensions of RDF
and/or SPARQL to work.
Perhaps this question is really about the ability to make statements
about a triple? Which is a problem for which no satisfactory solution
has been found yet?
Regards,
Frans
Hi Frans,
This is not a comprehensive answer on this topic, but you might
want to take a look at PROV-O [1] (which can address validity and
history of entities) and maybe even employ OA [2].
Capturing temporal dimension of linked data by Jindřich Mynarz is
an excellent read [3].
[1]http://www.w3.org/TR/prov-o/
[2]http://www.openannotation.org/spec/core/
[3]http://blog.mynarz.net/2013/07/capturing-temporal-dimension-of-linked.html
-Sarven
http://csarven.ca/#i
------------------------------------------------------------------------
Frans Knibbe
Geodan
President Kennedylaan 1
1079 MB Amsterdam (NL)
T +31 (0)20 - 5711 347
E [email protected]
www.geodan.nl <http://www.geodan.nl> | disclaimer
<http://www.geodan.nl/disclaimer>
------------------------------------------------------------------------
--
Krzysztof Janowicz
Geography Department, University of California, Santa Barbara
4830 Ellison Hall, Santa Barbara, CA 93106-4060
Email: [email protected]
Webpage: http://geog.ucsb.edu/~jano/
Semantic Web Journal: http://www.semantic-web-journal.net
