Well, I should have been more precise in my statement, since features like ratings can cover a wide variety of uses. On the one hand, you can have users expressing what activities and such they're interested in, and having that recorded on their user pages. That's an expression of real-world information, and it's totally appropriate to store such data semantically - that's how ardorado.com works, for instance. On the other extreme, there's "I found this help page useful/not useful". That's purely wiki-based information, and I think part of the reason I'm against storing it semantically is that I just don't think it makes that much sense in wikis in general, semantic or otherwise. Given that articles are changing all the time, how helpful is it to know that someone gave an article a certain rating six months ago? In addition, if someone's unhappy with a page, giving it a low rating is pretty much the least helpful thing they can do - ideally, they should try to improve the page, but even if they don't want to, they can write in the talk page about the specific problems they think the page has.
Then there are the in-between cases, like a wiki about movies, where anyone who visits the wiki can give a rating to any movie, and the wiki averages out everyone's ratings. There are various technical issues that make this difficult to implement in SMW and SF, but equally importantly, I just don't see this in the same "universe" of information as data like the movie's director, actors, etc. Querying it alongside real data seems odd to me. I know other people have different opinions on this. I should note that for cases like that, if you really want to query the data, a good long-term solution might be to try to use the External Data extension to get the ratings data stored by the specialized ratings extension, then store it semantically and query it; instead of trying to use SF in some roundabout way. But I don't know if that's feasible right now. Which brings us back to the original example, about boats. Thinking about it more now, what I might actually suggest is to take the approach ardorado.comtakes - store the information on user pages, instead of on the boat pages. Of course, it's a little trickier to put in an "add to my favorites" link on a boat page, that edits the user page; but it's doable - maybe Sergey can even send you the custom code they created for their site. :) I believe it involved the POM extension. -Yaron On Thu, Jul 16, 2009 at 9:45 PM, Bernhard Krabina <krab...@kdz.or.at> wrote: > > by the way, I think "Modification date" is a great property, my vote > goes for more of such built in properties, e. g. "Number of views", > "Number of revisions".... > > :-) > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Semantic Forms" group. To post to this group, send email to semantic-forms@googlegroups.com To unsubscribe from this group, send email to semantic-forms+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/semantic-forms?hl=en -~----------~----~----~----~------~----~------~--~---
