2,150
edits
SMW Summary: Difference between revisions
Jump to navigation
Jump to search
→Summary
| Line 18: | Line 18: | ||
While Semantic Mediawiki is just one approach to SemWeb, it practically builds on the underlying principals of wikis and the most popular open source Wiki software that has many extensions and supporters and users, including Wikipedia. When Wikipedia flips a switch, all its data will become semantic (evidenced today in sites like [http://dbpedia.org DBPedia]) and the culture will evolve to expect more and more refined and re-usable data. | While Semantic Mediawiki is just one approach to SemWeb, it practically builds on the underlying principals of wikis and the most popular open source Wiki software that has many extensions and supporters and users, including Wikipedia. When Wikipedia flips a switch, all its data will become semantic (evidenced today in sites like [http://dbpedia.org DBPedia]) and the culture will evolve to expect more and more refined and re-usable data. | ||
Today we have a grab bag of standard | Today we have a grab bag of standard Web components. Semantic Wikis should '''not''' be thought of as another element. The list of blogs, CMSs, calendars, etc, etc can all be rolled up into a semantic wiki, with re-use of information throughout - add a query and view into your blog posting, add events to any document. | ||
Of course, other systems have and are gaining semantic features. But standard sites today are 'admin' managed. 'Users' on wiki sites also expect to participate more. They can create or augment data types and add their own views. They can use their own front ends to work with data. In fact, browsers tomorrow are expected to be more interactive and rely on server processing less - a server can just provide raw data, the application can be in the browser. | Of course, other systems have and are gaining semantic features. But standard sites today are 'admin' managed. 'Users' on wiki sites also expect to participate more. They can create or augment data types and add their own views. They can use their own front ends to work with data. In fact, browsers tomorrow are expected to be more interactive and rely on server processing less - a server can just provide raw data, the application can be in the browser. | ||