Semantic Mediawiki and the Semantic Web: Difference between revisions

Jump to navigation Jump to search
no edit summary
No edit summary
No edit summary
Line 5: Line 5:
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.
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.


As an example, Wikipedia allows easily adding categories, which adds an incredible value to pages. The corpus becomes a set of resources that can 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; 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].


Semantic Mediawiki takes this one step farther, so that the encodings apply directly to the text. Rather than adding a category, one adds a property or relationship.
Using properties and relationships, Semantic Mediawiki takes this one giant step farther.


Looking at the following text, we see lots of opportunties for markup:
Looking at the following text, we see lots of opportunties for markup:
Line 23: Line 23:
   from a [[died of::heart attack]].</nowiki>
   from a [[died of::heart attack]].</nowiki>


Oh no! Look at all those strange symbols! Well, actually there are just a few and they add a lot of value (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.
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.
 
I've entered actors using the above syntax. I can query them in embedded views:


{{ #ask: [[born::+]]
{{ #ask: [[born::+]]
Line 34: Line 32:
}}
}}


The query is phrased as follows:
The above inline query is phrased as follows:


   <nowiki> {{ #ask: [[born::+]] <-- ask for all entities that have a born field
   <nowiki> {{ #ask: [[born::+]] <-- ask for all entities that have a born field
Line 43: Line 41:
   }}</nowiki>
   }}</nowiki>


The query will always show the latest information, you'll also 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.  
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}}
{{Next|SMW map}}


[[Category:SemWeb]]
[[Category:SemWeb]]

Navigation menu