<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://wiki.opensourceecology.org/index.php?action=history&amp;feed=atom&amp;title=Open_Language_Standards</id>
	<title>Open Language Standards - Revision history</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.opensourceecology.org/index.php?action=history&amp;feed=atom&amp;title=Open_Language_Standards"/>
	<link rel="alternate" type="text/html" href="https://wiki.opensourceecology.org/index.php?title=Open_Language_Standards&amp;action=history"/>
	<updated>2026-04-13T01:52:03Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.39.13</generator>
	<entry>
		<id>https://wiki.opensourceecology.org/index.php?title=Open_Language_Standards&amp;diff=89691&amp;oldid=prev</id>
		<title>Marcin: Created page with &quot;Ok just set it up for emails as they are sent.   And yes it was the OSHW Documentation Jam, I see now that you&#039;re listed in the partners section.   I don&#039;t have time to go int...&quot;</title>
		<link rel="alternate" type="text/html" href="https://wiki.opensourceecology.org/index.php?title=Open_Language_Standards&amp;diff=89691&amp;oldid=prev"/>
		<updated>2013-03-18T16:57:50Z</updated>

		<summary type="html">&lt;p&gt;Created page with &amp;quot;Ok just set it up for emails as they are sent.   And yes it was the OSHW Documentation Jam, I see now that you&amp;#039;re listed in the partners section.   I don&amp;#039;t have time to go int...&amp;quot;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;Ok just set it up for emails as they are sent. &lt;br /&gt;
&lt;br /&gt;
And yes it was the OSHW Documentation Jam, I see now that you&amp;#039;re listed in the partners section. &lt;br /&gt;
&lt;br /&gt;
I don&amp;#039;t have time to go into details as I&amp;#039;m going to work, but I&amp;#039;d really love to join the documentation jam, to contribute strategies what I&amp;#039;ve been developing. I believe language is powerful for accelerating concepts by facilitating discussion and stirring the imagination. &lt;br /&gt;
&lt;br /&gt;
There&amp;#039;s a strategy to the wording for openables, sustainables, and adaptables. Each has two cousin words&lt;br /&gt;
&lt;br /&gt;
For example, openables is the goods and the method (licensing, sharability); openability is the philosophy and the trait (think sustainability); and openeer is a &amp;quot;pioneer and engineer of openability&amp;quot; who has contributed to the advances and philosophy of openability. &lt;br /&gt;
&lt;br /&gt;
Since we have the website domain names (and Twitter aliases) then when people google the words they&amp;#039;ll more likely encounter a standard description. (I&amp;#039;ll leave this strategy to more capable hands, voted on by the community) &lt;br /&gt;
&lt;br /&gt;
Another strategy is transparency and sharing info. This will all be developed in the open, adhering to teachOpen standards. &lt;br /&gt;
&lt;br /&gt;
Finally, another language strategy: using the word &amp;quot;freed&amp;quot; to describe what really qualifies as open. Marketply could trademark it as I&amp;#039;ve done with &amp;quot;userSmart&amp;quot; and &amp;quot;Multiversal&amp;quot;, and license it free to the all goods and organizations that qualify. The beautiful thing is that Marketply doesn&amp;#039;t choose who qualifies for any of its trademarks, the community chooses. Always. &lt;br /&gt;
&lt;br /&gt;
Marketply will also empower the community to be able to &amp;quot;veto&amp;quot; any decisions that Marketply would make that clearly goes against its core principles. &lt;br /&gt;
&lt;br /&gt;
I expect all of this to generate discussion focused on openability (and/or sustainability, adaptability). &lt;br /&gt;
&lt;br /&gt;
Marketply will be as close to nonprofit as possible and I&amp;#039;m looking into how to share the company&amp;#039;s decisions and progress in real time and to involve companies in teachOpen so people everywhere can gain a demonstrated template for making hardware truly open source. &lt;br /&gt;
&lt;br /&gt;
Best, thank you! &lt;br /&gt;
&lt;br /&gt;
~Marino&lt;/div&gt;</summary>
		<author><name>Marcin</name></author>
	</entry>
</feed>