<div dir="ltr">sorry, correcting the email address...</div><div class="gmail_extra"><br clear="all"><div>_________________________________________<br>malcolm stanley<br><br>google.voice: 215.821.6252 <div>Cell: 267.251.9479 <------------- new<br>
email: <a href="mailto:a.malcolm.stanley@gmail.com" target="_blank">a.malcolm.stanley@gmail.com</a><br>twitter / linkedin: amstanley<br>Read my blog at <a href="http://soaringhorse.blogspot.com" target="_blank">http://soaringhorse.blogspot.com</a><br>
_________________________________________</div></div>
<br><br><div class="gmail_quote">On Tue, Mar 19, 2013 at 5:06 PM, malcolm stanley <span dir="ltr"><<a href="mailto:a.malcolm.stanley@gmail.com" target="_blank">a.malcolm.stanley@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">All<div><br></div><div>I am spending the week at the nVidia GPU conference in San Jose.</div><div>At the conference I ran into Manfred van der Voort of ICR3ATE, a company that sells sharing tools for object design.</div>
<div>I mentioned to him that we are discussing how you signify licences on designs for items;</div><div>he says that on his platform when you create a design then you can share that design under a variety of licences, and that the licence is part of the design record.</div>
<div>I'm not doing it justice with that description: its apparent they have thought a lot about this.</div><div><br></div><div>Anyway, I am copying him here so he can explain in more detail how their system works. </div>
<div><br></div></div><div class="gmail_extra"><div class="im"><br clear="all"><div>_________________________________________<br>malcolm stanley<br><br>google.voice: <a href="tel:215.821.6252" value="+12158216252" target="_blank">215.821.6252</a> <div>
Cell: <a href="tel:267.251.9479" value="+12672519479" target="_blank">267.251.9479</a> <------------- new<br>
email: <a href="mailto:a.malcolm.stanley@gmail.com" target="_blank">a.malcolm.stanley@gmail.com</a><br>twitter / linkedin: amstanley<br>Read my blog at <a href="http://soaringhorse.blogspot.com" target="_blank">http://soaringhorse.blogspot.com</a><br>
_________________________________________</div></div>
<br><br></div><div class="gmail_quote"><div><div class="h5">On Tue, Mar 19, 2013 at 10:18 AM, Marketply <span dir="ltr"><<a href="mailto:contact@marketply.org" target="_blank">contact@marketply.org</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5">
<u></u>
<div>
<div>
Good morning Alicia,
</div>
<div>
</div>
<div>
I believe technology is evolving such as to make it easier for people to share the method and stand out as genuine. We're developing a few strategies which might help, one is a digital wireframe standard to emulate all hardware, software, and firmware. It's open and comes in two parts: a wireclone and a simuclone (think wireframe and simulation).
</div>
<div>
</div>
<div>
Another strategy is "teachOpen", a way to certify that you record exactly how you build something. It's a free certification and any company can apply, but we let the community decide if they pass. Our company is doing business this way, teaching how we create everything and inviting other businesses and organizations to participate in order to build a community and to speed up the creation of best practices.
</div>
<div>
</div>
<div>
The third strategy is to simply have a trademark to certify goods as open, again decided by the community. I'll go into details later we'll overcome the usual pitfalls with this route.
</div>
<div>
</div>
<div>
See: <a href="http://www.marketply.org/seeds/#teachopen" target="_blank">http://www.marketply.org/seeds/#teachopen</a>
</div>
<div>
</div>
<div>
And check out or subscribe for updates to either:
</div>
<div>
<div>
<a href="https://twitter.com/wireclone" target="_blank">https://twitter.com/wireclone</a>
</div>
<div>
<a href="https://twitter.com/simuclone" target="_blank">https://twitter.com/simuclone</a>
</div>
</div>
<div>
</div>
<div>
~Marino
</div><div>
<div>
</div>
<div>
</div>
<blockquote style="margin-left:0px;padding-left:10px;border-left:solid 1px blue" type="cite">
On March 18, 2013 at 4:01 PM Alicia Gibb <<a href="mailto:pip@nycresistor.com" target="_blank">pip@nycresistor.com</a>> wrote:
<br>
<br>I think one of the issues with them term 'open' is that it has no consequences if you use it. Something I continue to think about is the incongruous parallels between openness like creative commons and using the open source hardware logo. The source for writing and the product are the same thing, so when putting something in the creative commons, the product is more likely to be the source itself and people can copy and paste, remix, whatever. With hardware, the product is different from the source, so it includes another step to publish the files. I'd like to see a test of reverse engineering on everything labeled as open hardware to see where the companies really fall - for example, someone tears down / reverse engineers the Pogo Linux box (*cough* ifixit) and publishes all the files and remixes it and starts selling the new thing, what is Pogo's reaction? If they are advertising oshw, they should be completely okay with this or otherwise not use the term. If there was a consequence of having your stuff published and remixed readily if you used the word open, I think there would be a different approach to the word, but unfortunately even with reverse engineering there's often layers we can't get to in complex items.... and of course the point of oshw is to publish the files yourself. But if it were advertised that anything with the word open were free to rip apart / reverse engineer / etc. AND it happened on a very regular basis when files were not published, perhaps we'd see more people following the communal definitions (oshw) around the word.
<div>
</div>
<div>
Alicia
</div>
<div>
<br>
<div>
<br>
</div>
</div>
</blockquote>
</div></div><br></div></div><div class="im">_______________________________________________<br>
discuss mailing list<br>
<a href="mailto:discuss@lists.oshwa.org" target="_blank">discuss@lists.oshwa.org</a><br>
<a href="http://lists.oshwa.org/listinfo/discuss" target="_blank">http://lists.oshwa.org/listinfo/discuss</a><br>
<br></div></blockquote></div><br></div>
</blockquote></div><br></div>