Yes, I think this is a very good idea - a simple query to "generate items
which fit the scope of this list" or "generate items which fit the scope of
this category". It could be very useful for maintenance purposes (finding
items in the list/category that don't have the right properties and
flagging them). As they are directly linked to the topic, having them on
the item page makes sense.
The more general question of "example queries for a property" (as in
Dario's original suggestion) feels like it would be more at home on the
talkpage than the property page - using the talkpage gives space for
complexity and alternatives and commentary, and it fits very well alongside
the constraints, which are also recorded there.
Andrew.
On 24 August 2016 at 13:21, Navino Evans <navino(a)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.subray(a)gmail.com> wrote:
मा
------------------------------
From: Stas Malyshev <smalyshev(a)wikimedia.org>
Sent: 24-08-2016 12:33 AM
To: Discussion list for the Wikidata project.
<wikidata(a)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
smalyshev(a)wikimedia.org
_______________________________________________
Wikidata mailing list
Wikidata(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata
_______________________________________________
Wikidata mailing list
Wikidata(a)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(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata