<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type"/>
</head><body style="">
<div>
Thank you, Michael.
</div>
<div>
</div>
<div>
I think the meeting is actually a great time/place to discuss a trademark option. My suggestion had been a reply specifically to point #2 and # that Alicia highlighted as points of discussion:
</div>
<div>
</div>
<div>
<em>2) Is there another area we could put aspects of oshw that is not in the realm of a patent, but rather User Agreement or Terms of Service?</em>
<div>
<em> </em>
</div>
<div>
<em>3) Continue the discussion / brain storm implementation of the <a target="_blank" href="http://lists.oshwa.org/pipermail/discuss/2013-February/thread.html">layering of openness / laundry label from the discussion list</a>.</em>
</div>
</div>
<div>
</div>
<div>
Patents are expensive, although defensive publishing is a lot more affordable and its costs can even be lowered further with a good strategy and getting patent offices to routinely browse the system. (Providing more detail than current patents do video sample, pics, sample code, sample use, etc would definitely ease the patent examiner's job and make it far more likely they'll check the open hardware database).
</div>
<div>
</div>
<div>
Trademarks to certify can be used as an additional layer with defensive publishing for a potent combination, or even alone pretty effectively.
</div>
<div>
</div>
<div>
And it's a great chance to discuss the trademark option because people with legal expertise will be present to consider its feasibility.
</div>
<div>
</div>
<div>
In any case, if OSHWA likes what we do with the Freedware licensing, they can opt to become its steward. (with the Freedware community's blessing, of course). Instead of having duplicate efforts. Or if they want, to create their own and we'd offer to help kick it off.
</div>
<div>
</div>
<div>
😃,
</div>
<div>
</div>
<div>
Marino Hernandez
<br/>(just a founder of
<a href="http://www.marketply.org">Marketply</a>)
<br/>203-429-4205
</div>
<div>
</div>
<div>
</div>
<blockquote style="position: relative; margin-left: 0px; padding-left: 10px; border-left: solid 1px blue;" type="cite">
On October 24, 2013 at 1:39 PM Michael Weinberg <mweinberg@publicknowledge.org> wrote:
<br/>
<br/>
<div dir="ltr">
<div>
I'll +1 on the TM/certification front. I don't know that it is an either/or with patents, and the details will matter (a lot), but conceptually it is quite attractive as an option.
<br/>
<br/>Of course, that doesn't mean that this meeting is the right time/place to talk about it. But the fact that it doesn't get discussed at this meeting also doesn't mean that it isn't worth talking about.
<br/>
</div> -michael
</div>
<div>
<br/>
<br/>
<div class="gmail_quote">
On Thu, Oct 24, 2013 at 1:08 PM, Marketply
<span><<a target="_blank" href="mailto:contact@marketply.org">contact@marketply.org</a>></span> wrote:
<br/>
<blockquote style="margin: 0 0 0 .8ex; border-left: 1px #ccc solid; padding-left: 1ex;">
<span style="text-decoration: underline;"></span>
<div>
<div>
Thanks for your input Michael,
</div>
<div>
</div>
<div>
We won't be shaming anyone, nor taking retribution. The process has an inherent reward for good behavior: credibility. That, together with respect/fellowship is enough to make the process self-efficient.
</div>
<div>
</div>
<div>
Also, as you say it'll be self-correcting because people will remember wrong certifications made in bad faith in a system that's transparent and open.
</div>
<div class="im">
<div>
</div>
<div>
<div>
😃,
</div>
<div>
</div>
<div>
Marino Hernandez
<br/>(just a founder of
<a target="_blank" href="http://www.marketply.org">Marketply</a>)
<br/>
<a target="_blank" href="tel:203-429-4205">203-429-4205</a>
</div>
</div>
<div>
</div>
</div>
<div>
<br/>> On October 24, 2013 at 1:04 AM Michael Turner <
<a target="_blank" href="mailto:michael.eugene.turner@gmail.com">michael.eugene.turner@gmail.com</a>> wrote:
<br/>.....
<br/>
<div>
<div class="h5">
> I'd charge a deposit for certification evaluation, which would not be
<br/>> refunded if it turns out basic criteria aren't met. Those that failed
<br/>> would furthermore see their applications appear on a Wall of Shame,
<br/>> with a Most Shameless Application of the Month featured. They'd have
<br/>> to pay even more to get de-listed from the Wall. But since they
<br/>> submitted their application in the open, nothing prevents others from
<br/>> copying onto a Wall of Shame of their own. Hey, sorry, we don't even
<br/>> know those people. You'll have to go talk to them, to see what their
<br/>> ransom demands are. What do you mean, "blackmail"? Did you read the
<br/>> fine print?
<br/>>
<br/>> Naturally, I'd call this "the Open Process for Openness
<br/>> Certification." It sounds cooler that way.
<br/>>
<br/>> Regards,
<br/>> Michael Turner
<br/>> Executive Director
<br/>> Project Persephone
<br/>> K-1 bldg 3F
<br/>> 7-2-6 Nishishinjuku
<br/>> Shinjuku-ku Tokyo 160-0023
<br/>> Tel:
<a target="_blank" href="tel:%2B81%20%283%29%206890-1140">+81 (3) 6890-1140</a>
<br/>> Fax:
<a target="_blank" href="tel:%2B81%20%283%29%206890-1158">+81 (3) 6890-1158</a>
<br/>> Mobile:
<a target="_blank" href="tel:%2B81%20%2890%29%205203-8682">+81 (90) 5203-8682</a>
<br/>>
<a target="_blank" href="mailto:turner@projectpersephone.org">turner@projectpersephone.org</a>
<br/>>
<a target="_blank" href="http://www.projectpersephone.org/">http://www.projectpersephone.org/</a>
<br/>>
<br/>> "Love does not consist in gazing at each other, but in looking outward
<br/>> together in the same direction." -- Antoine de Saint-Exupéry
</div>
</div>
</div>
</div>
<br/>_______________________________________________
<br/> discuss mailing list
<br/>
<a href="mailto:discuss@lists.oshwa.org">discuss@lists.oshwa.org</a>
<br/>
<a target="_blank" href="http://lists.oshwa.org/listinfo/discuss">http://lists.oshwa.org/listinfo/discuss</a>
<br/>
</blockquote>
</div>
<br clear="all"/>
</div>
</blockquote>
</body></html>