Thanks Christopher,

I’ve sent Apple a request for clarification on the matter and will
keep you all informed.


Keith



On Wed, Oct 21, 2009 at 2:10 PM, Christopher Wright <[email protected]> wrote:
>> Thanks Christopher for your explanation — although if my patch looks
>> and works the same…is that a breech of copyright.
>
> leave that one for the judges (and jury, where applicable) -- you won't get
> anywhere exploring the wide grey area of copyright law.  I have a hard time
> imagining Apple going after someone for what is admittedly very simple math,
> so unless you're making a bajillion dollars you're probably safe (and if you
> make that much, you can probably buy laws to keep yourself safe ;), but
> anyway...
>
>> I’m not a coder, but my understanding was that the example code from
>> Apple could always be used in any commercial application—and there are
>> examples of applications which not much more than one of the example
>> code projects. I expected patches to be the same, but am now not sure.
>
> Example code can be used in a commercial app, but I think George's question
> is whether or not the patch you referred to is considered "sample code" is
> the pertinent point of discussion -- just because it comes with the machine
> doesn't mean it's sample code.  The standard desktop wallpapers are _not_
> sample code/free reused, and I could be convinced that built-in virtual
> patches are in league with desktop wallpapers as much as they are sample
> code...
>
>> Who should I contact for clarification? Apple developer relations?
>
>
> I'd start by exploring Apple legal ( http://www.apple.com/legal/ ), and go
> from there.
>
> --
> [ christopher wright ]
> [email protected]
> http://kineme.net/
>
>
 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Quartzcomposer-dev mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/quartzcomposer-dev/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to