Don't want to interfere your in-depth discussion too much with my
general comments. I see you point now, Yaron. But it is only true if
you think as ratings of pages. I'd rather see them as rating the ting
that is described on the page. On of my wikis is about projects that
were submitted to an award. A rating would not rate the quality of the
page (a good or a bad description of the project), but the project
itself: is it more interesting than other? Is it a best-practice?
Mediocre projects can be described very well and very interesting
projects can be described very poorly...

Even when somebody dislikes a page you are right, it would be better
to improve it, but it could be possible that an admin has protected a
page and regular users can not improve it, but they could rate it (so
admins would have a sense on what pages should be improved with a
higher priority). Other use cases are sites where Semantic MediaWiki
is used as an online database rather than a real wiki. Look at
http://www.epsa-projects.com. It is no wiki, as it is not possible to
edit the content except for admins. So there is no real wiki approach
behind it, but still the used software makes a great page.

> 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.

This sounds like something I should try out one day...
- Bernhard

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to