Re: [Wikidata-l] Wikidata query feature: status and plans
You mean some kind of relations * French Region *receive fund from* French state ; * French Department *receive fund from *French Region * ... Hypothetically the domain of the relation *receive fund from* could be Type of administrative Unit, although this relation could be generalised. ? 2014-06-12 0:27 GMT+02:00 Gerard Meijssen gerard.meijs...@gmail.com: Hoi, I can easily imagine many totally unrelated French type of administrative units that are all part of a higher unit. For instance there are the true administrative units with offices and everything. Then there are the water departments that are organised within the same unit.. The police districts, the electoral districts, the carnival groups.. They all have one thing in common and one thing only. All the items of the same type fit with THAT higer level. They do not by definition need to cover its area completely. They can even fit together with another type that has a comparable function but is mutually exclusive.. From my point of view the only thing we need is to know what the is a of an item is and what is on the higher level. Afterthought... something can be totally be within one low level and administratively be subject to the highest level.. Thanks, Gerard On 11 June 2014 12:56, Thomas Douillard thomas.douill...@gmail.com wrote: I'm still talking of the model I proposed in my first post in this thread. I did give an advantage : you can really simply query the type of units used by a country to class his administrative units, like Region, Departement (as two items) for France with just simple in one request of the future simple query module : just retrieve the instances of the class French type of administrative units. This model also apply to any country administrative territorial division. I think French type of administrative units is the auxiliary item markus did mention. We can define precisely what it is becaus this class French type of administrative units regroups the types used by france to class cities, departments ... so clearly if we talk of Paris, there is several possibility, like the region of Paris, the City of Paris ... The city of Paris item is clearly the only one who is clearly defined by french law, hence it is an instance of the class French ville, who in turn is an instance of French type of administrative units. This seems to me a useful model, who can generalise easily to class things like Urban units, who are used for statistical purpose and are defined by national statistical organism in each country, such as INSEE in france Then we could also have a Urban unit class in Wikidata, but this is ambiguous. This class could have a subclass Urban unit as defined by INSEE, with instances such as Parisian urban unit, for hich it gives statistical information. Urban unit as defined by INSEE in turn may be a subclass of any geographical unit defined by INSEE. Then if you want INSEE geographical units, you query all instances of both Urban unit and any geographical unit defined by INSEE. But now let's say you want to find the definition of urban unit by the INSEE itself, not the instances. One way to do that would be to look at the subclass tree of any geographical unit defined by INSEE or the one of Urban unit, or compute the intersection of both trees. One alternative, using metamodelling this time, would be to have a class regrouping all definitions of statistical units used by INSEE. Those definitions identify to some class we already have, such as Urban unit as defined by INSEE identifies to the definition of urban unit by INSEE. Then the class of all definitions used by INSEE would identify to the class of all classes with a name ... unit defined by INSEE. I propose to create the item any type of unit defined by INSEE ; with Urban unit as defined by INSEE an instance of it (actually I might have already have done it /o\) This is an (non mutually exclusive, more complementary) alternative to just class administrative units instances. In a way, this is just identifying (reifying) a classification system and putting an ''instance of'' this item statements to its classes. I think this is interesting in Wikidata as we actually are using a lot of different classification system, having a clear and practicable pattern like this one, using just a few tools like reasonator, is useful. For example if I want to compute the subclass tree of statistical units, but only the classes used by INSEE, I can compute the subclass tree of the statistical geographical unit class but filtering only the instances of any type of unit defined by INSEE, instead of computing a tree intersection. This kind of patterns occurs also for example in biological taxonomy. They use classes such as Genera, taxon, clade. Imo any instance of taxon can be seen as a class of living organisms. Then Taxon is a class of class, just as any type of unit defined by
[Wikidata-l] New Wikidata classes browser (and updated property browser)
Hi all, I have extended our new interactive property browser with a class browser and updated everything to the latest data. You can use these new services to answer questions like: (1) What kinds of things do we actually have on Wikidata? (show all classes with more than 100 instances: humans, cities, galaxies, computer games, earthquakes, ... overall a very clear an readable list of our main subjects) (2) Which properties are typically used on lighthouses (Q39715)? (or any other class) (3) Which types of things have a patron saint (P417)? (or any other property) (4) What are the most used string properties on Wikidata? (5) Which properties are often used in qualifiers? (6) Which properties are often used in statements that have qualifiers? (7) Which properties are not used at all? (8) What are the (direct and indirect) superclasses of ninja (Q9402)? (there are expected things like profession and soldier but also thermodynamic process, which is probably not intended, although there might be some truth to it) (9) What are the most used classes that do not have a superclass? (10) What are the classes with most subclasses? (they have almost 2000 subclasses!) And many more ... I could play with it all day :-) We now offer two datasets: one with properties and classes, and one with properties only. The one with classes takes longer to load (about 10min on my machine) but it's very fast after that. The other one is faster to load and can still answer questions like (4), (5), (6), (7). Here are the links: * Classes+properties: http://tools.wmflabs.org/wikidata-exports/miga/?classes# (be patient, it will be fast once loaded) * Properties only: http://tools.wmflabs.org/wikidata-exports/miga/ Each dataset has an about page with some example queries. To see additional related properties and classes, scroll down to the bottom of the pages of individual properties or classes. Known limitations: * We leave away classes without instances and subclasses, to make the dataset smaller (it's large enough as it is). * Some classes are shown without labels. These are usually things that should not be classes anyway (filter them by narrowing your search to things with more than 10 instances). In any case, this only happens to things that have no superclass. Maybe I will fix this in the future. Feedback is welcome. Cheers, Markus On 11/06/14 14:36, Markus Krötzsch wrote: Hi all, We have prepared a new browser for Wikidata Properties: http://tools.wmflabs.org/wikidata-exports/miga/ It is based on Miga data browser [1]. This means it only works in Google Chrome/Chromium, Opera, Safari, and the Android Browser but not in Internet Explorer, Firefox, and Rekonq. You can browse properties by datatype or usage numbers, and also find related properties for every property (using my own custom notion of relatedness based on relative co-occurrence and overall prevalence). When filtering by usage numbers, you sometimes see only very coarse filters, but you can always apply the same filter again to get more fine grained steps. You can also edit the URL in the browser to modify filters if you cannot find the right one in the UI. This is still experimental. The data is based on the dump of 26 May. The data files for Miga were created using Wikidata Toolkit [2]; I will commit the specific code in due course. Feedback is welcome. Cheers, Markus [1] http://migadv.com/ [2] https://www.mediawiki.org/wiki/Wikidata_Toolkit ___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l ___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l
Re: [Wikidata-l] New Wikidata classes browser (and updated property browser)
Hi Markus, first thanks a lot for these tools. It would be cool to include a link to the property browser into some template, ( Template:P' for example , as Template:Q' generates a link to reasonator. Is there a way to get the database id of some property by its number ? ___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l
Re: [Wikidata-l] New Wikidata classes browser (and updated property browser)
[Including Yaron, the Miga developer, who is not on this list yet] On 12/06/14 17:21, Thomas Douillard wrote: Hi Markus, first thanks a lot for these tools. It would be cool to include a link to the property browser into some template, ( Template:P' for example , as Template:Q' generates a link to reasonator. Is there a way to get the database id of some property by its number ? The internal IDs of Miga are no good for linking, since they depend on the list of items and thus might change with updates. However, the following work: http://tools.wmflabs.org/wikidata-exports/miga/#_cat=Properties/Id=P31 http://tools.wmflabs.org/wikidata-exports/miga/?classes#_cat=Classes/Id=Q39715 Etc. A nice feature in Miga is that all queries work, even if they are not clickable through the UI. If you look at the URL you get after some clicking, it is easy to see how to change it to get other results. Cheers, Markus ___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l
Re: [Wikidata-l] New Wikidata classes browser (and updated property browser)
Perfect thank you (for some reason I did not success, I see the names are case sensitives :) ) 2014-06-12 17:59 GMT+02:00 Markus Krötzsch mar...@semantic-mediawiki.org: [Including Yaron, the Miga developer, who is not on this list yet] On 12/06/14 17:21, Thomas Douillard wrote: Hi Markus, first thanks a lot for these tools. It would be cool to include a link to the property browser into some template, ( Template:P' for example , as Template:Q' generates a link to reasonator. Is there a way to get the database id of some property by its number ? The internal IDs of Miga are no good for linking, since they depend on the list of items and thus might change with updates. However, the following work: http://tools.wmflabs.org/wikidata-exports/miga/#_cat=Properties/Id=P31 http://tools.wmflabs.org/wikidata-exports/miga/? classes#_cat=Classes/Id=Q39715 Etc. A nice feature in Miga is that all queries work, even if they are not clickable through the UI. If you look at the URL you get after some clicking, it is easy to see how to change it to get other results. Cheers, Markus ___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l ___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l
[Wikidata-l] Hello
Sent from my iPad ___ Wikidata-l mailing list Wikidata-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-l
