<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Kommentare zu: First KiWi Open Source Release!</title>
	<atom:link href="http://www.schaffert.eu/2009/02/27/first-kiwi-open-source-release/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.schaffert.eu/2009/02/27/first-kiwi-open-source-release/</link>
	<description>Homepage of Sebastian Schaffert</description>
	<lastBuildDate>Sat, 10 Sep 2011 20:28:38 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>Von: wastl</title>
		<link>http://www.schaffert.eu/2009/02/27/first-kiwi-open-source-release/comment-page-1/#comment-411</link>
		<dc:creator>wastl</dc:creator>
		<pubDate>Tue, 05 Jan 2010 20:28:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.schaffert.eu/?p=233#comment-411</guid>
		<description>Hi Josef! You are right to point out a certain contradiction; my reasons for using Wordpress on my homepage are: (1) Wordpress is very light weight, while KiWi is a full Java EE application; this has many advantages, but not for &quot;small&quot; installations like a homepage; in situations where you use Confluence or similar, you might also think about KiWi. (2) Wordpress is a finished and reliable product while KiWi is still a research prototype where the focus is not only on stability and usability but also on experimenting with new research ideas - I don&#039;t want to constantly bug fix my homepage :-). (3) The Wordpress team has more developers for the user interface alone than the KiWi project has altogether, so the overall usability of Wordpress is not easy to match. Still, we are working on it, and maybe in some months we have a KiWi release that is stable and usable enough to be used as a replacement for actual productive systems. We definately plan to do so after the end of the project.</description>
		<content:encoded><![CDATA[<p>Hi Josef! You are right to point out a certain contradiction; my reasons for using WordPress on my homepage are: (1) WordPress is very light weight, while KiWi is a full Java EE application; this has many advantages, but not for &#8220;small&#8221; installations like a homepage; in situations where you use Confluence or similar, you might also think about KiWi. (2) WordPress is a finished and reliable product while KiWi is still a research prototype where the focus is not only on stability and usability but also on experimenting with new research ideas &#8211; I don&#8217;t want to constantly bug fix my homepage <img src='http://www.schaffert.eu/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> . (3) The WordPress team has more developers for the user interface alone than the KiWi project has altogether, so the overall usability of WordPress is not easy to match. Still, we are working on it, and maybe in some months we have a KiWi release that is stable and usable enough to be used as a replacement for actual productive systems. We definately plan to do so after the end of the project.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Von: Josef Noll</title>
		<link>http://www.schaffert.eu/2009/02/27/first-kiwi-open-source-release/comment-page-1/#comment-410</link>
		<dc:creator>Josef Noll</dc:creator>
		<pubDate>Tue, 05 Jan 2010 19:55:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.schaffert.eu/?p=233#comment-410</guid>
		<description>Sebastian, 
first shot is very impressive... really what we are looking for in Movation (http://www.movation.no, company for open innovation in mobile services). 

But why do you use Wordpress for your home page, and not Kiwi?
I&#039;m exactly there, where I need a &quot;frond-end&quot; which is looking professional (like WordPress) while the information is semantically annotated (as in Kiwi). Any suggestion?
Josef</description>
		<content:encoded><![CDATA[<p>Sebastian,<br />
first shot is very impressive&#8230; really what we are looking for in Movation (<a href="http://www.movation.no" rel="nofollow">http://www.movation.no</a>, company for open innovation in mobile services). </p>
<p>But why do you use WordPress for your home page, and not Kiwi?<br />
I&#8217;m exactly there, where I need a &#8220;frond-end&#8221; which is looking professional (like WordPress) while the information is semantically annotated (as in Kiwi). Any suggestion?<br />
Josef</p>
]]></content:encoded>
	</item>
	<item>
		<title>Von: wastl</title>
		<link>http://www.schaffert.eu/2009/02/27/first-kiwi-open-source-release/comment-page-1/#comment-224</link>
		<dc:creator>wastl</dc:creator>
		<pubDate>Sun, 01 Mar 2009 20:43:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.schaffert.eu/?p=233#comment-224</guid>
		<description>Of course there will is still the possibility to do manual triple store queries - for the most common cases you just don&#039;t need to do them. SPARQL endpoint is not yet complete, but we are working on it. We&#039;d like to get rid of Sesame first and map SPARQL to our own triple store. If you are really willing to jump on board and port SWiM, we&#039;ll do our best to try to help you. Although KiWi does not share much code with IkeWiki, many of the general principles are the same, and I am sure you&#039;ll like the component- and service-based structure offered by KiWi.</description>
		<content:encoded><![CDATA[<p>Of course there will is still the possibility to do manual triple store queries &#8211; for the most common cases you just don&#8217;t need to do them. SPARQL endpoint is not yet complete, but we are working on it. We&#8217;d like to get rid of Sesame first and map SPARQL to our own triple store. If you are really willing to jump on board and port SWiM, we&#8217;ll do our best to try to help you. Although KiWi does not share much code with IkeWiki, many of the general principles are the same, and I am sure you&#8217;ll like the component- and service-based structure offered by KiWi.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Von: Christoph Lange</title>
		<link>http://www.schaffert.eu/2009/02/27/first-kiwi-open-source-release/comment-page-1/#comment-221</link>
		<dc:creator>Christoph Lange</dc:creator>
		<pubDate>Fri, 27 Feb 2009 23:17:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.schaffert.eu/?p=233#comment-221</guid>
		<description>Congratulations on the release! Let me give some comments and ask some questions here, maybe they are also interesting for others:

No more manual triple store queries? But I hope they are still possible, in case I want to do something that is not possible with the current Java interface.

Linked open data server: Nice! Do you also have a SPARQL endpoint?

You misspelled the svn URL (kWi -&gt; KiWi)

Good that one is no longer tied to PostgreSQL.

Not yet sure about the concrete schedule, as I have a lot of things to do (such as getting my Ph.D. done by the end of this year), but I will have a deeper look into KiWi quite soon and figure out how to port SWiM (the math extension to IkeWiki) to it.

Keep it up!</description>
		<content:encoded><![CDATA[<p>Congratulations on the release! Let me give some comments and ask some questions here, maybe they are also interesting for others:</p>
<p>No more manual triple store queries? But I hope they are still possible, in case I want to do something that is not possible with the current Java interface.</p>
<p>Linked open data server: Nice! Do you also have a SPARQL endpoint?</p>
<p>You misspelled the svn URL (kWi -&gt; KiWi)</p>
<p>Good that one is no longer tied to PostgreSQL.</p>
<p>Not yet sure about the concrete schedule, as I have a lot of things to do (such as getting my Ph.D. done by the end of this year), but I will have a deeper look into KiWi quite soon and figure out how to port SWiM (the math extension to IkeWiki) to it.</p>
<p>Keep it up!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

