<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">I think you're talking about two different things here. I'm not sure Catarina's talking about a sticker or logo, so much as an inventory tool.<div><br></div><div>t.</div><div><br><div><div>On Mar 7, 2013, at 1:06 PM, Matt Maier wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>Catarina,</div>
<div> </div>
<div>I agree with all of your sentiments regarding the integrity of the open source hardware definitions and mark(s).</div>
<div> </div>
<div>It doesn't seem like a sticker or a logo will have enough space to provide any useful resolution on which subcomponents are open. And as you pointed out the source files, while they can contain infinite resolution, might be hard to find.</div>
<div> </div>
<div>What if the mark/stamp/logo/whatever was used only to identify things that are totally open.</div>
<div> </div>
<div>For things that are partially open, or that contain open components, there could be a flyer (like a receipt, mattress tag, or warranty card) that has enough surface area to summarize the open components and their associated licenses. The added expense would be minimal and some projects would even have enough material to just print the flyer on an inside surface as part of the manufacturing process.</div>
<div> </div>
<div>Not so much a "mark" as an "openness card."</div>
<div> </div>
<div>Of course it wouldn't be mandatory, but the OSHWA could define best practices and a template for the openness card to make it easy for producers to standardize so that consumers/developers know what they're looking at.</div>
<div> </div>
<div>Cheers,</div>
<div>Matt<br></div>
<div class="gmail_quote">
<blockquote style="BORDER-LEFT:#ccc 1px solid;MARGIN:0px 0px 0px 0.8ex;PADDING-LEFT:1ex" class="gmail_quote">------------------------------<br><br>Message: 4<br>Date: Thu, 7 Mar 2013 12:36:58 -0500<br>From: Catarina Mota <<a href="mailto:catarina@openmaterials.org" target="_blank">catarina@openmaterials.org</a>><br>
To: The Open Source Hardware Association Discussion List<br> <<a href="mailto:discuss@lists.oshwa.org" target="_blank">discuss@lists.oshwa.org</a>><br>Subject: Re: [Discuss] discuss Digest, Vol 10, Issue 35<br>
Message-ID:<br> <CAH-asVYrCJ0vR_DnuTKH2vtAxT+YuGYU3FqwSWET7V=<a href="mailto:mYPxWbQ@mail.gmail.com" target="_blank">mYPxWbQ@mail.gmail.com</a>><br>Content-Type: text/plain; charset="iso-8859-1"<br>
<br><br>Agreed, this could work. I wasn't suggesting that the more detailed label<br>needs to be on the product itself (though a sticker would make it easier to<br>deal with), but there should be some sort of clarity about whether or not a<br>
project is open or partially open. And if we say it's partially open then<br>somewhere (on the documentation? on the website? on the product's<br>packaging?) we should state which parts are open source.<br><br><br>
><br>> -Matt<br>><br>><br>>> ------------------------------<br>>><br>>> Message: 2<br>>> Date: Thu, 7 Mar 2013 11:26:33 -0500<br>>> From: Catarina Mota <<a href="mailto:catarina@openmaterials.org" target="_blank">catarina@openmaterials.org</a>><br>
>> To: The Open Source Hardware Association Discussion List<br>>> <<a href="mailto:discuss@lists.oshwa.org" target="_blank">discuss@lists.oshwa.org</a>><br>>> Subject: Re: [Discuss] OSHW Best Practices / Layers of Openness<br>
>> Message-ID:<br>>> <CAH-asVZtQaQsqswJjXXoPWBHtnFpxn422+WmgJvAj22fky-W=<br>>> <a href="mailto:Q@mail.gmail.com" target="_blank">Q@mail.gmail.com</a>><br>>> Content-Type: text/plain; charset="iso-8859-1"<br>
>><br>>> This is why I was so attracted to Tom's idea of a label that, no matter<br>>> where it's placed on the product, tells you right away what parts are<br>>> open.<br>><br>><br>> _______________________________________________<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>><br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <<a href="http://lists.oshwa.org/pipermail/discuss/attachments/20130307/dfd746e5/attachment.html" target="_blank">http://lists.oshwa.org/pipermail/discuss/attachments/20130307/dfd746e5/attachment.html</a>><br>
<br>------------------------------<br><br>_______________________________________________<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><br>End of discuss Digest, Vol 10, Issue 38<br>***************************************<br></blockquote></div><br>
_______________________________________________<br>discuss mailing list<br><a href="mailto:discuss@lists.oshwa.org">discuss@lists.oshwa.org</a><br>http://lists.oshwa.org/listinfo/discuss<br></blockquote></div><br></div></body></html>