<?xml version="1.0"?>
<rss version="2.0">
	<channel>
		<title>Forum posts to 'Project Ideas'</title>
		<link>http://www.open-innovation-projects.org/project-ideas/</link>
		

		
		<item>
			<title>Open Source Lighting System</title>
			<link>http://www.open-innovation-projects.org/project-ideas/show/82</link>
			<description>&lt;p&gt;I have a design that is already at a prototype stage. I need help as the idea is to provide a system to provide modern residential lightging system. The whole industry is choked with IP, protocols and licensing agreements.&lt;/p&gt;&lt;p&gt;I have a design to provide a system that scales from residential to large commercial concerns. It provides a series of common building block components to enable a low cost net work via a protocol specifically designed for lighting control. Its main design goal is to provide cheap inteligent control systems with energy savings in excess of 80%.&lt;/p&gt;&lt;p&gt;I need help as my background is with embedded and network control protocols. Firstly chosing a GPL and protection or at least the ability to stop the design being bastardised for comercial gain needs to be discussed.&lt;/p&gt;&lt;p&gt;What I mean if the standard is released with a plethora of non compatible protocol modifictions then the design would be dead in the water.&lt;/p&gt;&lt;p&gt;Is there a open GPL that allows cottage industries to manufacture limited(generous) qty of the design but would require low bulk manufacturing licences. I am open to any sugestions.&lt;/p&gt;&lt;p&gt;In terms of communication I have a hybrid powerline that is unique in implementation as it cost requirements use low-end Lin_Bus microcontrollers to provide a hireachy of simple intelligence that scales to the future of modern intelligent lighting control.&lt;/p&gt;&lt;p&gt;&lt;/p&gt;&lt;br&gt;&lt;br&gt;Posted to: Open Source Lighting System</description>
			<pubDate>Tue, 21 Apr 2009 22:15:43 +0200</pubDate>
			<author>stuart naylor</author>
			<guid>http://www.open-innovation-projects.org/project-ideas/show/82</guid>
		</item>
		
		<item>
			<title>Creative and Innovative Business Solutions</title>
			<link>http://www.open-innovation-projects.org/project-ideas/show/76</link>
			<description>&lt;p&gt;Dear Enthusiasts of Open Development,&lt;/p&gt;&lt;p&gt;INNOVATION is everyone's business and we all know that! &lt;br /&gt;So why not share our knowledge, expertise, experiences, ideas and/or expectations about creative and innovative approaches to business services, already existing ones and not yet thought of...&lt;br /&gt;Out of these awesome ideas new projects may come up and this is always worth talking about!&lt;/p&gt;&lt;p&gt;Looking forward to getting creative with you!&lt;/p&gt;&lt;p&gt;Yours sincerely,&lt;/p&gt;&lt;p&gt;Aleksandra Kalinowska&lt;br /&gt;Founder/Owner/CEO&lt;/p&gt;&lt;p&gt;&lt;a href=&quot;http://www.e-innovations.info/&quot;&gt;European Innovations Consulting&lt;/a&gt;&lt;br /&gt;&lt;a href=&quot;mailto:office@e-innovations.info&quot;&gt;office@e-innovations.info&lt;/a&gt;&lt;br /&gt;&lt;/p&gt;&lt;br&gt;&lt;br&gt;Posted to: Creative and Innovative Business Solutions</description>
			<pubDate>Sat, 07 Mar 2009 21:01:54 +0100</pubDate>
			<author>Aleksandra  Kalinowska</author>
			<guid>http://www.open-innovation-projects.org/project-ideas/show/76</guid>
		</item>
		
		<item>
			<title>Open Source Technical Documentation</title>
			<link>http://www.open-innovation-projects.org/project-ideas/show/62</link>
			<description>&lt;p&gt;Hi @ all,&lt;/p&gt;&lt;p&gt;for some time now, I have been thinking about the feasibility of &quot;Open Source Technical Documentation&quot; or, OSTD.&lt;/p&gt;&lt;p&gt;What made me think this could be a good idea was the observation, that manuals (for whatever product...) always contain some or all of the following content:&lt;br /&gt;- About this manual&lt;br /&gt;- Warranty issues&lt;br /&gt;- Signs and Symbols used&lt;br /&gt;- Various warnings, such as &quot;caution, hot, do not touch&quot; or the like.&lt;/p&gt;&lt;p&gt;My idea of OSTD would be to make such content publicly available, e.g. in DITA-XML or LaTex or ... file formats, so that the maintenance could be handled by a community.&lt;/p&gt;&lt;p&gt;&amp;lt;edit&amp;gt;&lt;br /&gt;You might say &quot;Already right in place, it's called GFDL&quot;.&lt;br /&gt;My idea is not about the grassroot-style collaborative creation of new content, but about making available existing content.&lt;br /&gt;I have seen manuals for OSS, e.g., Gimp.&lt;br /&gt;These are written quite well, but unfortunately do not comply with any regulations, such as ANSI or DIN.&lt;br /&gt;&amp;lt;/edit)&lt;/p&gt;&lt;p&gt;Feedback welcome!&lt;/p&gt;&lt;p&gt;-Marty&lt;/p&gt;&lt;br&gt;&lt;br&gt;Posted to: Open Source Technical Documentation</description>
			<pubDate>Sat, 24 Jan 2009 19:07:22 +0100</pubDate>
			<author>Martin Brüggemann</author>
			<guid>http://www.open-innovation-projects.org/project-ideas/show/62</guid>
		</item>
		

	</channel>
</rss>

