Semantic Mediawiki and the Semantic Web - Revision history

DavidM at 19:29, 28 June 2012

2012-06-28T19:29:36Z

@@ Line 9: / Line 9: @@
 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}}
 [[Category:SemWeb]]
 {{Blikied|Oct 1, 2009}}

DavidM at 19:37, 11 April 2010

2010-04-11T19:37:13Z

← Older revision		Revision as of 19:37, 11 April 2010
Line 46:		Line 46:

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

			{{Blikied\|Oct 1, 2009}}

DavidM at 15:19, 1 October 2009

2009-10-01T15:19:58Z

← Older revision		Revision as of 15:19, 1 October 2009
Line 3:		Line 3:
	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.		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.		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 [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].

24.200.170.79 at 13:16, 1 October 2009

2009-10-01T13:16:05Z

← Older revision		Revision as of 13:16, 1 October 2009
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.

DavidM at 14:56, 25 September 2009

2009-09-25T14:56:48Z

← Older revision		Revision as of 14:56, 25 September 2009
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]]

DavidM at 14:44, 25 September 2009

2009-09-25T14:44:42Z

← Older revision		Revision as of 14:44, 25 September 2009
Line 30:		Line 30:
	\|?born		\|?born
	\|?died		\|?died
	~~\|?is from~~
	\|?died in		\|?died in
	\|?died of		\|?died of
Line 40:		Line 39:
	\|?born		\|?born
	\|?died		\|?died
	~~\|?is from~~
	\|?died in <-- include these ?fields in the output		\|?died in <-- include these ?fields in the output
	\|?died of		\|?died of

DavidM at 14:38, 25 September 2009

2009-09-25T14:38:31Z

← Older revision		Revision as of 14:38, 25 September 2009
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 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.

	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. 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 databases 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.		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.
Line 8:		Line 8:

	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.		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.

			Looking at the following text, we see lots of opportunties for markup:

			Phyllis Konstam (14 April 1907 – 20 August 1976)
			was an English film actress.
			She was born in London and died in Somerset
			from a heart attack.

	In markup, this can look like:		In markup, this can look like:

	<nowiki>Phyllis Konstam ([[born::14 April 1907]] – [[died::20 August 1976]])		<nowiki>Phyllis Konstam ([[born::14 April 1907]] – [[died::20 August 1976]])
	was an [[is from: England \| English]] [[is a::film actress]].		was an [[is from: England \| English]] [[is a::film actress]].
	She was born in [[born in::London]] and died in [[died in::Somerset]]		She was born in [[born in::London]] and died in [[died in::Somerset]]
	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, ~~you~~ 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 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.

	I've entered actors using the above syntax. I can query them in embedded views:		I've entered actors using the above syntax. I can query them in embedded views:
Line 28:		Line 35:
	}}		}}

	The query will always show the latest information, you'll also see some entries created later in these pages. ~~View~~ the source (edit) of any page to see how queries are composed.		The query is phrased as follows:

			<nowiki> {{ #ask: [[born::+]] <-- ask for all entities that have a born field
			\|?born
			\|?died
			\|?is from
			\|?died in <-- include these ?fields in the output
			\|?died of
			}}</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.

	{{Next\|SMW map}}		{{Next\|SMW map}}

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

DavidM at 13:35, 25 September 2009

2009-09-25T13:35:51Z

← Older revision		Revision as of 13:35, 25 September 2009
Line 16:		Line 16:
	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. Not only do you not have to add your subject to each of those categories, you 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 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, you can also re-use this information on other pages, for embedded queries and views.

	I've entered actors using the above syntax. I can query them in embedded views:		I've entered actors using the above syntax. I can query them in embedded views:
Line 28:		Line 28:
	}}		}}

	The query will always show the latest information, you'll also see some entries created later in these pages. View the source (edit) ~~this~~ page to see how ~~it's~~ composed.		The query will always show the latest information, you'll also see some entries created later in these pages. View the source (edit) of any page to see how queries are composed.

	{{Next\|SMW map}}		{{Next\|SMW map}}

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

DavidM at 20:51, 24 September 2009

2009-09-24T20:51:31Z

← Older revision		Revision as of 20:51, 24 September 2009
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 ~~applications~~ 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 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.

	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. 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. 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.

DavidM at 20:31, 24 September 2009

2009-09-24T20:31:03Z

← Older revision		Revision as of 20:31, 24 September 2009
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 applications 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, linked codes that ~~would~~ 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 applications 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.

	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. In creating those pages, hypertext databases can be easily created, with conventions allowing easy organization of 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. 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.

	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, 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].