On 27/08/2015 23:37, Stas Malyshev wrote:

As this is just starting the SPARQL story, it would be nice to see
suggestions about how we could format the output better... Maybe some
export options in the GUI. JSON has all the data, but some processing is
required to get CONSTRUCT produce some useful RDF serialization. At
least for now.

I think help with query building is at least as important as serialization of results.  If you can't work out how to find anything, there will be no results to serialize.  :-) Every SPARQL end-point exposes differently-structured RDF, so the first job a newcomer has is to try to work out what classes and properties are in there, and how they relate to each other.

So it would be good to have a guided query builder, which starts off "I want to find ..." with a drop-down list of classes (possibly complete, possibly a selection of the 'key' ones).  You select a class, and a second line pops up with a list of properties for that class.  Select one, and you get a text box with autocomplete to type a value into, etc.  So the query builder is itself using SPARQL queries to provide context-relevant options for the searcher.  When they have the result they want, the system can give them the SPARQL query which generated their result, for future reference and/or hand-editing.  But they don't actually have to write any SPARQL themselves.

Richard

--
Richard Light

_______________________________________________
Wikidata-tech mailing list
Wikidata-tech@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-tech