Very intriguing.

Are you planning to have support for some kind of display name,  
through a property defined on the Property page maybe ?

It would be nice to have a way to hide the reverse notation with a  
meaningful string sometimes.

- Laurent Alquier
Http://www.Alquier.org


On Aug 26, 2009, at 5:36 PM, Markus Krötzsch <mar...@semantic-mediawiki.or 
g> wrote:

> On Mittwoch, 26. August 2009, Jon Lang wrote:
>> Markus Krötzsch wrote:
>>> If applicable, inverse properties generally are linked to the page  
>>> of the
>>> corresponding property (so "-developer of" links to  
>>> "Property:developer
>>> of"). It is strongly suggested not to create property pages that are
>>> called like inverse properties (it won't destroy anything, but it  
>>> might
>>> create unnecessary confusion).
>>
>> Could you give an example of this, please?  In particular, what are
>> you meaning by "are linked to"?
>
> Sorry, I was not very clear here: Sometimes property names are  
> displayed
> somewhere, for example in the header of tables created by #ask. Such  
> texts are
> often linked to the property's page. In case of inverses, links will  
> go to
> non-inverse property pages.
>
>>
>>> Also, you cannot use inverse properties to enter semantic data
>>> into the wiki: all annotations must be on the page that is the  
>>> subject of
>>> the non-inverted property.
>>
>> So inverse properties are like the "what pages link here?" Wiki  
>> feature?
>
> Very roughly, yes.
>
>>
>>> Inverses in queries are currently only supported if they are of
>>> Type:Page.
>>
>> That makes sense.
>>
>>> == Development Information ==
>>>
>>> The main changes that I expect to be required in SMW extensions is  
>>> in
>>> places where you deal with property subjects and silently expect  
>>> them to
>>> be of Type:Page. If users can enter inverse properties, then a  
>>> query for
>>> a subject can also return datavalues of other datatypes, so you  
>>> need to
>>> use the generic datavalue API, or check the type of the datavalue  
>>> first.
>>
>> Could you give an example of such a query, for illustrative purposes?
>
> What query do you mean? You mean the actual source code that uses  
> inverse
> properties? It is not different from code using non-inverse  
> properties,
> really.
>
>>
>>> I hope that SMW already works properly in all cases where inverses  
>>> can
>>> occur. Feedback is welcome.
>>
>> This is a welcome step forward.  The other feature that I'm hoping to
>> see relatively soon are transitory properties.
>
> This is much harder (I think you mean "transitive" here).
> Maybe not so soon ...
>
> -- Markus
>
>
>
> -- 
> Markus Krötzsch  <mar...@semantic-mediawiki.org>
> * Personal page: http://korrekt.org
> * Semantic MediaWiki: http://semantic-mediawiki.org
> * Semantic Web textbook: http://semantic-web-book.org
> --
>
> --- 
> --- 
> --- 
> ---------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008  
> 30-Day
> trial. Simplify your report design, integration and deployment - and  
> focus on
> what you do best, core application coding. Discover what's new with
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> _______________________________________________
> Semediawiki-devel mailing list
> Semediawiki-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/semediawiki-devel


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Semediawiki-devel mailing list
Semediawiki-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/semediawiki-devel

Reply via email to