Hi Yaron,
It's not so much what sf/smw can or can't do -- it's about whether {{#ask:}}
is the right approach for repeating event. #ask is presently used to query
articles having *any* date-property. So what benefit actually is there to
having repeatable events handled by #ask? I can think of just ONE BENEFIT: a
user does not need to specify multiple date-properties for an article. Maybe
there are others?Here's the bigger problem though. Lets say we have an article about a book. The article contains many, many dates -- dates for composition, editing, proofing, publishing, shipping, distribution, etc. If repeat-properties are present for the article, which action is being "repeated"? Or maybe is the book itself somehow being "repeated"? So my concern is that -- yes while technically possible -- hardcoding repeat-event properties for an article kinda leads to many questions about the data model you're assuming/looking for. I'm curious, does #ask today handle multiple instances of a named property for an article, or does it just look for a single instance? Does the calendar format accurately show those multiple values? Hmm, if you'd like to bring #ask to a 'new level' that involves dates, might I suggest that a useful generic function would be to perform date arithmetic, eg difference(dated-property-1, dated-property-2, units-selection), and output the result. Or something like that. I'm not thoroughly knowldegeable about #ask, so maybe that's already there. Another example that ties right into the calendar option would be duration(dated-property-1, dated-property-2), which would bracket the two dates in an interesting way. Maybe that's there with the timeline option -- I havent studied it all enough yet. Thanks
------------------------------------------------------------------------------
_______________________________________________ Semediawiki-devel mailing list Semediawiki-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/semediawiki-devel
