<?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>Comments on: Triplify &#8211; expose semantics!</title>
	<atom:link href="http://blog.aksw.org/2008/triplify-expose-semantics/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.aksw.org/2008/triplify-expose-semantics/</link>
	<description>The shared AKSW blog about our projects and the Semantic Web.</description>
	<lastBuildDate>Thu, 02 Feb 2012 19:02:27 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
	<item>
		<title>By: Planeta Web SemÃ¡ntica &#187; Blog Archive &#187; Entender la web semÃ¡ntica a travÃ©s de las nuevas herramientas</title>
		<link>http://blog.aksw.org/2008/triplify-expose-semantics/#comment-5170</link>
		<dc:creator>Planeta Web SemÃ¡ntica &#187; Blog Archive &#187; Entender la web semÃ¡ntica a travÃ©s de las nuevas herramientas</dc:creator>
		<pubDate>Sun, 11 May 2008 13:48:02 +0000</pubDate>
		<guid isPermaLink="false">http://blog.aksw.org/2008/triplify-expose-semantics/#comment-5170</guid>
		<description>[...] os aconsejo, de momento, su instalaciÃ³n. PrevÃ©n el lanzamiento de su primera versiÃ³n pÃºblica (que tal vez soluciones los problemas con la privacidad de los que alertan) en [...]</description>
		<content:encoded><![CDATA[<p>[...] os aconsejo, de momento, su instalaciÃ³n. PrevÃ©n el lanzamiento de su primera versiÃ³n pÃºblica (que tal vez soluciones los problemas con la privacidad de los que alertan) en [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sören Auer</title>
		<link>http://blog.aksw.org/2008/triplify-expose-semantics/#comment-4670</link>
		<dc:creator>Sören Auer</dc:creator>
		<pubDate>Sun, 23 Mar 2008 13:06:32 +0000</pubDate>
		<guid isPermaLink="false">http://blog.aksw.org/2008/triplify-expose-semantics/#comment-4670</guid>
		<description>Dear Dreig,

Could you please give us some more information, what exactly happens? Which PHP version is installed on your Webspace (easy to find out with the function php_info()). You are saying it works with WordPress 2.3.1 but not with 2.2? That would be hard to belive, since the line your error message points to is in no way related to the WordPress version.

Sören</description>
		<content:encoded><![CDATA[<p>Dear Dreig,</p>
<p>Could you please give us some more information, what exactly happens? Which PHP version is installed on your Webspace (easy to find out with the function php_info()). You are saying it works with WordPress 2.3.1 but not with 2.2? That would be hard to belive, since the line your error message points to is in no way related to the WordPress version.</p>
<p>Sören</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dreig</title>
		<link>http://blog.aksw.org/2008/triplify-expose-semantics/#comment-4638</link>
		<dc:creator>dreig</dc:creator>
		<pubDate>Sun, 23 Mar 2008 07:01:05 +0000</pubDate>
		<guid isPermaLink="false">http://blog.aksw.org/2008/triplify-expose-semantics/#comment-4638</guid>
		<description>IÂ´m gonna write about triplifly on my blog but iÂ´ve done some testing on it and i obtain an error: syntax error, unexpected &#039;,&#039;, expecting &#039;(&#039; in /data/members/paid/d/r/dreig.eu/htdocs/www/caparazon/triplify/index.php on line 70
This is a 2.2 installation.

It runs correctly on 2.3.1. 

Could it be solved?

thanks</description>
		<content:encoded><![CDATA[<p>IÂ´m gonna write about triplifly on my blog but iÂ´ve done some testing on it and i obtain an error: syntax error, unexpected &#8216;,&#8217;, expecting &#8216;(&#8216; in /data/members/paid/d/r/dreig.eu/htdocs/www/caparazon/triplify/index.php on line 70<br />
This is a 2.2 installation.</p>
<p>It runs correctly on 2.3.1. </p>
<p>Could it be solved?</p>
<p>thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sören Auer</title>
		<link>http://blog.aksw.org/2008/triplify-expose-semantics/#comment-4296</link>
		<dc:creator>Sören Auer</dc:creator>
		<pubDate>Thu, 20 Mar 2008 14:35:10 +0000</pubDate>
		<guid isPermaLink="false">http://blog.aksw.org/2008/triplify-expose-semantics/#comment-4296</guid>
		<description>Thanks a lot Rolf - excellent job, this will be added to the next release!</description>
		<content:encoded><![CDATA[<p>Thanks a lot Rolf &#8211; excellent job, this will be added to the next release!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rolf Strathewerd</title>
		<link>http://blog.aksw.org/2008/triplify-expose-semantics/#comment-4295</link>
		<dc:creator>Rolf Strathewerd</dc:creator>
		<pubDate>Thu, 20 Mar 2008 14:25:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.aksw.org/2008/triplify-expose-semantics/#comment-4295</guid>
		<description>Wonderfull little toolkit. The Config-File for Wordpress 2.1 also works for Wordpress 2.3.3. I had only one problem: my database encoding is not UTF-8. So I made a brute-force-patch in index.php

function makeTriples($cl,$class,$dtypes) {
....
                foreach($cl as $p=&gt;$val) if($val &amp;&amp; ($dtypes[$p]!=&#039;xsd:dateTime&#039;&#124;&#124;$val!=&#039;0000-00-00 00:00:00&#039;)) {
                       $val=utf8_encode($val);  // ADDED LINE
                        if(strpos($p,&#039;^^&#039;)) {
....

Of course a config parameter would be better</description>
		<content:encoded><![CDATA[<p>Wonderfull little toolkit. The Config-File for WordPress 2.1 also works for WordPress 2.3.3. I had only one problem: my database encoding is not UTF-8. So I made a brute-force-patch in index.php</p>
<p>function makeTriples($cl,$class,$dtypes) {<br />
&#8230;.<br />
                foreach($cl as $p=&gt;$val) if($val &amp;&amp; ($dtypes[$p]!=&#8217;xsd:dateTime&#8217;||$val!=&#8217;0000-00-00 00:00:00&#8242;)) {<br />
                       $val=utf8_encode($val);  // ADDED LINE<br />
                        if(strpos($p,&#8217;^^&#8217;)) {<br />
&#8230;.</p>
<p>Of course a config parameter would be better</p>
]]></content:encoded>
	</item>
</channel>
</rss>

