To what extent does copyright protect software functionality? Suppose I see an innovative piece of (commercial) software that delivers considerable, non-trivial functionality. Can I re-implement it? Suppose I study it carefully, work out what it does and how it does it, and then write my own software to do the same thing. I haven't (knowingly) copied any specific part of that system, but I have replicated the system as a whole ...its design. So have I infringed the copyright of the original system? Consider the possibility of translating a Harry Potter novel into French. If I change the names, I could produce a text that didn't contain a single word of Rowling's original. But I believe that doing so would infring Rowling's copyright. What is the situation with software?
You can't compare a novel and a computer program that way. With a novel, the expression and the essence of the work are the same. With a computer program, while the expression is hard work to create, and often is very original, the essence of the work is what it does. So I can create a totally independent computer program doing the exact same thing, without any copying whatsoever. With your novel, the essence of the work is copied. Unless you change Harry Potter to a pot smoking sanitary engineer, change his wand to a guitar, move him to a different world, where is not surrounded by fellow wizards but by intelligent, speaking animals, and write the whole thing a few years before Mrs. Rowling did.
Alice has been developing her own enhancements, and they're pretty similar to Bob's. Neither Alice nor Bob has copied the other's enhancements, so neither has violated the other's copyright in the enhancements. Whether that could be proved in court is another matter, of course, but since the original work is licensed under creative commons the question unlikely to arise in court. Would Alice be prevented from coming up with enhancements to her own game if other people could prove they thought of and released the idea first? No. Copyright does not protect ideas. It only protects a particular expression of those ideas from being copied. Theoretically, if two authors come up with identical 500-word descriptions of something and can establish that each did so independently, neither has a claim against the other. The practical problem there, of course, is that it would be impossible to prove such a thing. Could Alice outright claim Bob's "Adapted Material" because he developed it on her original work? Assuming that in publishing his adaptations Bob followed the terms of the creative commons license with respect to the original work, Alice's only claim would be that he copied her adaptations without following the terms of the license. If Bob can show that he did not do so, her claim would fail. In a comment, you wrote: Suppose Alice went ahead and intentionally, somehow provably ripped off Bob's "Adapted Material" because she liked the content so much, does Bob reserve any rights on his adaptation, or is Alice able to commercialize the work that Bob did in extending her original work? If we assume that Bob complied with the license of the original material, we know that he licensed his adaptations under "the identical terms," so Alice would be able to use Bob's adaptations under those terms for non-commercial purposes. Since the assumption here is that Alice provably copied something of Bob's, I think it is fairly clear that she would be liable for damages if she exploited that material commercially without paying royalties.
If I lock you in a room without access to anything and tell you &quot;Write a novel&quot; and you write a novel with characters, you have copyright in the work. But it's not absolute: If you use your own characters, you own all the copyright in the work, but not in the idea, as ideas are not copyrightable, see Feist v Rural. If you use someone else's characters extensively (as in more than a short hommage/cameo), you very likely make a derivate. You own a copyright in your part, as in the expression of the story or pictures you created, but you do not gain property interest in the existing characters' expression. Since the copyright to the characters lies with the owner of their IP, you need their OK to release (and also to even make) your work - as with the owner of a copyright is the sole right to decide on distribution and creation of derivates under 17 USC § 106 (2). Also remember that making an unlicensed derivate work risks having nothing you can sue for in case the original copyright owner lifts your ideas and scenes-a-faire parts and adapts them for their own derivate, see Anderson v Stallone The strange case of fanfiction chains... Now, there is a strange situation when a work is based on a work which is based on a work... Then, publishers and editors start with red ink and the result is, that what people know as Twilight now has nothing to do with the fanfiction it started as (It wasn't Vampires in the original draft), and 50 Shades of Grey ended up striking any and all supernatural from it, despite it having been a Twilight fanfiction originally. By making own characters and own expression of the world, there could be no copyright infringement. US law vs Egypt law? Both Egypt and the US have signed the Berne convention, meaning that copyright is very very similar in the broad strokes that the right to allow or disallow derivates is with the copyright holder. Also, since Ben10's copyright owners are to the best of my knowledge in the US (Cartoon Network Studios &amp; Men of Action Studios), they will sue in a US federal court.
There are two common approaches. The first approach is simply to let copyright law apply. Under the default terms, the IT provider has no rights to copy your software. Running software is allowed, of course, and not a problem that you need to deal with vis-a-vis the IT provider. You still can sue them if they copy your software, even in the absence of a contract. That is the chief function of copyright, after all! The second approach is to allow the customer to subcontract third parties to act on behalf of them, while acknowledging that such subcontracting does not dissolve them from any responsibilities towards you. In other words, if the 3rd party would do something unauthorized, you have a claim towards the customer and they have a distinct but related claim towards their IT supplier.
Copyright includes authorization of derivative works such as translations, so you must have permission of the copyright holder to create a translation. You could be sued for creating the unauthorized translation for your friend. If you attempt to further distribute the book, the chances of getting sued increase substantially. That path probably includes your legal obligation to foot the bill for the publisher and distributor having to defend themselves in court, since your contract with the publisher or distributor probably includes an indemnification clause saying that you indemnify them (pay their costs) against damages for your infringement. So your are at risk, and it increases if you do anything to distribute the translation.
In general, the output of a program is not copyrighted by the author of the program. When you write a novel in Word, Microsoft doesn't own any copyright in your novel. When you prepare financial statements with Excel, Microsoft doesn't own any copyright in those either. There can be exceptions. Some programs (like GNU Bison, a parser generator) actually do output parts of their own source code, and their source code is copyright to the author. To clarify things, GNU made a statement in the license for Bison that officially says they don't have copyright to what it outputs. You should expect programs of this type to have such an exception, and if they don't, maybe ask the author or don't use them.
Software doesn't infringe any patents. Creating a product that includes the software may infringe the patent, and may infringe that patent because the software is included, but the software itself doesn't. Software on its own doesn't have any effect that could be patented, only as part of some machine. On the other hand, if you want to distribute software that is under the GPL v3.0 license, then a requirement is that you give everyone a patent license for all patents that would be infringed by using the software (as part of some machine), and if you are not the patent holder, then in practice that means you are not allowed to distribute the software. With your grand plan that you write software and then let the end users do the patent infringement, that will backfire in two ways: First, you'd be likely sued for contributory patent infringment, because it is you who enables the patent infringemnt. Second, you can be sued for copyright infringement because you have no license that allows you distribution of the software, depending on the Open Source license used.
Patents protect inventions, Copyright protects artistic or literary creation Software does not qualify for patents. In some jurisdictions but by no means most, algorithms and business processes can be patented. Software, both the literary (code) and artistic (UIJ) work, is protected by copyright which prevents copying the expression but not the idea. So software writers can take inspiration from other software but can’t copy it. So, things that look like copyright infringement often aren’t but things that look like patent infringement often are. Patents last for a short time (10-20 years) and take a lot of investment of time and money so their owners are incentivised to commercialise them quickly and on a large scale. Copyright lasts for a long time (life of the creator(s) + 50 years minimum depending on jurisdiction) and come into existence automatically. In general, it is easier to create a literary or artistic work than a novel invention. So, patent owners are more incentivised to protect their IP than copyright owners.