Re: [Wikidata-l] ontology Wikidata API, managing ontology structure and evolutions

2014-01-15 Thread Daniel Kinzler
Yes, I agree that statements (or claims) about properties would be useful. In fact, this is something I hope to see on the road map for 2014. -- daniel Am 15.01.2014 13:54, schrieb Lukas Benedix: > It would be nice to have statements about properties. > > Property:P107 -> isDeprecated -> "True"

Re: [Wikidata-l] ontology Wikidata API, managing ontology structure and evolutions

2014-01-15 Thread Lukas Benedix
It would be nice to have statements about properties. Property:P107 -> isDeprecated -> "True" That would also make it easier to claim some "constraints" for properties: Property:P21 -> validValue -> Q6581097 Property:P21 -> validValue -> Q6581072 Property:P21 -> validValue -> Q1097630 Property:P2

Re: [Wikidata-l] ontology Wikidata API, managing ontology structure and evolutions

2014-01-10 Thread John Erling Blad
Perhaps properties could be marked as deprecated, that is the Pxx and not the values in Qxx, and then published as part og the entity data. That would make any upcoming change detectable for reusers. It would also make it necessary to have some kind og delayed process on deletions, but that should

Re: [Wikidata-l] ontology Wikidata API, managing ontology structure and evolutions

2014-01-10 Thread Markus Krötzsch
On 10/01/14 03:21, emw wrote: What about monthly/dump-based aggregated property usage statistics? Property usage statistics would be very valuable, Dimitris. It would help inform community decisions about how to steer changes in property usage with less disruption. It would have other sig

Re: [Wikidata-l] ontology Wikidata API, managing ontology structure and evolutions

2014-01-09 Thread emw
> > What about monthly/dump-based aggregated property usage statistics? > Property usage statistics would be very valuable, Dimitris. It would help inform community decisions about how to steer changes in property usage with less disruption. It would have other significant benefits as well. Get

Re: [Wikidata-l] ontology Wikidata API, managing ontology structure and evolutions

2014-01-09 Thread Dimitris Kontokostas
What about monthly/dump-based aggregated property usage statistics? People would be able to check property trends or maybe subscribe to specific properties via rss. On Thu, Jan 9, 2014 at 3:55 PM, Daniel Kinzler wrote: > Am 08.01.2014 16:20, schrieb Thomas Douillard: > > Hi, a problem seems (no

Re: [Wikidata-l] ontology Wikidata API, managing ontology structure and evolutions

2014-01-09 Thread Daniel Kinzler
Am 08.01.2014 16:20, schrieb Thomas Douillard: > Hi, a problem seems (not very surprisingly) to emerge into Wikidata : the > managing of the evolution of how we do things on Wikidata. > > Properties are deleted, which made some consumer of the datas sometimes a > little > frustrated they are not

Re: [Wikidata-l] ontology Wikidata API, managing ontology structure and evolutions

2014-01-09 Thread Markus Krötzsch
On 08/01/14 16:57, Denny Vrandecic wrote: I am afraid that keeping versions is something the current architecture will be terrible at supporting, especially because we need to keep snapshots over a multitude of pages. MediaWiki is not terribly good at that. If something like the memento extension

[Wikidata-l] ontology Wikidata API, managing ontology structure and evolutions

2014-01-08 Thread Denny Vrandecic
I am afraid that keeping versions is something the current architecture will be terrible at supporting, especially because we need to keep snapshots over a multitude of pages. MediaWiki is not terribly good at that. If something like the memento extension would really work at scale, maybe... Anyw

[Wikidata-l] ontology Wikidata API, managing ontology structure and evolutions

2014-01-08 Thread Thomas Douillard
Hi, a problem seems (not very surprisingly) to emerge into Wikidata : the managing of the evolution of how we do things on Wikidata. Properties are deleted, which made some consumer of the datas sometimes a little frustrated they are not informed of that and could not take part of the discussion.