>Hey Kevin:
>
>>> Note:
>>> All modifications made by Claims Verification Inc. (CVI)
>>> are copyrighted and owned solely by CVI, that said all
>>> modifications made by CVI and published either here or
>>> on our website are freely usable by the public domain
>>> after and only after proper attribution is given.
>
>

ust my $.02 on this.

You might want to consult with a lawyer on the above. AFAIK, "Public Domain" has a very specific legal definition:

Content/Software released to the public domain is not copyrighted, and may be used for personal and commercial purposes, without restriction. The public domain content/software can be used in other programs.

That is, things can't be Copyrighted and Public Domain at the same time.

Also, "ideas" can't be copyrighted. The specific code used to implement that idea can be. However, I think you'd be hard pressed to enforce such a copyright on derivative material, especially if it only involves a small amount of code - there are only so many different ways to do some things in code.

Honestly, if I were a framework author I'd think long and hard about using any code that has been Copyrighted, unless it offered me real and specific advantages to do so. I'd be even harder pressed to use what I would consider "code-snippets" and acknowledge any kind of third party Copyright on them which might put me in a "bad" position legally later. It's a complication I just wouldn't want to deal with. There isn't any benefit to doing so since I am free to implement the changes any way I see fit w/o any nasty Copyright issues.

If all you're interested in is acknowledgement of the source of the idea (and code changes), as you've said, Kevin already does this. What does the Copyright on the code do for you? What benefit does it give you? I'd say virtually none since I don't think you could enforce it (would you even bother?). The downside to having it is that you're practically guaranteeing your code will never see the light of day in the framework (which means you'll have to keep making these changes with each new version), possibly no acknowledgement as to the source of the idea if it is implemented (since it might be construed as an acknowledgement of your claim of Copyright), etc. Why bother?