Ethics of incorporating a supplier's technical documentation into one's own documentation?
A company, M, buys components from company, S, to build into their product. Company S has technical documentation regarding safety and maintenance available in many languages and publicly available in the internet.
Is it ethical for company M to incorporate this documentation into it's own product documentation without first getting permission from the supplier or, at least, indicating the source?
This post was sourced from https://writers.stackexchange.com/q/16966. It is licensed under CC BY-SA 3.0.
2 answers
You are accessing this answer with a direct link, so it's being shown above all other answers regardless of its score. You can return to the normal view.
This is not an ethical question. It is a legal question. Ethics deals with professional conduct over and above what is required by law. Copyright is a matter of law, not ethics.
In this particular case, however, it is also a matter of contracts. You should be negotiating a licence to use their content as part of your purchase agreement with them, and you should also be negotiating for access to their source files so that you can reuse them more easily. Ideally, you should negotiate for an ongoing window into their docs process so that you always get the latest content from them to include in your docs.
0 comment threads
I am not a lawyer and this is not legal advice.
First, check any license terms that accompany Company S's documentation. They might have published it with the intention that other vendors will incorporate it (e.g. some Apache platforms), or they might not intend that but allow it under their license (e.g. Stack Exchange, or anything else that uses the CC-BY-SA license). Be sure to check whether any license you find permits commercial use; some don't.
In the absence of any explicit permission or license, incorporating their documentation into your own would be making a derivative work that might violate their copyright. (Wholesale incorporation would very likely be a copyright violation; being selective would come down to a question of how much and what you selected, and the limits there probably vary by jurisdiction.)
If Company S's license permits incorporating their documentation into other products, check the license to see if attribution is also required. Even if it is not, in my experience (technical writer in the software field) it's best to attribute anyway. Not only is it more honest, but it's also visibly honest -- important if you're concerned that people who don't know that you had permission notice the copying. You don't want to get a reputation as an unscrupulous business.
0 comment threads
0 comment threads