Last modified: 2011-06-22 22:52:01 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T31538, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 29538 - native sparql support
native sparql support
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
Semantic MediaWiki (Other open bugs)
unspecified
All All
: Unprioritized enhancement (vote)
: ---
Assigned To: Markus Krötzsch
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2011-06-22 21:23 UTC by Joel Hedlund
Modified: 2011-06-22 22:52 UTC (History)
1 user (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Joel Hedlund 2011-06-22 21:23:36 UTC
Semantic mediawiki is very nice and lets you do many nifty things that just aren't possible with vanilla mediawiki. However, the {{#ask: ... }} interface is quite limited compared to what you could do with sparql, and it would be really nice if smw could ship with sparql support. What I want to do, for example, which is currently impossible:

1. Report properties from other pages:
For example, a product has several [[available from::shop]] and each shop is [[located at::city]]. I want to dynamically generate lists of products along with which shop and city I can get it from, and I want to do it without jumping through the template hoops where the {{#ask: ... |template=foo}} template does a secondary query for the city.

2. Query for properties, not for pages:
A page has one or more [[concerns::field]]. I want to get at the individual fields for further processing, I do not want a comma separated list that I have to unreliably parse and string mangle.

3. Compare multiply set properties across pages:
A page has one or more [[concerns::field]] and a person has one or more [[expertise::field]]. For any given page I want to be able to generate dynamic lists of people who are experts in one or more of the concerned fields, and I do not want to repeat myself and give the fields again in the query.

4. And more...
Comment 1 Jeroen De Dauw 2011-06-22 22:35:34 UTC
You might already be aware of this, but SMW 1.6 introduces native support for triplestores, which means that instead of using the MySQL/whatever database used by your MW install, SMW will store it's data in this tripplestore and query from it. This then obviously allows doing SPARQL queries against your tripplestore for data stored by SMW. Is that what you want to be able to do, or do you want to be able to display data in your wiki based on SPARQL queries as well? IIRC some people showed some demo of an extension with capabilities along these lines on the last fall SMWCon; not sure what the state of that is. There is some new extension that allows embedding visualizations that pull data using SPARQL that works completely loose from SMW, but it's still very preliminary and does not support near as many formats as SMW: https://secure.wikimedia.org/wikipedia/mediawiki/wiki/Extension:Spark
Comment 2 Joel Hedlund 2011-06-22 22:52:01 UTC
Hey, neat!

I guess I should have specified, but I guess what I'm looking for is a sort of {{#sparql: ... }} replacement for {{#ask: ... }} for inline queries, using SMW's types for rendering stuff correctly and creating sortable tables and the like.

I reckon some output formatting code would have to be restructured though, since it's currently quite page-centric, one per row, and I guess what I'm suggesting would rather produce rows containing zero or more pagenames and zero or more properties. Does that make sense?

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links