Hi,
I think a valid_from and valid_to-field would be a great idea. Especially for queries on
the db.
But I think it is a fundamental design decision and I'm not sure if it's possible
to integrate now...
LB
Marco Fleckinger <marco.fleckinger(a)gmail.com> schrieb:
Hi,
On 30.09.2012 12:07, Daniel Kinzler wrote:
On 30.09.2012 11:59, Marco Fleckinger wrote:
> regarding an actual topic in Germany about publication of the
timetable-data
of
> Deutsche Bahn (German national railway
company) and their
willingness of a
> discussion with other Open-Data-Supporters it
may be a good idea of
providing an
> expiration dates for Wikidata-records.
>
> In their open letter to Mr. Kreil [1] they announced that it may
cause
problems
> providing the timetable-data in an open way
if e.g. anybody uses old
data.
Or approach to this is to mark individual statements as "historic",
while
the
most current data is marked as
"preferred". This is already necessary
for basic
things like population numbers. However, I
don't think we need to
expire data
automatically - it should just be superseded by
newer information.
Possible solution, but what will you do if a railway company does not
provide actual data anymore? Then the old data is still the most
actual.
Another using case would be a new law. There you could determine the
actual one by checking such dates with the server's date. The new law
will be in the repository before, but will be visible as it comes in
force.
So also a launch field would be great.
So with launch and expiration dates it would be possible that there
will
be no data if there is no data in the database, very important for some
applications as Deutsche Bahn says.
Marco
_______________________________________________
Wikidata-l mailing list
Wikidata-l(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-l
--
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.