About this board

talk

Previous discussion was archived at User talk:Chjohnson39/Archive 1 on 2016-03-20.

Please take part in the Flow satisfaction survey

1
MediaWiki message delivery (talkcontribs)

(That message in other languages: العربية • ‎bosanski • ‎català • ‎Deutsch • ‎Esperanto • ‎français • ‎עברית • ‎polski • ‎português • ‎português do Brasil • ‎русский • ‎اردو • ‎中文 – ‎translate that message)

Hello!

Like some other community members, you are using Flow.

An increasing number of communities now use Flow or are considering it. Although Flow itself is not scheduled for major development during 2016 fiscal year, the Collaboration Team remains interested in the project and in providing an improved system for structured discussions.

You can help us make decisions about the way forward in this area by sharing your thoughts about Flow — what works, doesn't work or should be improved?

Please fill out this survey (available in multiple languages), which is administered by a third-party service. It will not require an email or your username. See our privacy statement.

Thanks for your ideas and opinions about Flow!

Trizek (WMF), on behalf of the Collaboration team, 11:56, 7 September 2016 (UTC)

Reply to "Please take part in the Flow satisfaction survey"
Chjohnson39 (talkcontribs)

similar in output function to the Wikidata Generic Tree tool developed by Magnus_Manske, I have written a SPARQL query that expands entities along a property path or inverse property path.

It only works on the Virtuoso test instance at http://wdm-rdf.wmflabs.org/sparql.

The query looks pretty ugly, but the output is very interesting. This query finds all "parents" (parent taxons, subclasses or parts) of the species "leopard". But, unlike a simple property path result set aggregation, it also shows you how the path is constructed.

It can traverse multiple entities and accepts multiple paths. Since the subject variable is actually bound to the object the default direction is to go up the tree, rather than down, which is actually quite useful and not a feature in the UI. To go down the tree, use the ^ symbol which inverts the path traversal. To restrict the depth of the query, just add transitive option t_max (n).

select distinct ?o ?label ?uri ?rlabel where { { select ?s where { VALUES(?s) {(wd:Q34706)} } } { select ?s ?o ?rlabel ?label ?uri where { ?s wdt:P171|wdt:P279|wdt:P361 ?o . ?o rdfs:label ?label FILTER (lang(?label) = "en"). OPTIONAL {?o wdt:P105 ?rank . ?rank rdfs:label ?rlabel FILTER (lang(?rlabel) = "en") } . OPTIONAL {?o foaf:isPrimaryTopicOf ?uri FILTER regex (?uri, "^http://en.wikipedia.org/wiki/<nowiki>") }} } option (TRANSITIVE, T_IN (?s), T_OUT (?o), T_DISTINCT) }</nowiki>

click here to see the output

Reply to "property path expansion"
There are no older topics