<?xml version="1.0" encoding="utf-8"?><!-- generator="wordpress/2.3.3" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: SPARUL—SPARQL Update Language</title>
	<link>http://dowhatimean.net/2007/03/sparul%e2%80%94sparql-update-language</link>
	<description>Richard Cyganiak's Weblog</description>
	<pubDate>Mon, 13 Oct 2008 15:52:42 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
		<item>
		<title>By: saranya</title>
		<link>http://dowhatimean.net/2007/03/sparul%e2%80%94sparql-update-language#comment-175270</link>
		<dc:creator>saranya</dc:creator>
		<pubDate>Tue, 17 Jun 2008 09:27:48 +0000</pubDate>
		<guid>http://dowhatimean.net/2007/03/sparul%e2%80%94sparql-update-language#comment-175270</guid>
		<description>&lt;p&gt;I am creating rdf files for mailitems.&lt;/p&gt;

&lt;p&gt;Instead of recreating the entire RDF file is it possible to insert the rdfs for the newmail. Does such a query exixts&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I am creating rdf files for mailitems.</p>

<p>Instead of recreating the entire RDF file is it possible to insert the rdfs for the newmail. Does such a query exixts</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Richard Cyganiak</title>
		<link>http://dowhatimean.net/2007/03/sparul%e2%80%94sparql-update-language#comment-47863</link>
		<dc:creator>Richard Cyganiak</dc:creator>
		<pubDate>Sun, 11 Mar 2007 20:59:32 +0000</pubDate>
		<guid>http://dowhatimean.net/2007/03/sparul%e2%80%94sparql-update-language#comment-47863</guid>
		<description>&lt;p&gt;@Denny: RDF is just the data format, i.e. payload. We are talking protocols here. We need a clear and explicit specification of what kind of message a certain service can process. POST itself doesn&#8217;t constrain the message in any way. PUT, on the other hand, provides a clear specification: The state of the document is to be replaced with the payload. Simple and clear, but unfortunately not applicable to all situations.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>@Denny: RDF is just the data format, i.e. payload. We are talking protocols here. We need a clear and explicit specification of what kind of message a certain service can process. POST itself doesn&#8217;t constrain the message in any way. PUT, on the other hand, provides a clear specification: The state of the document is to be replaced with the payload. Simple and clear, but unfortunately not applicable to all situations.</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Denny Vrandecic</title>
		<link>http://dowhatimean.net/2007/03/sparul%e2%80%94sparql-update-language#comment-47849</link>
		<dc:creator>Denny Vrandecic</dc:creator>
		<pubDate>Sun, 11 Mar 2007 17:30:04 +0000</pubDate>
		<guid>http://dowhatimean.net/2007/03/sparul%e2%80%94sparql-update-language#comment-47849</guid>
		<description>&lt;p&gt;Isn&#8217;t the whole idea of RDF that it is clear and explicit and machine-interpretable?&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Isn&#8217;t the whole idea of RDF that it is clear and explicit and machine-interpretable?</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Richard Cyganiak</title>
		<link>http://dowhatimean.net/2007/03/sparul%e2%80%94sparql-update-language#comment-47840</link>
		<dc:creator>Richard Cyganiak</dc:creator>
		<pubDate>Sun, 11 Mar 2007 16:42:44 +0000</pubDate>
		<guid>http://dowhatimean.net/2007/03/sparul%e2%80%94sparql-update-language#comment-47840</guid>
		<description>&lt;p&gt;@Denny: On the traditional web, updates are done mostly using FTP or POST through forms. HTTP PUT in its pure form is used almost nowhere, except in WebDAV which is fairly widely used among web pros. PUT has also seen some uptake in the context of REST, as part of Web 2.0 APIs.&lt;/p&gt;

&lt;p&gt;On the SemWeb, the context is quite different, we want to be able to do updates in a fairly automated fashion without knowing much about the internals of the updated system. FTP is not good here. POST only works when you have a clear and explicit and machine-interpretable specification of what to send. On the traditional web, these specification are the HTML forms. I don&#8217;t know what the SemWeb equivalent will be. Semantic Web Services? Something like Mark Baker&#8217;s RDF Forms?&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>@Denny: On the traditional web, updates are done mostly using FTP or POST through forms. HTTP PUT in its pure form is used almost nowhere, except in WebDAV which is fairly widely used among web pros. PUT has also seen some uptake in the context of REST, as part of Web 2.0 APIs.</p>

<p>On the SemWeb, the context is quite different, we want to be able to do updates in a fairly automated fashion without knowing much about the internals of the updated system. FTP is not good here. POST only works when you have a clear and explicit and machine-interpretable specification of what to send. On the traditional web, these specification are the HTML forms. I don&#8217;t know what the SemWeb equivalent will be. Semantic Web Services? Something like Mark Baker&#8217;s RDF Forms?</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Denny Vrandecic</title>
		<link>http://dowhatimean.net/2007/03/sparul%e2%80%94sparql-update-language#comment-47738</link>
		<dc:creator>Denny Vrandecic</dc:creator>
		<pubDate>Sun, 11 Mar 2007 02:37:49 +0000</pubDate>
		<guid>http://dowhatimean.net/2007/03/sparul%e2%80%94sparql-update-language#comment-47738</guid>
		<description>&lt;p&gt;Just out of interest, is HTTP PUT actually widely used? For uploading data, I usually use FTP, or a web based system that usually uses POST, if not even GET. I know, it is applicable in theory, but in what circumstances is it actually applied in practice?&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Just out of interest, is HTTP PUT actually widely used? For uploading data, I usually use FTP, or a web based system that usually uses POST, if not even GET. I know, it is applicable in theory, but in what circumstances is it actually applied in practice?</p>]]></content:encoded>
	</item>
	<item>
		<title>By: Andy Seaborne</title>
		<link>http://dowhatimean.net/2007/03/sparul%e2%80%94sparql-update-language#comment-47453</link>
		<dc:creator>Andy Seaborne</dc:creator>
		<pubDate>Fri, 09 Mar 2007 18:05:09 +0000</pubDate>
		<guid>http://dowhatimean.net/2007/03/sparul%e2%80%94sparql-update-language#comment-47453</guid>
		<description>&lt;p&gt;The intent is teh modest one of local update.  Applications these days aren&#8217;t single programs, but several cooperating components connected by a local network even at a single site.&lt;/p&gt;

&lt;p&gt;&lt;span class='-linked-Data' title='http://seaborne.blogspot.com/2007/03/sparqlupdate.html' postaddress='http://dowhatimean.net/index.php?sioc_type=comment%26sioc_id=47453'&gt;&lt;a href='http://seaborne.blogspot.com/2007/03/sparqlupdate.html'&gt;http://seaborne.blogspot.com/2007/03/sparqlupdate.html&lt;/a&gt;&lt;/span&gt;&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>The intent is teh modest one of local update.  Applications these days aren&#8217;t single programs, but several cooperating components connected by a local network even at a single site.</p>

<p><span class='-linked-Data' title='http://seaborne.blogspot.com/2007/03/sparqlupdate.html' postaddress='http://dowhatimean.net/index.php?sioc_type=comment%26sioc_id=47453'><a href='http://seaborne.blogspot.com/2007/03/sparqlupdate.html'>http://seaborne.blogspot.com/2007/03/sparqlupdate.html</a></span></p>]]></content:encoded>
	</item>
</channel>
</rss>
