This is a comparison of how TOPS IWSS and Drupal are able to support our website feature proposals.
A message board can contain any number of topics, listed chronologically (newest first) by creation date.
Topics can contain any number of messages, listed chronologically (oldest first) by post date. Messages are posted to the topic, not as a reply to a specific message.
Messages have addresses (so they can be linked to), but the message's page does not indicate the topic it is a part of (there's no context).
Like the webpages they are a part of, discussions can be organized under any number of categories. This categorization also establishes the discussion's access permissions.
Categories, discussions, and individual comments, all have addresses (so they can be linked to).
We'll use the term subscribe here as the ability to be notified by email of discussion taking place on the website.
When a user accesses a website function, if the security level of the role assigned to the user is less than or equal to the security level assigned to the website function, access is granted, otherwise, denied.
To highlight one of the many differences between the two systems, suppose we have the roles, "web master" and "board member", and the website features, "tweak the website" and "view board minutes". How can we allow "webmasters" to "tweak the website" but not "view board minutes" and allow "board members" to "view board minutes" but not "tweak the website"? With TOPS IWSS, this cannot be done.
We'll use the term, revision control, here as the ability to track, and revert to, prior versions of an edited webpage.
In a collaborative (and even solitary) environment the possibility of reverting a webpage to a prior state is very valuable. For example, one may track the changes made by particular contributors, or quickly correct unintentional or malicious changes.
Unchecked content removal is also detrimental to collaboration: meaning is lost when references fail, users are discouraged when their contributions disappear, and no accountability can exist.
In this case, content is referred to using a link (by URL), but the content is protected (requires login). If the user is not already logged in (as will often be the case), what happens?
Referring to content using links is the key feature that makes the web so useful. Not being able to do so with protected content (requiring a login) would significantly reduce the usefulness of a website.
Recent comments
2011, January 26 - 5:04pm
2011, January 13 - 5:48pm
2010, March 12 - 12:53am
2010, March 11 - 9:49pm
2009, November 30 - 3:32pm
2009, November 30 - 3:09pm
2009, November 30 - 1:01pm
2009, November 30 - 10:50am
2009, November 30 - 10:29am
2009, November 29 - 10:15pm