Teach you how to apply for computer software copyright (5) --- Information supplement (must see)

#The flower on the cliff, the more fragrant the more impermanent

This blog is the fifth post I taught you how to apply for computer software copyright. The reason for writing this is that after I wrote the first four blogs, some people around me came to ask me some questions when applying for software. I found out after I answered There are still some omissions in the previous writing. If I don't add it, I'm afraid it will be considered as teaching people to apply. This is smashing my sign.

Teach you how to apply for software copyright series:
1. Fill in the application form
2. Generate code files and identity certificates
3. Software description documents
4. Information mailing
5. This article

—————————————————— The dividing line of the text—————————————————— I
still have to declare, my series, For students who have the intention to apply softly, there may be some deviations in the application of the company or unit. Please do not refer to my blog to avoid errors.

1. Questions about independent development and cooperative development.
Independent development means that there is only one copyright owner in the entire software copyright, and this copyright owner has all the rights to the code, which is independent development.
Cooperative development means that there are two or more copyright owners in the entire soft work, and they all have rights to their respective codes. (A bit complicated)
The explanation I found online is like this.

1. For software jointly developed by two or more natural persons, legal persons or other organizations, the ownership of the copyright shall be agreed upon in a written contract by the co-developers.
2. If there is no written contract between the developers of the jointly developed software or the contract does not clearly stipulate, and the cooperatively developed software can be used separately, the developers can independently enjoy the copyright of the parts they developed; however, when the copyright is exercised, it shall not be extended to The overall copyright of the jointly developed software.
3. If the cooperatively developed software cannot be used separately, its copyright shall be shared by the co-developers and exercised by consensus; if consensus cannot be reached and there is no legitimate reason, any party shall not prevent the other party from exercising other rights except the right of transfer. But the proceeds should be reasonably distributed to all co-developers.

What's said here is a bit complicated. If commercial systems are involved, the details are certain. For me in college, it doesn't have to be so complicated. Here are a few situations in which students apply for softening.
(1) Code written by yourself, including those written in idle time, written in projects, written in competitions, and written in curriculum design. If you are participating in a teacher’s project, this code needs to be applied by the team or the teacher, please negotiate in advance. If the code is written by yourself, please be sure to pay attention to your own rights. It is best to be the only copyright owner or the first copyright owner for the code written by yourself.
(2) Code written by yourself and others. For example, projects made by multiple people, course designs and competitions. In this case, please discuss with everyone, whether to write multiple copyright owners in a soft work, or each person is responsible for part of the code to apply for software copyright. Here is a problem. Some schools only look at the first copyright owner or the first second copyright owner for the credits for software copyright, which is more troublesome. If the team is willing, one person can be selected as the first copyright owner. If you want multiple copyright owners, you must sign a cooperative development agreement between copyright owners (there is a template on the Internet). Here is a problem. Please make sure to divide the software/code and allocate it in the cooperative development agreement to avoid subsequent Trouble.
(3) Code written by yourself, but add friends. Many people are willing to bring roommates or good friends with them when applying for a soft lease, so there must be multiple copyright owners on the application form. If you want multiple copyright owners, you must sign a cooperative development agreement between the copyright owners (there is a template on the Internet), here is a problem, because the copyright owner other than the first copyright owner is yours, so it’s best Choose some less important division of labor in the cooperative development agreement to avoid possible problems.

  1. For multiple copyright owners, please be sure to mail all the copies of the ID cards of the copyright owners, otherwise you will be asked to supplement the materials.

  2. Information about data other than the code but closely related to the software.
    This is a rather embarrassing question. It just so happens that the latest soft book I applied for is about image encryption. There is a mathematical sequence used for encryption. Strictly speaking, this thing is not considered as a code written by yourself, but if Without this sequence, the meaning of the entire code is not very large. So in the end, I didn’t know how to apply, so I asked many people who have software around me. Regarding this question, my recommendation is:
    print out the encrypted sequence in n*n format as an additional file of the software Submit, and attach a description when mailing the document, and let the Copyright Protection Center decide whether to stay.

I wrote it like this: This document is the encryption sequence of the xx software. There are x pieces of data on each page. There are x pages in total. The amount of data is x. It has xx functions for the software. If it is a software supplementary file, please include it as usual; if it is not needed, please discard it directly.

Because there is no news about my application, I show that I wrote it like this, and I will see the situation later.

  1. Precautions in the software documentation for embedded code and FPGA code applications.
    (Too sleepy, sleep, make up another day.)

Guess you like

Origin blog.csdn.net/Ninquelote/article/details/106965334