<?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"
	>
<channel>
	<title>Comments on: Less code: eRDF templates for RDF-driven web sites</title>
	<atom:link href="http://dowhatimean.net/2007/03/less-code-erdf-templates-for-rdf-driven-web-sites/feed" rel="self" type="application/rss+xml" />
	<link>http://dowhatimean.net/2007/03/less-code-erdf-templates-for-rdf-driven-web-sites</link>
	<description>Richard Cyganiak's Weblog</description>
	<pubDate>Thu, 09 Sep 2010 20:47:56 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Keith Alexander</title>
		<link>http://dowhatimean.net/2007/03/less-code-erdf-templates-for-rdf-driven-web-sites#comment-48460</link>
		<dc:creator>Keith Alexander</dc:creator>
		<pubDate>Thu, 15 Mar 2007 14:23:59 +0000</pubDate>
		<guid isPermaLink="false">http://dowhatimean.net/2007/03/less-code-erdf-templates-for-rdf-driven-web-sites#comment-48460</guid>
		<description>&lt;p&gt;Thanks for the write-up  Richard. Another idea in my code (which complements the semantic templating, and also aims to diminish coding without diminishing developer control) is for a generic form processor: you write the form elements name attributes as associative array keys which reflect an RDF/XML like structure, and use special class names to tell the processor which functions the input value should be passed through.&lt;/p&gt;

&lt;p&gt;Post the form to the same url as the page it appears on, and the processor will parse the xhtml page to retrieve (only) the expected name =&#62; values, and pass them through the functions (which the developer can write) specified in the class attribute. If the form processes without errors, the resulting array can be saved to the RDF store.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Thanks for the write-up  Richard. Another idea in my code (which complements the semantic templating, and also aims to diminish coding without diminishing developer control) is for a generic form processor: you write the form elements name attributes as associative array keys which reflect an RDF/XML like structure, and use special class names to tell the processor which functions the input value should be passed through.</p>

<p>Post the form to the same url as the page it appears on, and the processor will parse the xhtml page to retrieve (only) the expected name =&gt; values, and pass them through the functions (which the developer can write) specified in the class attribute. If the form processes without errors, the resulting array can be saved to the RDF store.</p>]]></content:encoded>
	</item>
</channel>
</rss>
