After reading all the info in that bug report, and all the info in the
'duplicate' bugs, I'm confused about what subproperties *should* do,
and what they currently do and don't do.

Could someone please summarise what is expected, currently implemented
and currently broken? I think such a table of features could be
maintained here:
http://semantic-mediawiki.org/wiki/Property:Subproperty_of

I'll start work on it when I have some time, but I've only just
started to use subproperties, so someone with more direct experience
should be able to do this much faster than me (I hope).


For the record, my opinion is that we have enough syntax already.
Anyone using subproperties should be aware of the implications, and
shouldn't need special query syntax to ask for 'direct' vs. 'indirect'
values of a superproperty. If they wan't only the direct values, they
shouldn't use subproperties... IMHO.


Cheers,
Dan.

On 2 October 2011 21:17, Yury Katkov <katkov.ju...@gmail.com> wrote:
> It seems that it's a planned feature
> Everyone who is interested in this new feature, please vote for this
> issue in Bugzilla:
>
> https://bugzilla.wikimedia.org/show_bug.cgi?id=12822
>
> On Sun, Oct 2, 2011 at 9:34 PM, Dan Bolser <dan.bol...@gmail.com> wrote:
>> On 1 October 2011 19:07, Yury Katkov <katkov.ju...@gmail.com> wrote:
>>> Hi everyone, developers and users!
>>>
>>> ==Problem==
>>>
>>> The printout statements are not currently engaged in inference in
>>> Semantic MediaWiki.
>>> For example if I have a page Moskow with a property [[is capital
>>> of::Russia]], which is a subproperty of the property [[located in]].
>>> If I construct the following query
>>>
>>> {{#ask:
>>>  [[is capital of::Russia]]
>>>  | ?located in
>>> }}
>>>
>>> there will be nothing in a located in column.
>>> == Questions ==
>>>
>>> # are there any plans to add inference in printout statements?
>>> # how hard is this task?
>>> # how many people besides myself are in need of this feature? The
>>> possible workarounds just seem wrong...
>>
>> I agree that the above query should return "Moscow, Moscow", according
>> to the definition of subproperties [1].
>>
>> To the extent that I expect things like "autocomplete on property =
>> located in" to return 'Moscow' as one of the possibilities in SF
>> (currently fails, but is this related?), then yes, I need features
>> like this.
>>
>>
>> Cheers,
>> Dan.
>>
>> [1] http://semantic-mediawiki.org/wiki/Property:Subproperty_of
>>
>>> Sincerely yours,
>>> --
>>> Yury V. Katkov
>>> WikiVote! llc
>>>
>>> ------------------------------------------------------------------------------
>>> All of the data generated in your IT infrastructure is seriously valuable.
>>> Why? It contains a definitive record of application performance, security
>>> threats, fraudulent activity, and more. Splunk takes this data and makes
>>> sense of it. IT sense. And common sense.
>>> http://p.sf.net/sfu/splunk-d2dcopy2
>>> _______________________________________________
>>> Semediawiki-devel mailing list
>>> Semediawiki-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
>>>
>>
>
>
>
> --
> Yury V. Katkov
> WikiVote! llc
>

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
_______________________________________________
Semediawiki-devel mailing list
Semediawiki-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/semediawiki-devel

Reply via email to