Semantic Mediawiki and the Semantic Web

From ZOOiD Wiki
(Difference between revisions)
Jump to: navigation, search
 
(3 intermediate revisions by 2 users not shown)
Line 1: Line 1:
Following Web development for 15 years, the Semantic Web has always been in the background. Today XML is commonly used as an interchange language between applications, Web Services are used by systems requiring rich data exchange, and REST is used as a lighter weight exchange system. All these elements contribute to the SemWeb. Yet providing a practical way to create semantic documents is difficult for the typical end user. Most SemWeb approaches use very explicit, requiring linked codes that are painful to enter, so clunky forms based interfaces are often used to develop documents.
+
Following Web development for 15 years, the Semantic Web has always been in the background. Today XML is commonly used as an interchange language between applications, Web Services are used by systems requiring rich data exchange, and REST is used as a lighter weight exchange system. All these elements contribute to a web of reusable information. Yet providing a practical way to create semantic documents is difficult for the typical end user. Most approaches use very explicit terminology, requiring linked codes that are painful to enter, so clunky forms based interfaces are often used to develop documents.
  
Contrast this with the fluidity of wikis, a giant force in the development of the participatory Web. A classic wiki allows anyone to edit pages, with a full 'audit trail.' In creating those pages, hypertext databases can be easily created, with conventions allowing easy organization of documents, and functions like "what links here" enable discovery navigation.
+
Contrast this with the fluidity of wikis, a giant force in the development of the participatory Web. A classic wiki allows anyone to edit pages, with a full 'audit trail.' In creating those pages, hypertext page sets can be easily created, with conventions allowing easy organization of documents, and functions like "what links here" enable discovery navigation.
  
However, to best use a wiki today (rather than using it as a Web based version of MS Word with hyperlinks), one often should use the low level wiki markup. Many people are afraid of working in text, but it adds a lot of fluidity. Over time, we should start to see better 'rich' interfaces, as well as the common pattern of an inexperienced user adding some information, and an expert adding semantic markup. But it's always going to be a benefit to have an idea of how the underlying markup works, similar to how a Web developer knows how a Web page is composed.
+
To best use a wiki today (rather than using it as a Web based version of MS Word), one often should use the low level wiki markup. Many people are afraid of working in text, but it adds a lot of fluidity. Over time, better 'rich' interfaces will evolve, as well as the common pattern of an inexperienced user adding some information, and an expert adding semantic markup. But it's always going to be a benefit — digital literacy — to have an idea of how the underlying markup works.
  
As an example, Wikipedia allows easily adding categories; the corpus can then be organized from any perspective. A [http://en.wikipedia.org/wiki/Phyllis_Konstam random article] is not just about an actress, it is also about [http://en.wikipedia.org/wiki/Category:1907_births 1907 births], [http://en.wikipedia.org/wiki/Category:1976_deaths 1976 deaths], and [http://en.wikipedia.org/wiki/Category:Deaths_from_myocardial_infarction deaths from myocardial infarction].
+
As an example, Wikipedia allows easily adding categories; documents can then be organized from any perspective. A [http://en.wikipedia.org/wiki/Phyllis_Konstam random article] is not just about an actress, it is also about [http://en.wikipedia.org/wiki/Category:1907_births 1907 births], [http://en.wikipedia.org/wiki/Category:1976_deaths 1976 deaths], and [http://en.wikipedia.org/wiki/Category:Deaths_from_myocardial_infarction deaths from myocardial infarction].
  
 
Using properties and relationships, Semantic Mediawiki takes this one giant step farther.
 
Using properties and relationships, Semantic Mediawiki takes this one giant step farther.
  
Looking at the following text, we see lots of opportunties for markup:
+
{{Next|SMW properties}}
  
  Phyllis Konstam (14 April 1907 – 20 August 1976)
+
[[Category:SemWeb]]
  was an English film actress.
+
  She was born in London and died in Somerset
+
  from a heart attack.
+
  
In markup, this can look like:
+
{{Blikied|Oct 1, 2009}}
 
+
  <nowiki>Phyllis Konstam ([[born::14 April 1907]] – [[died::20 August 1976]])
+
  was an [[is from: England | English]] [[is a::film actress]].
+
  She was born in [[born in::London]] and died in [[died in::Somerset]]
+
  from a [[died of::heart attack]].</nowiki>
+
 
+
Oh no! Look at all those strange symbols! Well, actually there are just a few (and there's a forms-based interface as well). Not only do you not have to add your subject to each of those categories, anyone can also re-use this information on other pages, for embedded queries and views, calculations, and so on.
+
 
+
{{ #ask: [[born::+]]
+
|?born
+
|?died
+
|?died in
+
|?died of
+
}}
+
 
+
The above inline query is phrased as follows:
+
 
+
  <nowiki> {{ #ask: [[born::+]] <-- ask for all entities that have a born field
+
  |?born
+
  |?died
+
  |?died in <-- include these ?fields in the output
+
  |?died of
+
  }}</nowiki>
+
 
+
The query will always show the latest information; you'll see some entries created later in these pages. Fields or parameters can be added easily. You can view the source (edit) of any page to see how queries are composed.
+
 
+
{{Next|SMW map}}
+
 
+
[[Category:SemWeb]]
+

Latest revision as of 14:29, 28 June 2012

Following Web development for 15 years, the Semantic Web has always been in the background. Today XML is commonly used as an interchange language between applications, Web Services are used by systems requiring rich data exchange, and REST is used as a lighter weight exchange system. All these elements contribute to a web of reusable information. Yet providing a practical way to create semantic documents is difficult for the typical end user. Most approaches use very explicit terminology, requiring linked codes that are painful to enter, so clunky forms based interfaces are often used to develop documents.

Contrast this with the fluidity of wikis, a giant force in the development of the participatory Web. A classic wiki allows anyone to edit pages, with a full 'audit trail.' In creating those pages, hypertext page sets can be easily created, with conventions allowing easy organization of documents, and functions like "what links here" enable discovery navigation.

To best use a wiki today (rather than using it as a Web based version of MS Word), one often should use the low level wiki markup. Many people are afraid of working in text, but it adds a lot of fluidity. Over time, better 'rich' interfaces will evolve, as well as the common pattern of an inexperienced user adding some information, and an expert adding semantic markup. But it's always going to be a benefit — digital literacy — to have an idea of how the underlying markup works.

As an example, Wikipedia allows easily adding categories; documents can then be organized from any perspective. A random article is not just about an actress, it is also about 1907 births, 1976 deaths, and deaths from myocardial infarction.

Using properties and relationships, Semantic Mediawiki takes this one giant step farther.

 Next: SMW properties



RSS

Blikied on Oct 1, 2009

Your comments would be appreciated, click on the Discussion tab or add them here.



Personal tools
Namespaces

Variants
Actions
Navigation
Tools