Last modified: 2011-03-13 18:05:10 UTC
<ask format="ul"> [[Property1::Value1]]||[[Property2::Value1]] </ask> When using such a query there is only a list of pages given. I think the list should contain the Property that is true. The list might look like this. *Page1, (Property1) *Page2, (Property2) *Page3, (Property2) *Page4, (Property1) *Page5, (Property1,Property2) *Page6, (Property2) *Page7, (Property1)
The same thing could be useful for <ask format="ul"> [[Property3::Value1]] </ask> When Property1 and Property2 are Subpropreties of Property3
This sounds like a useful feature but it is hard to implement in practice, since it does not fit into the uniform result format that we use. Also, the need for tracking information about why a certain result is shown is making query answering more difficult. Doing this in SMW would lead to a decrease in performance. It should also be noted that this is not a feature that is common to many query languages: even SPARQL and SQL (which are more powerful than SMW' ask) do not have such a facility. Based on these considerations, I reject this feature request. If there is strong interest in having this, then I would consider submitted code for inclusion in SMW, as long as it does not lead to significant performance reductions.
