Thanks to Sergey Chernyshev, I got a chance to see Microsoft SharePoint for myself last week; he was nice enough to show me a lot of the interface. Or rather, what he demo’d one of the two applications referred to as “SharePoint” - it’s still a little confusing to me, but I believe what he showed me was Windows SharePoint Services, as opposed to “SharePoint Server”. That’s good, because I believe that’s the application usually referred to as a competitor for Semantic MediaWiki. Anyway, seeing the SharePoint I saw, I could certainly understand how comparisons were being made. Windows SharePoint is all about collaborative data - users can create their own page types, with each page containing a set of fields; once you’ve created a page, there’s an automatic form created to let everyone add or edit data. Finally, there are “views” one can create, which are the equivalent of SMW’s queries - you can filter a set of pages by some set of criteria, and decide how to display the pages; just as with SMW, you can make tables, calendars, etc.
SharePoint is really closer to something like a set of public Excel spreadsheets with macros for entering data, or sites like Dabble DB, than to Semantic MediaWiki; with the caveat that SharePoint allows for uploading external files in a manner similar to MediaWiki. There are a few key differences that I can see. First the strengths of SharePoint:
- SharePoint allows for data permissions. You can set who can read and edit and who can’t for nearly each piece of data. At this point, that’s possible only through hacks with MediaWiki, and not at all with Semantic MediaWiki - basically, if someone can read any page on a wiki, they can pretty much read all of it. Is that a big advantage for SharePoint? I’m sure there are a lot of companies that see it that way.
- SharePoint’s interface is very easy to understand. If you want to create a new type of page, there’s a nice wizard that guides you through it in a few easy steps. Pages are “pages”, views are “views”, and that’s all there is to it - there’s no need to understand templates, properties, parser functions or anything else, and the word “semantic” is blissfully out of sight. Contrast that, sadly, with Semantic MediaWiki, where even if you know how wikis work, you still have to spend, I would guess, at least an hour or two reading documentation before you can do a thing.
And the weaknesses:
- SharePoint has no versioning. It is not a wiki. You can’t tell who made which changes to which data and when, and I believe that once a piece of data has been changed its old value is lost forever, except maybe in database archives. As the number of people who can modify a set of information grows, the value of complete versioning grows as well, until you reach the point when you literally can’t function without a record of every single change that was made. That, I think, is a big part of why permissions are so important in applications like SharePoint: you always have to keep the number of people who can change any piece of data to a manageable size; say a few dozen or a few hundred at the very most. Of course, companies can manage this way (they’ve been doing it for hundreds of years), but it’s not ideal.
- In SharePoint, you can’t link data. Every field in a page is a standalone field. If you have a page representing a project, and there’s a field representing the project manager, and that field reads “Bob Hoover”, it’s just a string of letters. It won’t link to a page representing Bob, and there will be no way to connect that information about Bob to anything else we know about him. Yes, you can create a view to find out all the projects that are managed by Bob Hoover, but you can’t go to a page about him and see which projects he manages, plus which other projects he’s a part of, plus his phone number, plus which days he’s willing to carpool. In Semantic MediaWiki, that’s all easy to do.
Note that I’m just comparing the interfaces here - there are obviously huge differences in price, support, etc. etc., but I wanted to give my sense about the applications themselves.
1f94