Markus,
Thanks for the reply. For the time being, I was able to find a work-around:
1. Users can still enter their role history using multi-instance templates
with Semantic Forms, so they get the same ability to enter their history
using the form, which is nice to record on their user page for reference.
2. The Template:Role no longer uses semantic internal objects.
3. Instead, Template:Role encodes semantic properties *only if* the End
date is blank (i.e. the role is current)
The result is that users can record their complete history on their user
page, but only their *current role* is stored as semantic data. This is
fine, because I have no need to query for historical data -- I just want to
query for their current role. Because I am only encoding one role, I don't
need semantic internal objects -- all semantic data is stored directly on
their user page rather than using internal objects.
Best Regards,
Daniel
On Sun, Nov 11, 2012 at 10:18 AM, Markus Krötzsch <
markus@...> wrote:
> Hi Daniel,
>
> short answer: no good way of doing this in general now. We need to
> implement this. This is definitely on our list of features to consider for
> SMW 1.9. Maybe there are other printout types that we should support as
> well, e.g., showing the list of all properties that one object has.
>
> This might be part of a more general extension of SMW printout features. I
> would also like to have a "|!format=count" option, and maybe even other
> formats for printing the list of values for one property. What we do now
> could be considered "|!format=list" with "|!sep=," or "|!sep=<br>"
> depending on context.
>
> It would be good to collect related ideas somewhere.
>
> Cheers,
>
> Markus
>
>
>
> On 09/11/12 18:19, Daniel Robbins wrote:
>
>> Hi All,
>>
>> I am building a Semantic Mediawiki system where Users have their own
>> Person
>> template which sets a number of semantic properties. Using semantic
>> internal objects, users can also define roles. There can be multiple
>> roles,
>> and each role has a start and (optional) end date.
>>
>> This returns all Users in a role:
>>
>> {{ #ask: [[Role type::Developer]] |? Role of }}
>>
>> This returns all users with a Role defined:
>>
>> {{ #ask: [[-Role of::+]] }}
>>
>> But I run into problems when I want to map all users in a particular role.
>> A person's geographic coordinates are stored using the [[Geoloc::]]
>> property on their user page. Ideally, I would do this:
>>
>> {{ #ask: [[Role type::Developer]]
>> |? Role of.Geoloc
>> |? Role of
>> }}
>>
>> Ideally, this would return the Geographic coordinates of each developer,
>> and each developer page (and this query could be put into map format and
>> displayed using Google Maps.)
>>
>> Problem is -- The syntax "Role of.Geoloc" is not supported in property
>> outputs. It would be extremely handy to be able to do this as this would
>> seem to be a common pattern when using semantic internal objects. Yaron
>> Koren has suggested a work-around of storing the Geoloc inside the Role
>> internal object as well, but this is kludgy in design and practice -- a
>> page needs to be saved *twice* for this to work, resulting in wacky wiki
>> user experience.
>>
>> Any thoughts on getting this working or anyone out there who would be
>> willing to add prop chain support to #ask property output?
>>
>> Thanks and Regards,
>>
>> Daniel Robbins
>> ------------------------------**------------------------------**
>> ------------------
>> Everyone hates slow websites. So do we.
>> Make your web apps faster with AppDynamics
>> Download AppDynamics Lite for free today:
>> http://p.sf.net/sfu/appdyn_**d2d_nov <http://p.sf.net/sfu/appdyn_d2d_nov>;
>> ______________________________**_________________
>> Semediawiki-user mailing list
>> Semediawiki-user@...**sourceforge.net<Semediawiki-user@...>
>> https://lists.sourceforge.net/**lists/listinfo/semediawiki-**user<https://lists.sourceforge.net/lists/listinfo/semediawiki-user>;
>>
>>
>
|