Hoi,
For many categories we have exactly that in Reasonator. This functionality
is based on "is a list of". It functions not for all categories or all
content for a category. Wikidata often shows more data particularly when
the categories from "other" Wikipedias have been harvested.
It would be relatively easy to continuously harvest data from Wikipedias
based on such categories.
Thanks,
GerardM
https://tools.wmflabs.org/reasonator/?q=Q8328346
On 24 August 2016 at 14:21, Navino Evans <nav...@histropedia.com> wrote:
> If you could store queries, you could also store queries for each item
>> that is about a list of things, so that the query returns exactly the
>> things that should be in the list ... could be useful.
>
>
> This also applies to a huge number of Wikipedia categories (the non
> subjective ones). It would be extremely useful to have queries describing
> them attached to the Wikidata items for the categories.
>
> On 24 August 2016 at 02:31, Ananth Subray <ananth.sub...@gmail.com> wrote:
>
>> मा
>> ------------------------------
>> From: Stas Malyshev <smalys...@wikimedia.org>
>> Sent: 24-08-2016 12:33 AM
>> To: Discussion list for the Wikidata project.
>> <wikidata@lists.wikimedia.org>
>> Subject: Re: [Wikidata] A property to exemplify SPARQL queries
>> associated witha property
>>
>> Hi!
>>
>> > Relaying a question from a brief discussion on Twitter [1], I am curious
>> > to hear how people feel about the idea of creating a a "SPARQL query
>> > example" property for properties, modeled after "Wikidata property
>> > example" [2]?
>>
>> Might be nice, but we need a good way to present the query in the UI
>> (see below).
>>
>> > This would allow people to discover queries that exemplify how the
>> > property is used in practice. Does the approach make sense or would it
>> > stretch too much the scope of properties of properties? Are there better
>> > ways to reference SPARQL examples and bring them closer to their source?
>>
>> I think it may be a good idea to start thinking about some way of
>> storing queries on Wikidata maybe? On one hand, they are just strings,
>> on the other hand, they are code - like CSS or Javascript - and storing
>> them just as strings may be inconvenient. Maybe .sparql file extension
>> handler like we have for .js and .json and so on?
>>
>> --
>> Stas Malyshev
>> smalys...@wikimedia.org
>>
>> _______________________________________________
>> Wikidata mailing list
>> Wikidata@lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/wikidata
>>
>> _______________________________________________
>> Wikidata mailing list
>> Wikidata@lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/wikidata
>>
>>
>
>
> --
> ___________________________
>
> The Timeline of Everything
>
> www.histropedia.com
>
> Twitter <https://twitter.com/Histropedia> Facebo
> <https://www.facebook.com/Histropedia>ok
> <https://www.facebook.com/Histropedia> Google +
> <https://plus.google.com/u/0/b/104484373317792180682/104484373317792180682/posts>
> L <http://www.linkedin.com/company/histropedia-ltd>inke
> <http://www.linkedin.com/company/histropedia-ltd>dIn
> <http://www.linkedin.com/company/histropedia-ltd>
>
>
> _______________________________________________
> Wikidata mailing list
> Wikidata@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikidata
>
>
_______________________________________________
Wikidata mailing list
Wikidata@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata
