Creative Commons - User contributions [en]

ShareAlike compatibility analysis: Mulan

2023-11-17T17:16:53Z

CCID-yuanxiaoxu:

“Mulan Open Works License Attribution-ShareAlike, Version 1” (MulanOWL BY-SA v1, http://openworks.mulanos.cn/#/licenses/MulanOWL_BY-SA-v1) and “Mulan Open Works License Attribution-PatentLicensed-ShareAlike, Version 1” (MulanOWL BY-PL-SA v1, http://openworks.mulanos.cn/#/licenses/MulanOWL_BY-PL-SA-v1) were published in 2022. MulanOWL BY-SA v1 and MulanOWL BY-PL-SA v1 are copyright licenses with a ShareAlike mechanism and an attribution mechanism, and [http://freedomdefined.org/Licenses#Free_Art_License they do not violate the definition of Free Cultural Licenses]. Thus, it satisfies the [[ShareAlike_compatibility_process_and_criteria#Minimum_compatibility_criteria.|minimum criteria]] for compatibility set forth in our [[ShareAlike_compatibility_process_and_criteria|ShareAlike compatibility criteria]].

MulanOWL BY-PL-SA v1 grants patent rights and is not compatible with CC BY-SA 4.0.

MulanOWL BY-SA v1 is similar to CC BY-SA 4.0 overall, and the effect of each license as applied to a creative work is largely the same. Inevitably, there are differences between the licenses, which are explained in more detail below.

'''Summary of comparison: MulanOWL BY-SA v1<ref>Note that CC reviewed the English language version of the MulanOWL BY-SA v1 and MulanOWL BY-PL-SA v1 to conduct this analysis.</ref> and BY-SA 4.0'''

*It appears that the MulanOWL BY-SA v1 license referenced the CC BY-SA 4.0 license in its development. We are not sure what decisions went into the choices that made some portion of MulanOWL BY-SA v1 diverge from CC BY-SA 4.0. The steward of Mulan licenses pointed to LearnerHub as a repository for works licensed under Mulan BY-SA v1 license.

*The specific attribution and marking requirements in the two licenses vary slightly. CC BY-SA 4.0 allows for more flexibility depending on the context in which the work is used. Most notably, MulanOWL BY-SA v1 asks users to retain trademark and patent statements.

*We are particularly concerned that, unlike CC BY-SA 4.0, MulanOWL BY-SA v1 does not mention database rights, nor does it mention related rights. This could cause problems for reusers.

*The ShareAlike scope of MulanOWL BY-SA v1 is likely broader.

*MulanOWL BY-SA v1 does not terminate even upon breach, as long as the breach was cured prior to, or within 30 days of, receiving notice of termination. This may create some ambiguity, such as whether a licensor can collect damages during the period when a breach has happened but no notice is yet sent. CC BY-SA terminates automatically upon breach, but is reinstated automatically if the breach is cured within 30 days of discovery.

*

{| style="border-collapse: collapse;" border="1" cellpadding="10"
|-
! style="background-color:#CCCCCC;" | Features || style="background-color:#CCCCCC;" | BY-SA 4.0 || style="background-color:#CCCCCC;" | MulanOWL BY-SA v1
|-
| License scope || Copyright, neighboring rights and sui generis database rights (SGDRs) (Sec 1d) || Copyright only (Sec 1)
|-
| Attribution trigger || If there is applicable copyright in work, then when work or adaptation of work is shared. (Sec 3a)
<br>
If there are applicable SGDRs in work, then when all or a substantial portion of database contents is shared. (Sec 4c)
|| When work (modified or not) is disseminated (Sec 3)
|-
| Attribution removal clause || Yes (Sec 3a3) || No
|-
| Attribution elements ||
#creator and attribution parties
#copyright notice
# license notice
# disclaimer notice
# URI or link to the licensed material
# indicate and link to license
(Sec 3a1)
<br>
||
#name of licensor
#copyright statement
#license notice
#modification statements
#patent statements
# trademark statements
# disclaimer statements
# URI or link to the licensed material
# indicate and link to license
# title and version of the work (optional)
(Sec 3)
|-
| Special marking requirement if work is modified || Yes (indicate if you modified and retain indication of previous modifications) (Sec 3a1B)
|| Yes (indicate if you modified and retain indication of previous modifications) (Sec 3(3) and Sec 3(4))
|-
| ShareAlike trigger || When adaptation is shared (Sec 3b) || When adaptation is shared (Sec 3(3))
|-
| ShareAlike scope || Must ShareAlike contributions to adaptations (Sec 3b);
<br>
Must ShareAlike database if it incorporates substantial portion of database contents (Sec 4b)
|| Must ShareAlike contributions to adaptations (Sec 3(3))
|-
| Source requirement || None || None
|-
| Effective technological measures || May not be applied by licensees if they restrict access to the work or adaptations (Sec 2a5C)
<br>
Licensees have express permission to circumvent if applied by licensor (Sec 2a4)
|| May not be applied by licensees if they restrict access to the work or adaptations (Sec 3(4))
<br>
Licensees have express permission to circumvent even when applied by a third party (Sec 3(4))
|-
| Moral rights || Waived only to the extent necessary to allow the license to function. (Sec 2b1) || Not mentioned
|-
| Termination || Automatic upon breach (Sec 6a) || Terminate upon the receipt of the termination notice from the licensors, unless (1) licensee has cured all the breaches prior to receipt of such notice of termination; or,(2) it’s Licensee's first time to receive a notice of termination from the Licensor, and the licensee has cured all the breaches within 30 days of receipt of such notice; or,(3) licensor has expressly reinstated the license granted to You.(Sec 4.1)
|-
| Reinstatement after termination || Requires express permission unless cured within 30 days of discovery of violation (Sec 6b) || None
|-
| Reps & warranties || Expressly disclaimed (Sec 5) || Expressly disclaimed (Sec 5)
|-
| Choice of law || None || None
|-
| Option to comply with other license versions
|| Yes, but limited. Licensees may choose to comply with a later version of BY-SA if such version is applied to an adaptation of the work.
(Secs 2a5B, 3b1)
|| Yes, but limited. Licensees may choose to comply with a later version of MulanOWL BY-SA if such version is applied to an adaptation of the work.(Sec 3(3))
|}

== Notes ==
<references/>

ShareAlike compatibility analysis: Mulan

2023-11-17T17:15:10Z

CCID-yuanxiaoxu:

“Mulan Open Works License Attribution-ShareAlike, Version 1” (MulanOWL BY-SA v1, http://openworks.mulanos.cn/#/licenses/MulanOWL_BY-SA-v1) and “Mulan Open Works License Attribution-PatentLicensed-ShareAlike, Version 1” (MulanOWL BY-PL-SA v1, http://openworks.mulanos.cn/#/licenses/MulanOWL_BY-PL-SA-v1) were published in 2022. MulanOWL BY-SA v1 and MulanOWL BY-PL-SA v1 are copyright licenses with a ShareAlike mechanism and an attribution mechanism, and [http://freedomdefined.org/Licenses#Free_Art_License they do not violate the definition of Free Cultural Licenses]. Thus, it satisfies the [[ShareAlike_compatibility_process_and_criteria#Minimum_compatibility_criteria.|minimum criteria]] for compatibility set forth in our [[ShareAlike_compatibility_process_and_criteria|ShareAlike compatibility criteria]].

MulanOWL BY-PL-SA v1 grants patent rights and is not compatible with CC BY-SA 4.0.

MulanOWL BY-SA v1 is similar to CC BY-SA 4.0 overall, and the effect of each license as applied to a creative work is largely the same. Inevitably, there are differences between the licenses, which are explained in more detail below.

'''Summary of comparison: MulanOWL BY-SA v1<ref>Note that CC reviewed the English language version of the MulanOWL BY-SA v1 and MulanOWL BY-PL-SA v1 to conduct this analysis.</ref> and BY-SA 4.0'''

*It appears that the MulanOWL BY-SA v1 license referenced the CC BY-SA 4.0 license in its development. We are not sure what decisions went into the choices that made some portion of MulanOWL BY-SA v1 diverge from CC BY-SA 4.0. The steward of Mulan licenses pointed to LearnerHub as a repository for works licensed under Mulan BY-SA v1 license.

*The specific attribution and marking requirements in the two licenses vary slightly. CC BY-SA 4.0 allows for more flexibility depending on the context in which the work is used. Most notably, MulanOWL BY-SA v1 asks users to retain trademark and patent statements.

*We are particularly concerned that, unlike CC BY-SA 4.0, MulanOWL BY-SA v1 does not mention database rights, nor does it mention related rights. This could be because copyright in China is construed as including related rights and moral rights that are never waivable.

*The ShareAlike scope of MulanOWL BY-SA v1 is likely broader.

*MulanOWL BY-SA v1 does not terminate even upon breach, as long as the breach was cured prior to, or within 30 days of, receiving notice of termination. This may create some ambiguity, such as whether a licensor can collect damages during the period when a breach has happened but no notice is yet sent. CC BY-SA terminates automatically upon breach, but is reinstated automatically if the breach is cured within 30 days of discovery.

*

{| style="border-collapse: collapse;" border="1" cellpadding="10"
|-
! style="background-color:#CCCCCC;" | Features || style="background-color:#CCCCCC;" | BY-SA 4.0 || style="background-color:#CCCCCC;" | MulanOWL BY-SA v1
|-
| License scope || Copyright, neighboring rights and sui generis database rights (SGDRs) (Sec 1d) || Copyright only (Sec 1)
|-
| Attribution trigger || If there is applicable copyright in work, then when work or adaptation of work is shared. (Sec 3a)
<br>
If there are applicable SGDRs in work, then when all or a substantial portion of database contents is shared. (Sec 4c)
|| When work (modified or not) is disseminated (Sec 3)
|-
| Attribution removal clause || Yes (Sec 3a3) || No
|-
| Attribution elements ||
#creator and attribution parties
#copyright notice
# license notice
# disclaimer notice
# URI or link to the licensed material
# indicate and link to license
(Sec 3a1)
<br>
||
#name of licensor
#copyright statement
#license notice
#modification statements
#patent statements
# trademark statements
# disclaimer statements
# URI or link to the licensed material
# indicate and link to license
# title and version of the work (optional)
(Sec 3)
|-
| Special marking requirement if work is modified || Yes (indicate if you modified and retain indication of previous modifications) (Sec 3a1B)
|| Yes (indicate if you modified and retain indication of previous modifications) (Sec 3(3) and Sec 3(4))
|-
| ShareAlike trigger || When adaptation is shared (Sec 3b) || When adaptation is shared (Sec 3(3))
|-
| ShareAlike scope || Must ShareAlike contributions to adaptations (Sec 3b);
<br>
Must ShareAlike database if it incorporates substantial portion of database contents (Sec 4b)
|| Must ShareAlike contributions to adaptations (Sec 3(3))
|-
| Source requirement || None || None
|-
| Effective technological measures || May not be applied by licensees if they restrict access to the work or adaptations (Sec 2a5C)
<br>
Licensees have express permission to circumvent if applied by licensor (Sec 2a4)
|| May not be applied by licensees if they restrict access to the work or adaptations (Sec 3(4))
<br>
Licensees have express permission to circumvent even when applied by a third party (Sec 3(4))
|-
| Moral rights || Waived only to the extent necessary to allow the license to function. (Sec 2b1) || Not mentioned
|-
| Termination || Automatic upon breach (Sec 6a) || Terminate upon the receipt of the termination notice from the licensors, unless (1) licensee has cured all the breaches prior to receipt of such notice of termination; or,(2) it’s Licensee's first time to receive a notice of termination from the Licensor, and the licensee has cured all the breaches within 30 days of receipt of such notice; or,(3) licensor has expressly reinstated the license granted to You.(Sec 4.1)
|-
| Reinstatement after termination || Requires express permission unless cured within 30 days of discovery of violation (Sec 6b) || None
|-
| Reps & warranties || Expressly disclaimed (Sec 5) || Expressly disclaimed (Sec 5)
|-
| Choice of law || None || None
|-
| Option to comply with other license versions
|| Yes, but limited. Licensees may choose to comply with a later version of BY-SA if such version is applied to an adaptation of the work.
(Secs 2a5B, 3b1)
|| Yes, but limited. Licensees may choose to comply with a later version of MulanOWL BY-SA if such version is applied to an adaptation of the work.(Sec 3(3))
|}

== Notes ==
<references/>

ShareAlike compatibility analysis: Mulan

2023-11-10T20:35:40Z

CCID-yuanxiaoxu:

“Mulan Open Works License Attribution-ShareAlike, Version 1” (MulanOWL BY-SA v1, http://openworks.mulanos.cn/#/licenses/MulanOWL_BY-SA-v1) and “Mulan Open Works License Attribution-PatentLicensed-ShareAlike, Version 1” (MulanOWL BY-PL-SA v1, http://openworks.mulanos.cn/#/licenses/MulanOWL_BY-PL-SA-v1) were published in 2022. MulanOWL BY-SA v1 and MulanOWL BY-PL-SA v1 are copyright licenses with a ShareAlike mechanism and an attribution mechanism, and [http://freedomdefined.org/Licenses#Free_Art_License they do not violate the definition of Free Cultural Licenses]. Thus, it satisfies the [[ShareAlike_compatibility_process_and_criteria#Minimum_compatibility_criteria.|minimum criteria]] for compatibility set forth in our [[ShareAlike_compatibility_process_and_criteria|ShareAlike compatibility criteria]].

MulanOWL BY-PL-SA v1 grants patent rights and is not compatible with CC BY-SA 4.0.

MulanOWL BY-SA v1 is similar to CC BY-SA 4.0 overall, and the effect of each license as applied to a creative work is largely the same. Inevitably, there are differences between the licenses, which are explained in more detail below.

'''Summary of comparison: MulanOWL BY-SA v1<ref>Note that CC reviewed the English language version of the MulanOWL BY-SA v1 and MulanOWL BY-PL-SA v1 to conduct this analysis.</ref> and BY-SA 4.0'''

*It appears that the MulanOWL BY-SA v1 license referenced the CC BY-SA 4.0 license in its development. We are not sure what decisions went into the choices that made some portion of MulanOWL BY-SA v1 diverge from CC BY-SA 4.0, and we do not know what use cases MulanOWL BY-SA v1 contemplates that cannot already be accomplished by the CC BY-SA 4.0 license.

*The specific attribution and marking requirements in the two licenses vary slightly. CC BY-SA 4.0 allows for more flexibility depending on the context in which the work is used. Most notably, MulanOWL BY-SA v1 asks users to retain trademark and patent statements.

*Unlike CC BY-SA 4.0, MulanOWL BY-SA v1 does not mention database rights. Nor does it mention related rights—which could be because copyright in China is construed as including related rights and moral rights.

*The ShareAlike scope of MulanOWL BY-SA v1 is likely broader.

*MulanOWL BY-SA v1 does not terminate even upon breach, as long as the breach was cured prior to, or within 30 days of, receiving notice of termination. This may create some ambiguity, such as whether a licensor can collect damages during the period when a breach has happened but no notice is yet sent. CC BY-SA terminates automatically upon breach, but is reinstated automatically if the breach is cured within 30 days of discovery.

*

{| style="border-collapse: collapse;" border="1" cellpadding="10"
|-
! style="background-color:#CCCCCC;" | Features || style="background-color:#CCCCCC;" | BY-SA 4.0 || style="background-color:#CCCCCC;" | MulanOWL BY-SA v1
|-
| License scope || Copyright, neighboring rights and sui generis database rights (SGDRs) (Sec 1d) || Copyright only (Sec 1)
|-
| Attribution trigger || If there is applicable copyright in work, then when work or adaptation of work is shared. (Sec 3a)
<br>
If there are applicable SGDRs in work, then when all or a substantial portion of database contents is shared. (Sec 4c)
|| When work (modified or not) is disseminated (Sec 3)
|-
| Attribution removal clause || Yes (Sec 3a3) || No
|-
| Attribution elements ||
#creator and attribution parties
#copyright notice
# license notice
# disclaimer notice
# URI or link to the licensed material
# indicate and link to license
(Sec 3a1)
<br>
||
#name of licensor
#copyright statement
#license notice
#modification statements
#patent statements
# trademark statements
# disclaimer statements
# URI or link to the licensed material
# indicate and link to license
# title and version of the work (optional)
(Sec 3)
|-
| Special marking requirement if work is modified || Yes (indicate if you modified and retain indication of previous modifications) (Sec 3a1B)
|| Yes (indicate if you modified and retain indication of previous modifications) (Sec 3(3) and Sec 3(4))
|-
| ShareAlike trigger || When adaptation is shared (Sec 3b) || When adaptation is shared (Sec 3(3))
|-
| ShareAlike scope || Must ShareAlike contributions to adaptations (Sec 3b);
<br>
Must ShareAlike database if it incorporates substantial portion of database contents (Sec 4b)
|| Must ShareAlike contributions to adaptations (Sec 3(3))
|-
| Source requirement || None || None
|-
| Effective technological measures || May not be applied by licensees if they restrict access to the work or adaptations (Sec 2a5C)
<br>
Licensees have express permission to circumvent if applied by licensor (Sec 2a4)
|| May not be applied by licensees if they restrict access to the work or adaptations (Sec 3(4))
<br>
Licensees have express permission to circumvent even when applied by a third party (Sec 3(4))
|-
| Moral rights || Waived only to the extent necessary to allow the license to function. (Sec 2b1) || Not mentioned
|-
| Termination || Automatic upon breach (Sec 6a) || Terminate upon the receipt of the termination notice from the licensors, unless (1) licensee has cured all the breaches prior to receipt of such notice of termination; or,(2) it’s Licensee's first time to receive a notice of termination from the Licensor, and the licensee has cured all the breaches within 30 days of receipt of such notice; or,(3) licensor has expressly reinstated the license granted to You.(Sec 4.1)
|-
| Reinstatement after termination || Requires express permission unless cured within 30 days of discovery of violation (Sec 6b) || None
|-
| Reps & warranties || Expressly disclaimed (Sec 5) || Expressly disclaimed (Sec 5)
|-
| Choice of law || None || None
|-
| Option to comply with other license versions
|| Yes, but limited. Licensees may choose to comply with a later version of BY-SA if such version is applied to an adaptation of the work.
(Secs 2a5B, 3b1)
|| Yes, but limited. Licensees may choose to comply with a later version of MulanOWL BY-SA if such version is applied to an adaptation of the work.(Sec 3(3))
|}

== Notes ==
<references/>

ShareAlike compatibility analysis: Mulan

2023-11-10T20:31:38Z

CCID-yuanxiaoxu:

“Mulan Open Works License Attribution-ShareAlike, Version 1” (MulanOWL BY-SA v1, http://openworks.mulanos.cn/#/licenses/MulanOWL_BY-SA-v1) and “Mulan Open Works License Attribution-PatentLicensed-ShareAlike, Version 1” (MulanOWL BY-PL-SA v1, http://openworks.mulanos.cn/#/licenses/MulanOWL_BY-PL-SA-v1) were published in 2022. MulanOWL BY-SA v1 and MulanOWL BY-PL-SA v1 are copyright licenses with a ShareAlike mechanism and an attribution mechanism, and [http://freedomdefined.org/Licenses#Free_Art_License they do not violate the definition of Free Cultural Licenses]. Thus, it satisfies the [[ShareAlike_compatibility_process_and_criteria#Minimum_compatibility_criteria.|minimum criteria]] for compatibility set forth in our [[ShareAlike_compatibility_process_and_criteria|ShareAlike compatibility criteria]].

MulanOWL BY-PL-SA v1 grants patent rights and is not compatible with CC BY-SA 4.0.

MulanOWL BY-SA v1 is similar to CC BY-SA 4.0 overall, and the effect of each license as applied to a creative work is largely the same. Inevitably, there are differences between the licenses, which are explained in more detail below.

'''Summary of comparison: MulanOWL BY-SA v1<ref>Note that CC reviewed the English language version of the MulanOWL BY-SA v1 and MulanOWL BY-PL-SA v1 to conduct this analysis.</ref> and BY-SA 4.0'''

*It appears that the MulanOWL BY-SA v1 license referenced the CC BY-SA 4.0 license in its development. We are not sure what decisions went into the choices that made some portion of MulanOWL BY-SA v1 diverge from CC BY-SA 4.0, and we do not know what use cases MulanOWL BY-SA v1 contemplates that cannot already be accomplished by the CC BY-SA 4.0 license.

*The specific attribution and marking requirements in the two licenses vary slightly. CC BY-SA 4.0 allows for more flexibility depending on the context in which the work is used. Most notably, MulanOWL BY-SA v1 asks users to retain trademark and patent statements.

*Unlike CC BY-SA 4.0, MulanOWL BY-SA v1 does not mention database rights. Nor does it mention related rights—which could be because copyright in China is construed as including related rights and moral rights.

*The ShareAlike scope of MulanOWL BY-SA v1 is likely broader.

*MulanOWL BY-SA v1 does not terminate even upon breach, as long as the breach was cured prior to, or within 30 days of, receiving notice of termination. This may create some ambiguity, such as whether a licensor can collect damages during the period when a breach has happened but no notice is yet sent. CC BY-SA terminates automatically upon breach, but is reinstated automatically if the breach is cured within 30 days of discovery.

*

{| style="border-collapse: collapse;" border="1" cellpadding="10"
|-
! style="background-color:#CCCCCC;" | Features || style="background-color:#CCCCCC;" | BY-SA 4.0 || style="background-color:#CCCCCC;" | MulanOWL BY-SA v1
|-
| License scope || Copyright, neighboring rights and sui generis database rights (SGDRs) (Sec 1d) || Copyright only (Sec 1)
|-
| Attribution trigger || If there is applicable copyright in work, then when work or adaptation of work is shared. (Sec 3a)
<br>
If there are applicable SGDRs in work, then when all or a substantial portion of database contents is shared. (Sec 4c)
|| When work (modified or not) is disseminated (Sec 3)
|-
| Attribution removal clause || Yes (Sec 3a3) || No
|-
| Attribution elements ||
#creator and attribution parties
#copyright notice
# license notice
# disclaimer notice
# URI or link to the licensed material
# indicate and link to license
(Sec 3a1)
<br>
||
#name of licensor
#copyright statement
#license notice
#modification statements
#patent statements
# trademark statements
# disclaimer statements
# URI or link to the licensed material
# indicate and link to license
# title and version of the work (optional)
(Sec 3)
|-
| Special marking requirement if work is modified || Yes (indicate if you modified and retain indication of previous modifications) (Sec 3a1B)
|| Yes (indicate if you modified and retain indication of previous modifications) (Sec 3(3) and Sec 3(4))
|-
| ShareAlike trigger || When adaptation is shared (Sec 3b) || When adaptation is shared (Sec 3(3))
|-
| ShareAlike scope || Must ShareAlike contributions to adaptations (Sec 3b);
<br>
Must ShareAlike database if it incorporates substantial portion of database contents (Sec 4b)
|| Must ShareAlike contributions to adaptations (Sec 3(3))
|-
| Source requirement || None || None
|-
| Effective technological measures || May not be applied by licensees if they restrict access to the work or adaptations (Sec 2a5C)
<br>
Licensees have express permission to circumvent if applied by licensor (Sec 2a4)
|| May not be applied by licensees if they restrict access to the work or adaptations (Sec 3(4))
<br>
Licensees have express permission to circumvent if applied by licensor (Sec 3(4))
|-
| Moral rights || Waived only to the extent necessary to allow the license to function. (Sec 2b1) || Not mentioned
|-
| Termination || Automatic upon breach (Sec 6a) || Terminate upon the receipt of the termination notice from the licensors, unless (1) licensee has cured all the breaches prior to receipt of such notice of termination; or,(2) it’s Licensee's first time to receive a notice of termination from the Licensor, and the licensee has cured all the breaches within 30 days of receipt of such notice; or,(3) licensor has expressly reinstated the license granted to You.(Sec 4.1)
|-
| Reinstatement after termination || Requires express permission unless cured within 30 days of discovery of violation (Sec 6b) || None
|-
| Reps & warranties || Expressly disclaimed (Sec 5) || Expressly disclaimed (Sec 5)
|-
| Choice of law || None || None
|-
| Option to comply with other license versions
|| Yes, but limited. Licensees may choose to comply with a later version of BY-SA if such version is applied to an adaptation of the work.
(Secs 2a5B, 3b1)
|| Yes, but limited. Licensees may choose to comply with a later version of MulanOWL BY-SA if such version is applied to an adaptation of the work.(Sec 3(3))
|}

== Notes ==
<references/>

ShareAlike compatibility analysis: Mulan

2023-11-10T20:29:35Z

CCID-yuanxiaoxu:

“Mulan Open Works License Attribution-ShareAlike, Version 1” (MulanOWL BY-SA v1, http://openworks.mulanos.cn/#/licenses/MulanOWL_BY-SA-v1) and “Mulan Open Works License Attribution-PatentLicensed-ShareAlike, Version 1” (MulanOWL BY-PL-SA v1, http://openworks.mulanos.cn/#/licenses/MulanOWL_BY-PL-SA-v1) were published in 2022. MulanOWL BY-SA v1 and MulanOWL BY-PL-SA v1 are copyright licenses with a ShareAlike mechanism and an attribution mechanism, and [http://freedomdefined.org/Licenses#Free_Art_License they do not violate the definition of Free Cultural Licenses]. Thus, it satisfies the [[ShareAlike_compatibility_process_and_criteria#Minimum_compatibility_criteria.|minimum criteria]] for compatibility set forth in our [[ShareAlike_compatibility_process_and_criteria|ShareAlike compatibility criteria]].

MulanOWL BY-PL-SA v1 grants patent rights and is not compatible with CC BY-SA 4.0.

MulanOWL BY-SA v1 is similar to CC BY-SA 4.0 overall, and the effect of each license as applied to a creative work is largely the same. Inevitably, there are differences between the licenses, which are explained in more detail below.

'''Summary of comparison: MulanOWL BY-SA v1<ref>Note that CC reviewed the English language version of the MulanOWL BY-SA v1 and MulanOWL BY-PL-SA v1 to conduct this analysis.</ref> and BY-SA 4.0'''

*It appears that the MulanOWL BY-SA v1 license referenced the CC BY-SA 4.0 license in its development. We are not sure what decisions went into the choices that made some portion of MulanOWL BY-SA v1 diverge from CC BY-SA 4.0, and we do not know what use cases MulanOWL BY-SA v1 contemplates that cannot already be accomplished by the CC BY-SA 4.0 license.

*The specific attribution and marking requirements in the two licenses vary slightly. CC BY-SA 4.0 allows for more flexibility depending on the context in which the work is used. Most notably, MulanOWL BY-SA v1 asks users to retain trademark and patent statements.

*Unlike CC BY-SA 4.0, MulanOWL BY-SA v1 does not mention database rights. Nor does it mention related rights—which could be because copyright in China is construed as including related rights and moral rights.

*MulanOWL BY-SA v1 does not terminate even upon breach, as long as the breach was cured prior to, or within 30 days of, receiving notice of termination. This may create some ambiguity, such as whether a licensor can collect damages during the period when a breach has happened but no notice is yet sent. CC BY-SA terminates automatically upon breach, but is reinstated automatically if the breach is cured within 30 days of discovery.

*

{| style="border-collapse: collapse;" border="1" cellpadding="10"
|-
! style="background-color:#CCCCCC;" | Features || style="background-color:#CCCCCC;" | BY-SA 4.0 || style="background-color:#CCCCCC;" | MulanOWL BY-SA v1
|-
| License scope || Copyright, neighboring rights and sui generis database rights (SGDRs) (Sec 1d) || Copyright only (Sec 1)
|-
| Attribution trigger || If there is applicable copyright in work, then when work or adaptation of work is shared. (Sec 3a)
<br>
If there are applicable SGDRs in work, then when all or a substantial portion of database contents is shared. (Sec 4c)
|| When work (modified or not) is disseminated (Sec 3)
|-
| Attribution removal clause || Yes (Sec 3a3) || No
|-
| Attribution elements ||
#creator and attribution parties
#copyright notice
# license notice
# disclaimer notice
# URI or link to the licensed material
# indicate and link to license
(Sec 3a1)
<br>
||
#name of licensor
#copyright statement
#license notice
#modification statements
#patent statements
# trademark statements
# disclaimer statements
# URI or link to the licensed material
# indicate and link to license
# title and version of the work (optional)
(Sec 3)
|-
| Special marking requirement if work is modified || Yes (indicate if you modified and retain indication of previous modifications) (Sec 3a1B)
|| Yes (indicate if you modified and retain indication of previous modifications) (Sec 3(3) and Sec 3(4))
|-
| ShareAlike trigger || When adaptation is shared (Sec 3b) || When adaptation is shared (Sec 3(3))
|-
| ShareAlike scope || Must ShareAlike contributions to adaptations (Sec 3b);
<br>
Must ShareAlike database if it incorporates substantial portion of database contents (Sec 4b)
|| Must ShareAlike contributions to adaptations (Sec 3(3))
|-
| Source requirement || None || None
|-
| Effective technological measures || May not be applied by licensees if they restrict access to the work or adaptations (Sec 2a5C)
<br>
Licensees have express permission to circumvent if applied by licensor (Sec 2a4)
|| May not be applied by licensees if they restrict access to the work or adaptations (Sec 3(4))
<br>
Licensees have express permission to circumvent if applied by licensor (Sec 3(4))
|-
| Moral rights || Waived only to the extent necessary to allow the license to function. (Sec 2b1) || Not mentioned
|-
| Termination || Automatic upon breach (Sec 6a) || Terminate upon the receipt of the termination notice from the licensors, unless (1) licensee has cured all the breaches prior to receipt of such notice of termination; or,(2) it’s Licensee's first time to receive a notice of termination from the Licensor, and the licensee has cured all the breaches within 30 days of receipt of such notice; or,(3) licensor has expressly reinstated the license granted to You.(Sec 4.1)
|-
| Reinstatement after termination || Requires express permission unless cured within 30 days of discovery of violation (Sec 6b) || None
|-
| Reps & warranties || Expressly disclaimed (Sec 5) || Expressly disclaimed (Sec 5)
|-
| Choice of law || None || None
|-
| Option to comply with other license versions
|| Yes, but limited. Licensees may choose to comply with a later version of BY-SA if such version is applied to an adaptation of the work.
(Secs 2a5B, 3b1)
|| Yes, but limited. Licensees may choose to comply with a later version of MulanOWL BY-SA if such version is applied to an adaptation of the work.(Sec 3(3))
|}

== Notes ==
<references/>

ShareAlike compatibility analysis: Mulan

2023-11-10T20:25:53Z

CCID-yuanxiaoxu:

“Mulan Open Works License Attribution-ShareAlike, Version 1” (MulanOWL BY-SA v1, http://openworks.mulanos.cn/#/licenses/MulanOWL_BY-SA-v1) and “Mulan Open Works License Attribution-PatentLicensed-ShareAlike, Version 1” (MulanOWL BY-PL-SA v1, http://openworks.mulanos.cn/#/licenses/MulanOWL_BY-PL-SA-v1) were published in 2022. MulanOWL BY-SA v1 and MulanOWL BY-PL-SA v1 are copyright licenses with a ShareAlike mechanism and an attribution mechanism, and [http://freedomdefined.org/Licenses#Free_Art_License they do not violate the definition of Free Cultural Licenses]. Thus, it satisfies the [[ShareAlike_compatibility_process_and_criteria#Minimum_compatibility_criteria.|minimum criteria]] for compatibility set forth in our [[ShareAlike_compatibility_process_and_criteria|ShareAlike compatibility criteria]].

MulanOWL BY-PL-SA v1 grants patent rights and is not compatible with CC BY-SA 4.0.

MulanOWL BY-SA v1 is similar to CC BY-SA 4.0 overall, and the effect of each license as applied to a creative work is largely the same. Inevitably, there are differences between the licenses, which are explained in more detail below.

'''Summary of comparison: MulanOWL BY-SA v1<ref>Note that CC reviewed the English language version of the MulanOWL BY-SA v1 and MulanOWL BY-PL-SA v1 to conduct this analysis.</ref> and BY-SA 4.0'''

*It appears that the MulanOWL BY-SA v1 license referenced the CC BY-SA 4.0 license in its development. We are not sure what decisions went into the choices that made some portion of MulanOWL BY-SA v1 diverge from CC BY-SA 4.0, and we do not know what use cases MulanOWL BY-SA v1 contemplates that cannot already be accomplished by the CC BY-SA 4.0 license.

*The specific attribution and marking requirements in the two licenses vary slightly. CC BY-SA 4.0 allows for more flexibility depending on the context in which the work is used.

*Unlike CC BY-SA 4.0, MulanOWL BY-SA v1 does not mention database rights. Nor does it mention related rights—which could be because copyright in China is construed as including related rights and moral rights.

*MulanOWL BY-SA v1 does not terminate even upon breach, as long as the breach was cured prior to, or within 30 days of, receiving notice of termination. This may create some ambiguity, such as whether a licensor can collect damages during the period when a breach has happened but no notice is yet sent. CC BY-SA terminates automatically upon breach, but is reinstated automatically if the breach is cured within 30 days of discovery.

*

{| style="border-collapse: collapse;" border="1" cellpadding="10"
|-
! style="background-color:#CCCCCC;" | Features || style="background-color:#CCCCCC;" | BY-SA 4.0 || style="background-color:#CCCCCC;" | MulanOWL BY-SA v1
|-
| License scope || Copyright, neighboring rights and sui generis database rights (SGDRs) (Sec 1d) || Copyright only (Sec 1)
|-
| Attribution trigger || If there is applicable copyright in work, then when work or adaptation of work is shared. (Sec 3a)
<br>
If there are applicable SGDRs in work, then when all or a substantial portion of database contents is shared. (Sec 4c)
|| When work (modified or not) is disseminated (Sec 3)
|-
| Attribution removal clause || Yes (Sec 3a3) || No
|-
| Attribution elements ||
#creator and attribution parties
#copyright notice
# license notice
# disclaimer notice
# URI or link to the licensed material
# indicate and link to license
(Sec 3a1)
<br>
||
#name of licensor
#copyright statement
#license notice
#modification statements
#patent statements
# trademark statements
# disclaimer statements
# URI or link to the licensed material
# indicate and link to license
# title and version of the work (optional)
(Sec 3)
|-
| Special marking requirement if work is modified || Yes (indicate if you modified and retain indication of previous modifications) (Sec 3a1B)
|| Yes (indicate if you modified and retain indication of previous modifications) (Sec 3(3) and Sec 3(4))
|-
| ShareAlike trigger || When adaptation is shared (Sec 3b) || When adaptation is shared (Sec 3(3))
|-
| ShareAlike scope || Must ShareAlike contributions to adaptations (Sec 3b);
<br>
Must ShareAlike database if it incorporates substantial portion of database contents (Sec 4b)
|| Must ShareAlike contributions to adaptations (Sec 3(3))
|-
| Source requirement || None || None
|-
| Effective technological measures || May not be applied by licensees if they restrict access to the work or adaptations (Sec 2a5C)
<br>
Licensees have express permission to circumvent if applied by licensor (Sec 2a4)
|| May not be applied by licensees if they restrict access to the work or adaptations (Sec 3(4))
<br>
Licensees have express permission to circumvent if applied by licensor (Sec 3(4))
|-
| Moral rights || Waived only to the extent necessary to allow the license to function. (Sec 2b1) || Not mentioned
|-
| Termination || Automatic upon breach (Sec 6a) || Terminate upon the receipt of the termination notice from the licensors, unless (1) licensee has cured all the breaches prior to receipt of such notice of termination; or,(2) it’s Licensee's first time to receive a notice of termination from the Licensor, and the licensee has cured all the breaches within 30 days of receipt of such notice; or,(3) licensor has expressly reinstated the license granted to You.(Sec 4.1)
|-
| Reinstatement after termination || Requires express permission unless cured within 30 days of discovery of violation (Sec 6b) || None
|-
| Reps & warranties || Expressly disclaimed (Sec 5) || Expressly disclaimed (Sec 5)
|-
| Choice of law || None || None
|-
| Option to comply with other license versions
|| Yes, but limited. Licensees may choose to comply with a later version of BY-SA if such version is applied to an adaptation of the work.
(Secs 2a5B, 3b1)
|| Yes, but limited. Licensees may choose to comply with a later version of MulanOWL BY-SA if such version is applied to an adaptation of the work.(Sec 3(3))
|}

== Notes ==
<references/>

ShareAlike compatibility analysis: Mulan

2023-11-10T20:23:18Z

CCID-yuanxiaoxu:

“Mulan Open Works License Attribution-ShareAlike, Version 1” (MulanOWL BY-SA v1, http://openworks.mulanos.cn/#/licenses/MulanOWL_BY-SA-v1) and “Mulan Open Works License Attribution-PatentLicensed-ShareAlike, Version 1” (MulanOWL BY-PL-SA v1, http://openworks.mulanos.cn/#/licenses/MulanOWL_BY-PL-SA-v1) were published in 2022. MulanOWL BY-SA v1 and MulanOWL BY-PL-SA v1 are copyright licenses with a ShareAlike mechanism and an attribution mechanism, and [http://freedomdefined.org/Licenses#Free_Art_License they do not violate the definition of Free Cultural Licenses]. Thus, it satisfies the [[ShareAlike_compatibility_process_and_criteria#Minimum_compatibility_criteria.|minimum criteria]] for compatibility set forth in our [[ShareAlike_compatibility_process_and_criteria|ShareAlike compatibility criteria]].

MulanOWL BY-PL-SA v1 grants patent rights and is not compatible with CC BY-SA 4.0.

MulanOWL BY-SA v1 is similar to CC BY-SA 4.0 overall, and the effect of each license as applied to a creative work is largely the same. Inevitably, there are differences between the licenses, which are explained in more detail below.

'''Summary of comparison: MulanOWL BY-SA v1<ref>Note that CC reviewed the English language version of the MulanOWL BY-SA v1 and MulanOWL BY-PL-SA v1 to conduct this analysis.</ref> and BY-SA 4.0'''

*It appears that the MulanOWL BY-SA v1 license referenced the CC BY-SA 4.0 license in its development. We are not sure what decisions went into the choices that made some portion of MulanOWL BY-SA v1 diverge from CC BY-SA 4.0, and we do not know what use cases MulanOWL BY-SA v1 contemplates that cannot already be accomplished by the CC BY-SA 4.0 license.

*The specific attribution and marking requirements in the two licenses vary slightly. CC BY-SA 4.0 allows for more flexibility depending on the context in which the work is used.

*Unlike CC BY-SA 4.0, MulanOWL BY-SA v1 does not mention database rights. Nor does it mention related rights—which could be because copyright in China is construed as including related rights and moral rights.

*MulanOWL BY-SA v1 does not terminate even upon breach, as long as the breach was cured prior to, or within 30 days of, receiving notice of termination. This may create some ambiguity, such as whether a licensor can collect damages during the period when a breach has happened but no notice is yet sent. CC BY-SA terminates automatically upon breach, but is reinstated automatically if the breach is cured within 30 days of discovery.

*

{| style="border-collapse: collapse;" border="1" cellpadding="10"
|-
! style="background-color:#CCCCCC;" | Features || style="background-color:#CCCCCC;" | BY-SA 4.0 || style="background-color:#CCCCCC;" | MulanOWL BY-SA v1
|-
| License scope || Copyright, neighboring rights and sui generis database rights (SGDRs) (Sec 1d) || Copyright only, but related rights may not challenge rights granted by license (Sec 1)
|-
| Attribution trigger || If there is applicable copyright in work, then when work or adaptation of work is shared. (Sec 3a)
<br>
If there are applicable SGDRs in work, then when all or a substantial portion of database contents is shared. (Sec 4c)
|| When work (modified or not) is distributed (Sec 3)
|-
| Attribution removal clause || Yes (Sec 3a3) || No
|-
| Attribution elements ||
#creator and attribution parties
#copyright notice
# license notice
# disclaimer notice
# URI or link to the licensed material
# indicate and link to license
(Sec 3a1)
<br>
||
#name of licensor
#copyright statement
#license notice
#modification statements
#patent statements
# trademark statements
# disclaimer statements
# URI or link to the licensed material
# indicate and link to license
# title and version of the work (optional)
(Sec 3)
|-
| Special marking requirement if work is modified || Yes (indicate if you modified and retain indication of previous modifications) (Sec 3a1B)
|| Yes (indicate if you modified and retain indication of previous modifications) (Sec 3(3) and Sec 3(4))
|-
| ShareAlike trigger || When adaptation is shared (Sec 3b) || When adaptation is shared (Sec 3(3))
|-
| ShareAlike scope || Must ShareAlike contributions to adaptations (Sec 3b);
<br>
Must ShareAlike database if it incorporates substantial portion of database contents (Sec 4b)
|| Must ShareAlike contributions to adaptations (Sec 3(3))
|-
| Source requirement || None || None
|-
| Effective technological measures || May not be applied by licensees if they restrict access to the work or adaptations (Sec 2a5C)
<br>
Licensees have express permission to circumvent if applied by licensor (Sec 2a4)
|| May not be applied by licensees if they restrict access to the work or adaptations (Sec 3(4))
<br>
Licensees have express permission to circumvent if applied by licensor (Sec 3(4))
|-
| Moral rights || Waived only to the extent necessary to allow the license to function. (Sec 2b1) || Not mentioned
|-
| Termination || Automatic upon breach (Sec 6a) || Terminate upon the receipt of the termination notice from the licensors, unless (1) licensee has cured all the breaches prior to receipt of such notice of termination; or,(2) it’s Licensee's first time to receive a notice of termination from the Licensor, and the licensee has cured all the breaches within 30 days of receipt of such notice; or,(3) licensor has expressly reinstated the license granted to You.(Sec 4.1)
|-
| Reinstatement after termination || Requires express permission unless cured within 30 days of discovery of violation (Sec 6b) || None
|-
| Reps & warranties || Expressly disclaimed (Sec 5) || Expressly disclaimed (Sec 5)
|-
| Choice of law || None || None
|-
| Option to comply with other license versions
|| Yes, but limited. Licensees may choose to comply with a later version of BY-SA if such version is applied to an adaptation of the work.
(Secs 2a5B, 3b1)
|| Yes, but limited. Licensees may choose to comply with a later version of MulanOWL BY-SA if such version is applied to an adaptation of the work.(Sec 3(3))
|}

== Notes ==
<references/>

ShareAlike compatibility analysis: Mulan

2023-11-10T20:19:02Z

CCID-yuanxiaoxu:

“Mulan Open Works License Attribution-ShareAlike, Version 1” (MulanOWL BY-SA v1, http://openworks.mulanos.cn/#/licenses/MulanOWL_BY-SA-v1) and “Mulan Open Works License Attribution-PatentLicensed-ShareAlike, Version 1” (MulanOWL BY-PL-SA v1, http://openworks.mulanos.cn/#/licenses/MulanOWL_BY-PL-SA-v1) were published in 2022. MulanOWL BY-SA v1 and MulanOWL BY-PL-SA v1 are copyright licenses with a ShareAlike mechanism and an attribution mechanism, and [http://freedomdefined.org/Licenses#Free_Art_License they do not violate the definition of Free Cultural Licenses]. Thus, it satisfies the [[ShareAlike_compatibility_process_and_criteria#Minimum_compatibility_criteria.|minimum criteria]] for compatibility set forth in our [[ShareAlike_compatibility_process_and_criteria|ShareAlike compatibility criteria]].

MulanOWL BY-PL-SA v1 grants patent rights and is not compatible with CC BY-SA 4.0.

MulanOWL BY-SA v1 is similar to CC BY-SA 4.0 overall, and the effect of each license as applied to a creative work is largely the same. Inevitably, there are differences between the licenses, which are explained in more detail below.

'''Summary of comparison: MulanOWL BY-SA v1<ref>Note that CC reviewed the English language version of the MulanOWL BY-SA v1 and MulanOWL BY-PL-SA v1 to conduct this analysis.</ref> and BY-SA 4.0'''

*It appears that the MulanOWL BY-SA v1 license referenced the CC BY-SA 4.0 license in its development. We are not sure what decisions went into the choices that diverged from the CC BY-SA 4.0 license, and we do not know what use cases MulanOWL BY-SA v1 contemplates that cannot already be accomplished by the CC BY-SA 4.0 license.

*The specific attribution and marking requirements in the two licenses vary slightly. CC BY-SA allows for more flexibility depending on the context in which the work is used.

*

*MulanOWL BY-SA v1 does not terminate even upon breach, as long as the breach was cured prior to, or within 30 days of, receiving notice of termination. This may create some ambiguity, such as whether a licensor can collect damages during the period when a breach has happened but no notice is yet sent. CC BY-SA terminates automatically upon breach, but is reinstated automatically if the breach is cured within 30 days of discovery.

*

{| style="border-collapse: collapse;" border="1" cellpadding="10"
|-
! style="background-color:#CCCCCC;" | Features || style="background-color:#CCCCCC;" | BY-SA 4.0 || style="background-color:#CCCCCC;" | MulanOWL BY-SA v1
|-
| License scope || Copyright, neighboring rights and sui generis database rights (SGDRs) (Sec 1d) || Copyright only, but related rights may not challenge rights granted by license (Sec 1)
|-
| Attribution trigger || If there is applicable copyright in work, then when work or adaptation of work is shared. (Sec 3a)
<br>
If there are applicable SGDRs in work, then when all or a substantial portion of database contents is shared. (Sec 4c)
|| When work (modified or not) is distributed (Sec 3)
|-
| Attribution removal clause || Yes (Sec 3a3) || No
|-
| Attribution elements ||
#creator and attribution parties
#copyright notice
# license notice
# disclaimer notice
# URI or link to the licensed material
# indicate and link to license
(Sec 3a1)
<br>
||
#name of licensor
#copyright statement
#license notice
#modification statements
#patent statements
# trademark statements
# disclaimer statements
# URI or link to the licensed material
# indicate and link to license
# title and version of the work (optional)
(Sec 3)
|-
| Special marking requirement if work is modified || Yes (indicate if you modified and retain indication of previous modifications) (Sec 3a1B)
|| Yes (indicate if you modified and retain indication of previous modifications) (Sec 3(3) and Sec 3(4))
|-
| ShareAlike trigger || When adaptation is shared (Sec 3b) || When adaptation is shared (Sec 3(3))
|-
| ShareAlike scope || Must ShareAlike contributions to adaptations (Sec 3b);
<br>
Must ShareAlike database if it incorporates substantial portion of database contents (Sec 4b)
|| Must ShareAlike contributions to adaptations (Sec 3(3))
|-
| Source requirement || None || None
|-
| Effective technological measures || May not be applied by licensees if they restrict access to the work or adaptations (Sec 2a5C)
<br>
Licensees have express permission to circumvent if applied by licensor (Sec 2a4)
|| May not be applied by licensees if they restrict access to the work or adaptations (Sec 3(4))
<br>
Licensees have express permission to circumvent if applied by licensor (Sec 3(4))
|-
| Moral rights || Waived only to the extent necessary to allow the license to function. (Sec 2b1) || Not mentioned
|-
| Termination || Automatic upon breach (Sec 6a) || Terminate upon the receipt of the termination notice from the licensors, unless (1) licensee has cured all the breaches prior to receipt of such notice of termination; or,(2) it’s Licensee's first time to receive a notice of termination from the Licensor, and the licensee has cured all the breaches within 30 days of receipt of such notice; or,(3) licensor has expressly reinstated the license granted to You.(Sec 4.1)
|-
| Reinstatement after termination || Requires express permission unless cured within 30 days of discovery of violation (Sec 6b) || None
|-
| Reps & warranties || Expressly disclaimed (Sec 5) || Expressly disclaimed (Sec 5)
|-
| Choice of law || None || None
|-
| Option to comply with other license versions
|| Yes, but limited. Licensees may choose to comply with a later version of BY-SA if such version is applied to an adaptation of the work.
(Secs 2a5B, 3b1)
|| Yes, but limited. Licensees may choose to comply with a later version of MulanOWL BY-SA if such version is applied to an adaptation of the work.(Sec 3(3))
|}

== Notes ==
<references/>

ShareAlike compatibility analysis: Mulan

2023-11-10T20:07:18Z

CCID-yuanxiaoxu:

“Mulan Open Works License Attribution-ShareAlike, Version 1” (MulanOWL BY-SA v1, http://openworks.mulanos.cn/#/licenses/MulanOWL_BY-SA-v1) and “Mulan Open Works License Attribution-PatentLicensed-ShareAlike, Version 1” (MulanOWL BY-PL-SA v1, http://openworks.mulanos.cn/#/licenses/MulanOWL_BY-PL-SA-v1) were published in 2022. MulanOWL BY-SA v1 and MulanOWL BY-PL-SA v1 are copyright licenses with a ShareAlike mechanism and an attribution mechanism, and [http://freedomdefined.org/Licenses#Free_Art_License they do not violate the definition of Free Cultural Licenses]. Thus, it satisfies the [[ShareAlike_compatibility_process_and_criteria#Minimum_compatibility_criteria.|minimum criteria]] for compatibility set forth in our [[ShareAlike_compatibility_process_and_criteria|ShareAlike compatibility criteria]].

MulanOWL BY-PL-SA v1 grants patent rights and is not compatible with CC BY-SA 4.0.

MulanOWL BY-SA v1 is similar to CC BY-SA 4.0 overall, and the effect of each license as applied to a creative work is largely the same. Inevitably, there are differences between the licenses, which are explained in more detail below.

'''Summary of comparison: MulanOWL BY-SA v1<ref>Note that CC reviewed the English language version of the MulanOWL BY-SA v1 and MulanOWL BY-PL-SA v1 to conduct this analysis.</ref> and BY-SA 4.0'''

*The specific attribution and marking requirements in the two licenses vary slightly. CC BY-SA allows for more flexibility depending on the context in which the work is used.

*

*MulanOWL BY-SA v1 does not terminate even upon breach, as long as the breach was cured prior to, or within 30 days of, receiving notice of termination. CC BY-SA terminates automatically upon breach, but is reinstated automatically if the breach is cured within 30 days of discovery.

*

{| style="border-collapse: collapse;" border="1" cellpadding="10"
|-
! style="background-color:#CCCCCC;" | Features || style="background-color:#CCCCCC;" | BY-SA 4.0 || style="background-color:#CCCCCC;" | MulanOWL BY-SA v1
|-
| License scope || Copyright, neighboring rights and sui generis database rights (SGDRs) (Sec 1d) || Copyright only, but related rights may not challenge rights granted by license (Sec 1)
|-
| Attribution trigger || If there is applicable copyright in work, then when work or adaptation of work is shared. (Sec 3a)
<br>
If there are applicable SGDRs in work, then when all or a substantial portion of database contents is shared. (Sec 4c)
|| When work (modified or not) is distributed (Sec 3)
|-
| Attribution removal clause || Yes (Sec 3a3) || No
|-
| Attribution elements ||
#creator and attribution parties
#copyright notice
# license notice
# disclaimer notice
# URI or link to the licensed material
# indicate and link to license
(Sec 3a1)
<br>
||
#name of licensor
#copyright statement
#license notice
#modification statements
#patent statements
# trademark statements
# disclaimer statements
# URI or link to the licensed material
# indicate and link to license
# title and version of the work (optional)
(Sec 3)
|-
| Special marking requirement if work is modified || Yes (indicate if you modified and retain indication of previous modifications) (Sec 3a1B)
|| Yes (indicate if you modified and retain indication of previous modifications) (Sec 3(3) and Sec 3(4))
|-
| ShareAlike trigger || When adaptation is shared (Sec 3b) || When adaptation is shared (Sec 3(3))
|-
| ShareAlike scope || Must ShareAlike contributions to adaptations (Sec 3b);
<br>
Must ShareAlike database if it incorporates substantial portion of database contents (Sec 4b)
|| Must ShareAlike contributions to adaptations (Sec 3(3))
|-
| Source requirement || None || None
|-
| Effective technological measures || May not be applied by licensees if they restrict access to the work or adaptations (Sec 2a5C)
<br>
Licensees have express permission to circumvent if applied by licensor (Sec 2a4)
|| May not be applied by licensees if they restrict access to the work or adaptations (Sec 3(4))
<br>
Licensees have express permission to circumvent if applied by licensor (Sec 3(4))
|-
| Moral rights || Waived only to the extent necessary to allow the license to function. (Sec 2b1) || Not mentioned
|-
| Termination || Automatic upon breach (Sec 6a) || Terminate upon the receipt of the termination notice from the licensors, unless (1) licensee has cured all the breaches prior to receipt of such notice of termination; or,(2) it’s Licensee's first time to receive a notice of termination from the Licensor, and the licensee has cured all the breaches within 30 days of receipt of such notice; or,(3) licensor has expressly reinstated the license granted to You.(Sec 4.1)
|-
| Reinstatement after termination || Requires express permission unless cured within 30 days of discovery of violation (Sec 6b) || None
|-
| Reps & warranties || Expressly disclaimed (Sec 5) || Expressly disclaimed (Sec 5)
|-
| Choice of law || None || None
|-
| Option to comply with other license versions
|| Yes, but limited. Licensees may choose to comply with a later version of BY-SA if such version is applied to an adaptation of the work.
(Secs 2a5B, 3b1)
|| Yes, but limited. Licensees may choose to comply with a later version of MulanOWL BY-SA if such version is applied to an adaptation of the work.(Sec 3(3))
|}

== Notes ==
<references/>

ShareAlike compatibility analysis: Mulan

2023-11-10T20:02:52Z

CCID-yuanxiaoxu:

“Mulan Open Works License Attribution-ShareAlike, Version 1” (MulanOWL BY-SA v1, http://openworks.mulanos.cn/#/licenses/MulanOWL_BY-SA-v1) and “Mulan Open Works License Attribution-PatentLicensed-ShareAlike, Version 1” (MulanOWL BY-PL-SA v1, http://openworks.mulanos.cn/#/licenses/MulanOWL_BY-PL-SA-v1) were published in 2022. MulanOWL BY-SA v1 and MulanOWL BY-PL-SA v1 are copyright licenses with a ShareAlike mechanism and an attribution mechanism, and [http://freedomdefined.org/Licenses#Free_Art_License they do not violate the definition of Free Cultural Licenses]. Thus, it satisfies the [[ShareAlike_compatibility_process_and_criteria#Minimum_compatibility_criteria.|minimum criteria]] for compatibility set forth in our [[ShareAlike_compatibility_process_and_criteria|ShareAlike compatibility criteria]].

MulanOWL BY-PL-SA v1 grants patent rights and is not compatible with CC BY-SA 4.0.

MulanOWL BY-SA v1 is similar to CC BY-SA 4.0 overall, and the effect of each license as applied to a creative work is largely the same. Inevitably, there are differences between the licenses, which are explained in more detail below.

'''Summary of comparison: MulanOWL BY-SA v1<ref>Note that CC reviewed the English language version of the MulanOWL BY-SA v1 and MulanOWL BY-PL-SA v1 to conduct this analysis.</ref> and BY-SA 4.0'''

*The specific attribution and marking requirements in the two licenses vary slightly. CC BY-SA allows for more flexibility depending on the context in which the work is used.

*

*MulanOWL BY-SA v1 does not terminate even upon breach, as long as the breach was cured prior to, or within 30 days of, receiving notice of termination. CC BY-SA terminates automatically upon breach, but is reinstated automatically if the breach is cured within 30 days of discovery.

*

{| style="border-collapse: collapse;" border="1" cellpadding="10"
|-
! style="background-color:#CCCCCC;" | Features || style="background-color:#CCCCCC;" | BY-SA 4.0 || style="background-color:#CCCCCC;" | MulanOWL BY-SA v1 || style="background-color:#CCCCCC;" | MulanOWL BY-PL-SA v1
|-
| License scope || Copyright, neighboring rights and sui generis database rights (SGDRs) (Sec 1d) || Copyright only, but related rights may not challenge rights granted by license (Sec 1) || Copyright and Patent rights, but related rights may not challenge rights granted by license (Sec 1 and Sec 2)
|-
| Attribution trigger || If there is applicable copyright in work, then when work or adaptation of work is shared. (Sec 3a)
<br>
If there are applicable SGDRs in work, then when all or a substantial portion of database contents is shared. (Sec 4c)
|| When work (modified or not) is distributed (Sec 3) || When work (modified or not) is distributed (Sec 4)
|-
| Attribution removal clause || Yes (Sec 3a3) || No || No
|-
| Attribution elements ||
#creator and attribution parties
#copyright notice
# license notice
# disclaimer notice
# URI or link to the licensed material
# indicate and link to license
(Sec 3a1)
<br>
||
#name of licensor
#copyright statement
#license notice
#modification statements
#patent statements
# trademark statements
# disclaimer statements
# URI or link to the licensed material
# indicate and link to license
# title and version of the work (optional)
(Sec 3)
||
#name of licensor
#copyright statement
#license notice
#modification statements
#patent statements
# trademark statements
# disclaimer statements
# URI or link to the licensed material
# indicate and link to license
# title and version of the work (optional)
(Sec 4)
|-
| Special marking requirement if work is modified || Yes (indicate if you modified and retain indication of previous modifications) (Sec 3a1B)
|| Yes (indicate if you modified and retain indication of previous modifications) (Sec 3(3) and Sec 3(4))|| Yes (indicate if you modified and retain indication of previous modifications) (Sec 4(3) and Sec 4(4))
|-
| ShareAlike trigger || When adaptation is shared (Sec 3b) || When adaptation is shared (Sec 3(3)) || When adaptation is shared (Sec 4(3))
|-
| ShareAlike scope || Must ShareAlike contributions to adaptations (Sec 3b);
<br>
Must ShareAlike database if it incorporates substantial portion of database contents (Sec 4b)
|| Must ShareAlike contributions to adaptations (Sec 3(3)) || Must ShareAlike contributions to adaptations (Sec 4(3))
|-
| Source requirement || None || None || None
|-
| Effective technological measures || May not be applied by licensees if they restrict access to the work or adaptations (Sec 2a5C)
<br>
Licensees have express permission to circumvent if applied by licensor (Sec 2a4)
|| May not be applied by licensees if they restrict access to the work or adaptations (Sec 3(4))
<br>
Licensees have express permission to circumvent if applied by licensor (Sec 3(4))
|| May not be applied by licensees if they restrict access to the work or adaptations (Sec 4(4))
<br>
Licensees have express permission to circumvent if applied by licensor (Sec 4(4))
|-
| Moral rights || Waived only to the extent necessary to allow the license to function. (Sec 2b1) || Not mentioned || Not mentioned
|-
| Termination || Automatic upon breach (Sec 6a) || Terminate upon the receipt of the termination notice from the licensors, unless (1) licensee has cured all the breaches prior to receipt of such notice of termination; or,(2) it’s Licensee's first time to receive a notice of termination from the Licensor, and the licensee has cured all the breaches within 30 days of receipt of such notice; or,(3) licensor has expressly reinstated the license granted to You.(Sec 4.1) || Terminate upon the receipt of the termination notice from the licensors, unless (1) licensee has cured all the breaches prior to receipt of such notice of termination; or,(2) it’s Licensee's first time to receive a notice of termination from the Licensor, and the licensee has cured all the breaches within 30 days of receipt of such notice; or,(3) licensor has expressly reinstated the license granted to You.(Sec 5.1)
|-
| Reinstatement after termination || Requires express permission unless cured within 30 days of discovery of violation (Sec 6b) || None || None
|-
| Reps & warranties || Expressly disclaimed (Sec 5) || Expressly disclaimed (Sec 5) || Expressly disclaimed (Sec 6)
|-
| Choice of law || None || None || None
|-
| Option to comply with other license versions
|| Yes, but limited. Licensees may choose to comply with a later version of BY-SA if such version is applied to an adaptation of the work.
(Secs 2a5B, 3b1)
|| Yes, but limited. Licensees may choose to comply with a later version of MulanOWL BY-SA if such version is applied to an adaptation of the work.(Sec 3(3)) || Yes, but limited. Licensees may choose to comply with a later version of MulanOWL BY-SA if such version is applied to an adaptation of the work.(Sec 4(3))
|}

== Notes ==
<references/>

ShareAlike compatibility analysis: Mulan

2023-11-10T20:01:56Z

CCID-yuanxiaoxu:

“Mulan Open Works License Attribution-ShareAlike, Version 1” (MulanOWL BY-SA v1, http://openworks.mulanos.cn/#/licenses/MulanOWL_BY-SA-v1) and “Mulan Open Works License Attribution-PatentLicensed-ShareAlike, Version 1” (MulanOWL BY-PL-SA v1, http://openworks.mulanos.cn/#/licenses/MulanOWL_BY-PL-SA-v1) were published in 2022. MulanOWL BY-SA v1 and MulanOWL BY-PL-SA v1 are copyright licenses with a ShareAlike mechanism and an attribution mechanism, and [http://freedomdefined.org/Licenses#Free_Art_License they do not violate the definition of Free Cultural Licenses]. Thus, it satisfies the [[ShareAlike_compatibility_process_and_criteria#Minimum_compatibility_criteria.|minimum criteria]] for compatibility set forth in our [[ShareAlike_compatibility_process_and_criteria|ShareAlike compatibility criteria]].

MulanOWL BY-PL-SA v1 grants patent rights and is not compatible with CC BY-SA 4.0.

MulanOWL BY-SA v1 is similar to CC BY-SA 4.0 overall, and the effect of each license as applied to a creative work is largely the same. Inevitably, there are differences between the licenses, which are explained in more detail below.

'''Summary of comparison: MulanOWL BY-SA v1 and MulanOWL BY-PL-SA v1<ref>Note that CC reviewed the English language version of the MulanOWL BY-SA v1 and MulanOWL BY-PL-SA v1 to conduct this analysis.</ref> and BY-SA 4.0'''

*The specific attribution and marking requirements in the two licenses vary slightly. CC BY-SA allows for more flexibility depending on the context in which the work is used.

*MulanOWL BY-SA v1 and MulanOWL BY-PL-SA v1 do not terminate even upon breach, as long as the breach was cured prior to, or within 30 days of, receiving notice of termination. CC BY-SA terminates automatically upon breach, but is reinstated automatically if the breach is cured within 30 days of discovery.

*

{| style="border-collapse: collapse;" border="1" cellpadding="10"
|-
! style="background-color:#CCCCCC;" | Features || style="background-color:#CCCCCC;" | BY-SA 4.0 || style="background-color:#CCCCCC;" | MulanOWL BY-SA v1 || style="background-color:#CCCCCC;" | MulanOWL BY-PL-SA v1
|-
| License scope || Copyright, neighboring rights and sui generis database rights (SGDRs) (Sec 1d) || Copyright only, but related rights may not challenge rights granted by license (Sec 1) || Copyright and Patent rights, but related rights may not challenge rights granted by license (Sec 1 and Sec 2)
|-
| Attribution trigger || If there is applicable copyright in work, then when work or adaptation of work is shared. (Sec 3a)
<br>
If there are applicable SGDRs in work, then when all or a substantial portion of database contents is shared. (Sec 4c)
|| When work (modified or not) is distributed (Sec 3) || When work (modified or not) is distributed (Sec 4)
|-
| Attribution removal clause || Yes (Sec 3a3) || No || No
|-
| Attribution elements ||
#creator and attribution parties
#copyright notice
# license notice
# disclaimer notice
# URI or link to the licensed material
# indicate and link to license
(Sec 3a1)
<br>
||
#name of licensor
#copyright statement
#license notice
#modification statements
#patent statements
# trademark statements
# disclaimer statements
# URI or link to the licensed material
# indicate and link to license
# title and version of the work (optional)
(Sec 3)
||
#name of licensor
#copyright statement
#license notice
#modification statements
#patent statements
# trademark statements
# disclaimer statements
# URI or link to the licensed material
# indicate and link to license
# title and version of the work (optional)
(Sec 4)
|-
| Special marking requirement if work is modified || Yes (indicate if you modified and retain indication of previous modifications) (Sec 3a1B)
|| Yes (indicate if you modified and retain indication of previous modifications) (Sec 3(3) and Sec 3(4))|| Yes (indicate if you modified and retain indication of previous modifications) (Sec 4(3) and Sec 4(4))
|-
| ShareAlike trigger || When adaptation is shared (Sec 3b) || When adaptation is shared (Sec 3(3)) || When adaptation is shared (Sec 4(3))
|-
| ShareAlike scope || Must ShareAlike contributions to adaptations (Sec 3b);
<br>
Must ShareAlike database if it incorporates substantial portion of database contents (Sec 4b)
|| Must ShareAlike contributions to adaptations (Sec 3(3)) || Must ShareAlike contributions to adaptations (Sec 4(3))
|-
| Source requirement || None || None || None
|-
| Effective technological measures || May not be applied by licensees if they restrict access to the work or adaptations (Sec 2a5C)
<br>
Licensees have express permission to circumvent if applied by licensor (Sec 2a4)
|| May not be applied by licensees if they restrict access to the work or adaptations (Sec 3(4))
<br>
Licensees have express permission to circumvent if applied by licensor (Sec 3(4))
|| May not be applied by licensees if they restrict access to the work or adaptations (Sec 4(4))
<br>
Licensees have express permission to circumvent if applied by licensor (Sec 4(4))
|-
| Moral rights || Waived only to the extent necessary to allow the license to function. (Sec 2b1) || Not mentioned || Not mentioned
|-
| Termination || Automatic upon breach (Sec 6a) || Terminate upon the receipt of the termination notice from the licensors, unless (1) licensee has cured all the breaches prior to receipt of such notice of termination; or,(2) it’s Licensee's first time to receive a notice of termination from the Licensor, and the licensee has cured all the breaches within 30 days of receipt of such notice; or,(3) licensor has expressly reinstated the license granted to You.(Sec 4.1) || Terminate upon the receipt of the termination notice from the licensors, unless (1) licensee has cured all the breaches prior to receipt of such notice of termination; or,(2) it’s Licensee's first time to receive a notice of termination from the Licensor, and the licensee has cured all the breaches within 30 days of receipt of such notice; or,(3) licensor has expressly reinstated the license granted to You.(Sec 5.1)
|-
| Reinstatement after termination || Requires express permission unless cured within 30 days of discovery of violation (Sec 6b) || None || None
|-
| Reps & warranties || Expressly disclaimed (Sec 5) || Expressly disclaimed (Sec 5) || Expressly disclaimed (Sec 6)
|-
| Choice of law || None || None || None
|-
| Option to comply with other license versions
|| Yes, but limited. Licensees may choose to comply with a later version of BY-SA if such version is applied to an adaptation of the work.
(Secs 2a5B, 3b1)
|| Yes, but limited. Licensees may choose to comply with a later version of MulanOWL BY-SA if such version is applied to an adaptation of the work.(Sec 3(3)) || Yes, but limited. Licensees may choose to comply with a later version of MulanOWL BY-SA if such version is applied to an adaptation of the work.(Sec 4(3))
|}

== Notes ==
<references/>

ShareAlike compatibility analysis: Mulan

2023-11-10T20:01:41Z

CCID-yuanxiaoxu:

“Mulan Open Works License Attribution-ShareAlike, Version 1” (MulanOWL BY-SA v1, http://openworks.mulanos.cn/#/licenses/MulanOWL_BY-SA-v1) and “Mulan Open Works License Attribution-PatentLicensed-ShareAlike, Version 1” (MulanOWL BY-PL-SA v1, http://openworks.mulanos.cn/#/licenses/MulanOWL_BY-PL-SA-v1) were published in 2022. MulanOWL BY-SA v1 and MulanOWL BY-PL-SA v1 are copyright licenses with a ShareAlike mechanism and an attribution mechanism, and [http://freedomdefined.org/Licenses#Free_Art_License they do not violate the definition of Free Cultural Licenses]. Thus, it satisfies the [[ShareAlike_compatibility_process_and_criteria#Minimum_compatibility_criteria.|minimum criteria]] for compatibility set forth in our [[ShareAlike_compatibility_process_and_criteria|ShareAlike compatibility criteria]].

MulanOWL BY-PL-SA v1 grants patent rights and is not compatible with CC BY-SA 4.0.

MulanOWL BY-SA v1 is similar to CC BY-SA 4.0 overall, and the effect of each license as applied to a creative work is largely the same. Inevitably, there are differences between the licenses, which are explained in more detail below.

'''Summary of comparison: MulanOWL BY-SA v1 and MulanOWL BY-PL-SA v1<ref>Note that CC reviewed the English language version of the MulanOWL BY-SA v1 and MulanOWL BY-PL-SA v1 to conduct this analysis.</ref> and BY-SA 4.0'''

*The specific attribution and marking requirements in the two licenses vary slightly. CC BY-SA allows for more flexibility depending on the context in which the work is used.

*MulanOWL BY-SA v1 and MulanOWL BY-PL-SA v1 do not terminate even upon breach, as long as the breach was cured prior to, or within 30 days of, receiving notice of termination. CC BY-SA terminates automatically upon breach, but is reinstated automatically if the breach is cured within 30 days of discovery.

*

{| style="border-collapse: collapse;" border="1" cellpadding="10"
|-
! style="background-color:#CCCCCC;" | Features || style="background-color:#CCCCCC;" | BY-SA 4.0 || style="background-color:#CCCCCC;" | MulanOWL BY-SA v1 || style="background-color:#CCCCCC;" | MulanOWL BY-PL-SA v1
|-
| License scope || Copyright, neighboring rights and sui generis database rights (SGDRs) (Sec 1d) || Copyright only, but related rights may not challenge rights granted by license (Sec 1) || Copyright and Patent rights, but related rights may not challenge rights granted by license (Sec 1 and Sec 2)
|-
| Attribution trigger || If there is applicable copyright in work, then when work or adaptation of work is shared. (Sec 3a)
<br>
If there are applicable SGDRs in work, then when all or a substantial portion of database contents is shared. (Sec 4c)
|| When work (modified or not) is distributed (Sec 3) || When work (modified or not) is distributed (Sec 4)
|-
| Attribution removal clause || Yes (Sec 3a3) || No || No
|-
| Attribution elements ||
#creator and attribution parties
#copyright notice
# license notice
# disclaimer notice
# URI or link to the licensed material
# indicate and link to license
(Sec 3a1)
<br>
||
#name of licensor
#copyright statement
#license notice
#modification statements
#patent statements
# trademark statements
# disclaimer statements
# URI or link to the licensed material
# indicate and link to license
# title and version of the work (optional)
(Sec 3)
||
#name of licensor
#copyright statement
#license notice
#modification statements
#patent statements
# trademark statements
# disclaimer statements
# URI or link to the licensed material
# indicate and link to license
# title and version of the work (optional)
(Sec 4)
|-
| Special marking requirement if work is modified || Yes (indicate if you modified and retain indication of previous modifications) (Sec 3a1B)
|| Yes (indicate if you modified and retain indication of previous modifications) (Sec 3(3) and Sec 3(4))|| Yes (indicate if you modified and retain indication of previous modifications) (Sec 4(3) and Sec 4(4))
|-
| ShareAlike trigger || When adaptation is shared (Sec 3b) || When adaptation is shared (Sec 3(3)) || When adaptation is shared (Sec 4(3))
|-
| ShareAlike scope || Must ShareAlike contributions to adaptations (Sec 3b);
<br>
Must ShareAlike database if it incorporates substantial portion of database contents (Sec 4b)
|| Must ShareAlike contributions to adaptations (Sec 3(3)) || Must ShareAlike contributions to adaptations (Sec 4(3))
|-
| Source requirement || None || None || None
|-
| Effective technological measures || May not be applied by licensees if they restrict access to the work or adaptations (Sec 2a5C)
<br>
Licensees have express permission to circumvent if applied by licensor (Sec 2a4)
|| May not be applied by licensees if they restrict access to the work or adaptations (Sec 3(4))
<br>
Licensees have express permission to circumvent if applied by licensor (Sec 3(4))
|| May not be applied by licensees if they restrict access to the work or adaptations (Sec 4(4))
<br>
Licensees have express permission to circumvent if applied by licensor (Sec 4(4))
|-
| Moral rights || Waived only to the extent necessary to allow the license to function. (Sec 2b1) || Not mentioned || Not mentioned
|-
| Termination || Automatic upon breach (Sec 6a) || Terminate upon the receipt of the termination notice from the licensors, unless (1) licensee has cured all the breaches prior to receipt of such notice of termination; or,(2) it’s Licensee's first time to receive a notice of termination from the Licensor, and the licensee has cured all the breaches within 30 days of receipt of such notice; or,(3) licensor has expressly reinstated the license granted to You.(Sec 4.1) || Terminate upon the receipt of the termination notice from the licensors, unless (1) licensee has cured all the breaches prior to receipt of such notice of termination; or,(2) it’s Licensee's first time to receive a notice of termination from the Licensor, and the licensee has cured all the breaches within 30 days of receipt of such notice; or,(3) licensor has expressly reinstated the license granted to You.(Sec 5.1)
|-
| Reinstatement after termination || Requires express permission unless cured within 30 days of discovery of violation (Sec 6b) || None || None
|-
| Reps & warranties || Expressly disclaimed (Sec 5) || Expressly disclaimed (Sec 5) || Expressly disclaimed (Sec 6)
|-
| Choice of law || None || None || None
|-
| Option to comply with other license versions
|| Yes, but limited. Licensees may choose to comply with a later version of BY-SA if such version is applied to an adaptation of the work.
(Secs 2a5B, 3b1)
|| Yes, but limited. Licensees may choose to comply with a later version of MulanOWL BY-SA if such version is applied to an adaptation of the work.(Sec 3(3)) || Yes, but limited. Licensees may choose to comply with a later version of MulanOWL BY-SA if such version is applied to an adaptation of the work.(Sec 4(3))
|}

== Notes ==
<references/>

ShareAlike compatibility analysis: Mulan

2023-09-15T00:19:31Z

CCID-yuanxiaoxu:

“Mulan Open Works License Attribution-ShareAlike, Version 1” (MulanOWL BY-SA v1, http://openworks.mulanos.cn/#/licenses/MulanOWL_BY-SA-v1) and “Mulan Open Works License Attribution-PatentLicensed-ShareAlike, Version 1” (MulanOWL BY-PL-SA v1, http://openworks.mulanos.cn/#/licenses/MulanOWL_BY-PL-SA-v1) were published in 2022. MulanOWL BY-SA v1 and MulanOWL BY-PL-SA v1 are copyright licenses with a ShareAlike mechanism and an attribution mechanism, and [http://freedomdefined.org/Licenses#Free_Art_License they do not violate the definition of Free Cultural Licenses]. Thus, it satisfies the [[ShareAlike_compatibility_process_and_criteria#Minimum_compatibility_criteria.|minimum criteria]] for compatibility set forth in our [[ShareAlike_compatibility_process_and_criteria|ShareAlike compatibility criteria]]. Overall, the MulanOWL BY-SA v1 and MulanOWL BY-PL-SA v1 are similar to CC BY-SA 4.0, and the effect of each license as applied to a creative work is largely the same. Inevitably, there are differences between the licenses, which are explained in more detail below.

'''Summary of comparison: MulanOWL BY-SA v1 and MulanOWL BY-PL-SA v1<ref>Note that CC reviewed the English language version of the MulanOWL BY-SA v1 and MulanOWL BY-PL-SA v1 to conduct this analysis.</ref> and BY-SA 4.0'''

*The specific attribution and marking requirements in the two licenses vary slightly. CC BY-SA allows for more flexibility depending on the context in which the work is used.

*MulanOWL BY-SA v1 and MulanOWL BY-PL-SA v1 do not terminate even upon breach, as long as the breach was cured prior to, or within 30 days of, receiving notice of termination. CC BY-SA terminates automatically upon breach, but is reinstated automatically if the breach is cured within 30 days of discovery.

*

{| style="border-collapse: collapse;" border="1" cellpadding="10"
|-
! style="background-color:#CCCCCC;" | Features || style="background-color:#CCCCCC;" | BY-SA 4.0 || style="background-color:#CCCCCC;" | MulanOWL BY-SA v1 || style="background-color:#CCCCCC;" | MulanOWL BY-PL-SA v1
|-
| License scope || Copyright, neighboring rights and sui generis database rights (SGDRs) (Sec 1d) || Copyright only, but related rights may not challenge rights granted by license (Sec 1) || Copyright and Patent rights, but related rights may not challenge rights granted by license (Sec 1 and Sec 2)
|-
| Attribution trigger || If there is applicable copyright in work, then when work or adaptation of work is shared. (Sec 3a)
<br>
If there are applicable SGDRs in work, then when all or a substantial portion of database contents is shared. (Sec 4c)
|| When work (modified or not) is distributed (Sec 3) || When work (modified or not) is distributed (Sec 4)
|-
| Attribution removal clause || Yes (Sec 3a3) || No || No
|-
| Attribution elements ||
#creator and attribution parties
#copyright notice
# license notice
# disclaimer notice
# URI or link to the licensed material
# indicate and link to license
(Sec 3a1)
<br>
||
#name of licensor
#copyright statement
#license notice
#modification statements
#patent statements
# trademark statements
# disclaimer statements
# URI or link to the licensed material
# indicate and link to license
# title and version of the work (optional)
(Sec 3)
||
#name of licensor
#copyright statement
#license notice
#modification statements
#patent statements
# trademark statements
# disclaimer statements
# URI or link to the licensed material
# indicate and link to license
# title and version of the work (optional)
(Sec 4)
|-
| Special marking requirement if work is modified || Yes (indicate if you modified and retain indication of previous modifications) (Sec 3a1B)
|| Yes (indicate if you modified and retain indication of previous modifications) (Sec 3(3) and Sec 3(4))|| Yes (indicate if you modified and retain indication of previous modifications) (Sec 4(3) and Sec 4(4))
|-
| ShareAlike trigger || When adaptation is shared (Sec 3b) || When adaptation is shared (Sec 3(3)) || When adaptation is shared (Sec 4(3))
|-
| ShareAlike scope || Must ShareAlike contributions to adaptations (Sec 3b);
<br>
Must ShareAlike database if it incorporates substantial portion of database contents (Sec 4b)
|| Must ShareAlike contributions to adaptations (Sec 3(3)) || Must ShareAlike contributions to adaptations (Sec 4(3))
|-
| Source requirement || None || None || None
|-
| Effective technological measures || May not be applied by licensees if they restrict access to the work or adaptations (Sec 2a5C)
<br>
Licensees have express permission to circumvent if applied by licensor (Sec 2a4)
|| May not be applied by licensees if they restrict access to the work or adaptations (Sec 3(4))
<br>
Licensees have express permission to circumvent if applied by licensor (Sec 3(4))
|| May not be applied by licensees if they restrict access to the work or adaptations (Sec 4(4))
<br>
Licensees have express permission to circumvent if applied by licensor (Sec 4(4))
|-
| Moral rights || Waived only to the extent necessary to allow the license to function. (Sec 2b1) || Not mentioned || Not mentioned
|-
| Termination || Automatic upon breach (Sec 6a) || Terminate upon the receipt of the termination notice from the licensors, unless (1) licensee has cured all the breaches prior to receipt of such notice of termination; or,(2) it’s Licensee's first time to receive a notice of termination from the Licensor, and the licensee has cured all the breaches within 30 days of receipt of such notice; or,(3) licensor has expressly reinstated the license granted to You.(Sec 4.1) || Terminate upon the receipt of the termination notice from the licensors, unless (1) licensee has cured all the breaches prior to receipt of such notice of termination; or,(2) it’s Licensee's first time to receive a notice of termination from the Licensor, and the licensee has cured all the breaches within 30 days of receipt of such notice; or,(3) licensor has expressly reinstated the license granted to You.(Sec 5.1)
|-
| Reinstatement after termination || Requires express permission unless cured within 30 days of discovery of violation (Sec 6b) || None || None
|-
| Reps & warranties || Expressly disclaimed (Sec 5) || Expressly disclaimed (Sec 5) || Expressly disclaimed (Sec 6)
|-
| Choice of law || None || None || None
|-
| Option to comply with other license versions
|| Yes, but limited. Licensees may choose to comply with a later version of BY-SA if such version is applied to an adaptation of the work.
(Secs 2a5B, 3b1)
|| Yes, but limited. Licensees may choose to comply with a later version of MulanOWL BY-SA if such version is applied to an adaptation of the work.(Sec 3(3)) || Yes, but limited. Licensees may choose to comply with a later version of MulanOWL BY-SA if such version is applied to an adaptation of the work.(Sec 4(3))
|}

== Notes ==
<references/>

ShareAlike compatibility analysis: Mulan

2023-09-15T00:17:51Z

CCID-yuanxiaoxu:

“Mulan Open Works License Attribution-ShareAlike, Version 1” (MulanOWL BY-SA v1, http://openworks.mulanos.cn/#/licenses/MulanOWL_BY-SA-v1) and “Mulan Open Works License Attribution-PatentLicensed-ShareAlike, Version 1” (MulanOWL BY-PL-SA v1, http://openworks.mulanos.cn/#/licenses/MulanOWL_BY-PL-SA-v1) were published in 2022. MulanOWL BY-SA v1 and MulanOWL BY-PL-SA v1 are copyright licenses with a ShareAlike mechanism and an attribution mechanism, and [http://freedomdefined.org/Licenses#Free_Art_License they do not violate the definition of Free Cultural Licenses]. Thus, it satisfies the [[ShareAlike_compatibility_process_and_criteria#Minimum_compatibility_criteria.|minimum criteria]] for compatibility set forth in our [[ShareAlike_compatibility_process_and_criteria|ShareAlike compatibility criteria]]. Overall, the MulanOWL BY-SA v1 and MulanOWL BY-PL-SA v1 are similar to CC BY-SA 4.0, and the effect of each license as applied to a creative work is largely the same. Inevitably, there are differences between the licenses, which are explained in more detail below.

'''Summary of comparison: MulanOWL BY-SA v1 and MulanOWL BY-PL-SA v1<ref>Note that CC reviewed the English language version of the MulanOWL BY-SA v1 and MulanOWL BY-PL-SA v1 to conduct this analysis.</ref> and BY-SA 4.0'''

*The specific attribution and marking requirements in the two licenses vary slightly. CC BY-SA allows for more flexibility depending on the context in which the work is used.

*MulanOWL BY-SA v1 and MulanOWL BY-PL-SA v1 do not terminate even upon breach, as long as the breach was cured prior to, or within 30 days of, receiving notice of termination. CC BY-SA terminates automatically upon breach, but is reinstated automatically if the breach is cured within 30 days of discovery.

*

{| style="border-collapse: collapse;" border="1" cellpadding="10"
|-
! style="background-color:#CCCCCC;" | Features || style="background-color:#CCCCCC;" | BY-SA 4.0 || style="background-color:#CCCCCC;" | MulanOWL BY-SA v1 || style="background-color:#CCCCCC;" | MulanOWL BY-PL-SA v1
|-
| License scope || Copyright, neighboring rights and sui generis database rights (SGDRs) (Sec 1d) || Copyright only, but related rights may not challenge rights granted by license (Sec 1) || Copyright and Patent rights, but related rights may not challenge rights granted by license (Sec 1 and Sec 2)
|-
| Attribution trigger || If there is applicable copyright in work, then when work or adaptation of work is shared. (Sec 3a)
<br>
If there are applicable SGDRs in work, then when all or a substantial portion of database contents is shared. (Sec 4c)
|| When work (modified or not) is distributed (Sec 3) || When work (modified or not) is distributed (Sec 4)
|-
| Attribution removal clause || Yes (Sec 3a3) || No || No
|-
| Attribution elements ||
#creator and attribution parties
#copyright notice
# license notice
# disclaimer notice
# URI or link to the licensed material
# indicate and link to license
(Sec 3a1)
<br>
||
#name of licensor
#copyright statement
#license notice
#modification statements
#patent statements
# trademark statements
# disclaimer statements
# URI or link to the licensed material
# indicate and link to license
# title and version of the work (optional)
(Sec 3)
||
#name of licensor
#copyright statement
#license notice
#modification statements
#patent statements
# trademark statements
# disclaimer statements
# URI or link to the licensed material
# indicate and link to license
# title and version of the work (optional)
(Sec 4)
|-
| Special marking requirement if work is modified || Yes (indicate if you modified and retain indication of previous modifications) (Sec 3a1B)
|| Yes (indicate if you modified and retain indication of previous modifications) (Sec 3(3) and Sec 3(4))|| Yes (indicate if you modified and retain indication of previous modifications) (Sec 4(3) and Sec 4(4))
|-
| ShareAlike trigger || When adaptation is shared (Sec 3b) || When adaptation is shared (Sec 3(3)) || When adaptation is shared (Sec 4(3))
|-
| ShareAlike scope || Must ShareAlike contributions to adaptations (Sec 3b);
<br>
Must ShareAlike database if it incorporates substantial portion of database contents (Sec 4b)
|| Must ShareAlike contributions to adaptations (Sec 3(3)) || Must ShareAlike contributions to adaptations (Sec 4(3))
|-
| Source requirement || None || None || None
|-
| Effective technological measures || May not be applied by licensees if they restrict access to the work or adaptations (Sec 2a5C)
<br>
Licensees have express permission to circumvent if applied by licensor (Sec 2a4)
|| May not be applied by licensees if they restrict access to the work or adaptations (Sec 3(4))
<br>
Licensees have express permission to circumvent if applied by licensor (Sec 3(4))
|| May not be applied by licensees if they restrict access to the work or adaptations (Sec 4(4))
<br>
Licensees have express permission to circumvent if applied by licensor (Sec 4(4))
|-
| Moral rights || Waived only to the extent necessary to allow the license to function. (Sec 2b1) || Not mentioned || Not mentioned
|-
| Termination || Automatic upon breach (Sec 6a) || Terminate upon the receipt of the termination notice from the licensors, unless (1) licensee has cured all the breaches prior to receipt of such notice of termination; or,(2) it’s Licensee's first time to receive a notice of termination from the Licensor, and the licensee has cured all the breaches within 30 days of receipt of such notice; or,(3) licensor has expressly reinstated the license granted to You.(Sec 4.1) || Terminate upon the receipt of the termination notice from the licensors, unless (1) licensee has cured all the breaches prior to receipt of such notice of termination; or,(2) it’s Licensee's first time to receive a notice of termination from the Licensor, and the licensee has cured all the breaches within 30 days of receipt of such notice; or,(3) licensor has expressly reinstated the license granted to You.(Sec 5.1)
|-
| Reinstatement after termination || Requires express permission unless cured within 30 days of discovery of violation (Sec 6b) || None || None
|-
| Reps & warranties || Expressly disclaimed (Sec 5) || Expressly disclaimed (Sec 5) || Expressly disclaimed (Sec 6)
|-
| Choice of law || None || None
|-
| Option to comply with other license versions
|| Yes, but limited. Licensees may choose to comply with a later version of BY-SA if such version is applied to an adaptation of the work.
(Secs 2a5B, 3b1)
|| Yes, licensees may choose to comply with the version of the FAL that was applied to the copy distributed to them or a later version. (Sec 9)
|}

== Notes ==
<references/>

ShareAlike compatibility analysis: Mulan

2023-09-15T00:14:13Z

CCID-yuanxiaoxu:

“Mulan Open Works License Attribution-ShareAlike, Version 1” (MulanOWL BY-SA v1, http://openworks.mulanos.cn/#/licenses/MulanOWL_BY-SA-v1) and “Mulan Open Works License Attribution-PatentLicensed-ShareAlike, Version 1” (MulanOWL BY-PL-SA v1, http://openworks.mulanos.cn/#/licenses/MulanOWL_BY-PL-SA-v1) were published in 2022. MulanOWL BY-SA v1 and MulanOWL BY-PL-SA v1 are copyright licenses with a ShareAlike mechanism and an attribution mechanism, and [http://freedomdefined.org/Licenses#Free_Art_License they do not violate the definition of Free Cultural Licenses]. Thus, it satisfies the [[ShareAlike_compatibility_process_and_criteria#Minimum_compatibility_criteria.|minimum criteria]] for compatibility set forth in our [[ShareAlike_compatibility_process_and_criteria|ShareAlike compatibility criteria]]. Overall, the MulanOWL BY-SA v1 and MulanOWL BY-PL-SA v1 are similar to CC BY-SA 4.0, and the effect of each license as applied to a creative work is largely the same. Inevitably, there are differences between the licenses, which are explained in more detail below.

'''Summary of comparison: MulanOWL BY-SA v1 and MulanOWL BY-PL-SA v1<ref>Note that CC reviewed the English language version of the MulanOWL BY-SA v1 and MulanOWL BY-PL-SA v1 to conduct this analysis.</ref> and BY-SA 4.0'''

*The specific attribution and marking requirements in the two licenses vary slightly. CC BY-SA allows for more flexibility depending on the context in which the work is used.

*MulanOWL BY-SA v1 and MulanOWL BY-PL-SA v1 do not terminate even upon breach, as long as the breach was cured prior to, or within 30 days of, receiving notice of termination. CC BY-SA terminates automatically upon breach, but is reinstated automatically if the breach is cured within 30 days of discovery.

*

{| style="border-collapse: collapse;" border="1" cellpadding="10"
|-
! style="background-color:#CCCCCC;" | Features || style="background-color:#CCCCCC;" | BY-SA 4.0 || style="background-color:#CCCCCC;" | MulanOWL BY-SA v1 || style="background-color:#CCCCCC;" | MulanOWL BY-PL-SA v1
|-
| License scope || Copyright, neighboring rights and sui generis database rights (SGDRs) (Sec 1d) || Copyright only, but related rights may not challenge rights granted by license (Sec 1) || Copyright and Patent rights, but related rights may not challenge rights granted by license (Sec 1 and Sec 2)
|-
| Attribution trigger || If there is applicable copyright in work, then when work or adaptation of work is shared. (Sec 3a)
<br>
If there are applicable SGDRs in work, then when all or a substantial portion of database contents is shared. (Sec 4c)
|| When work (modified or not) is distributed (Sec 3) || When work (modified or not) is distributed (Sec 4)
|-
| Attribution removal clause || Yes (Sec 3a3) || No || No
|-
| Attribution elements ||
#creator and attribution parties
#copyright notice
# license notice
# disclaimer notice
# URI or link to the licensed material
# indicate and link to license
(Sec 3a1)
<br>
||
#name of licensor
#copyright statement
#license notice
#modification statements
#patent statements
# trademark statements
# disclaimer statements
# URI or link to the licensed material
# indicate and link to license
# title and version of the work (optional)
(Sec 3)
||
#name of licensor
#copyright statement
#license notice
#modification statements
#patent statements
# trademark statements
# disclaimer statements
# URI or link to the licensed material
# indicate and link to license
# title and version of the work (optional)
(Sec 4)
|-
| Special marking requirement if work is modified || Yes (indicate if you modified and retain indication of previous modifications) (Sec 3a1B)
|| Yes (indicate if you modified and retain indication of previous modifications) (Sec 3(3) and Sec 3(4))|| Yes (indicate if you modified and retain indication of previous modifications) (Sec 4(3) and Sec 4(4))
|-
| ShareAlike trigger || When adaptation is shared (Sec 3b) || When adaptation is shared (Sec 3(3)) || When adaptation is shared (Sec 4(3))
|-
| ShareAlike scope || Must ShareAlike contributions to adaptations (Sec 3b);
<br>
Must ShareAlike database if it incorporates substantial portion of database contents (Sec 4b)
|| Must ShareAlike contributions to adaptations (Sec 3(3)) || Must ShareAlike contributions to adaptations (Sec 4(3))
|-
| Source requirement || None || None || None
|-
| Effective technological measures || May not be applied by licensees if they restrict access to the work or adaptations (Sec 2a5C)
<br>
Licensees have express permission to circumvent if applied by licensor (Sec 2a4)
|| May not be applied by licensees if they restrict access to the work or adaptations (Sec 3(4))
<br>
Licensees have express permission to circumvent if applied by licensor (Sec 3(4))
|| May not be applied by licensees if they restrict access to the work or adaptations (Sec 4(4))
<br>
Licensees have express permission to circumvent if applied by licensor (Sec 4(4))
|-
| Moral rights || Waived only to the extent necessary to allow the license to function. (Sec 2b1) || Author’s rights may not challenge the rights granted by license. (Sec 3)
|-
| Termination || Automatic upon breach (Sec 6a) || Automatic upon breach (Sec 8)
|-
| Reinstatement after termination || Requires express permission unless cured within 30 days of discovery of violation (Sec 6b) || None
|-
| Reps & warranties || Expressly disclaimed (Sec 5) || Not mentioned
|-
| Choice of law || None || None
|-
| Option to comply with other license versions
|| Yes, but limited. Licensees may choose to comply with a later version of BY-SA if such version is applied to an adaptation of the work.
(Secs 2a5B, 3b1)
|| Yes, licensees may choose to comply with the version of the FAL that was applied to the copy distributed to them or a later version. (Sec 9)
|}

== Notes ==
<references/>

ShareAlike compatibility analysis: Mulan

2023-09-15T00:13:00Z

CCID-yuanxiaoxu:

“Mulan Open Works License Attribution-ShareAlike, Version 1” (MulanOWL BY-SA v1, http://openworks.mulanos.cn/#/licenses/MulanOWL_BY-SA-v1) and “Mulan Open Works License Attribution-PatentLicensed-ShareAlike, Version 1” (MulanOWL BY-PL-SA v1, http://openworks.mulanos.cn/#/licenses/MulanOWL_BY-PL-SA-v1) were published in 2022. MulanOWL BY-SA v1 and MulanOWL BY-PL-SA v1 are copyright licenses with a ShareAlike mechanism and an attribution mechanism, and [http://freedomdefined.org/Licenses#Free_Art_License they do not violate the definition of Free Cultural Licenses]. Thus, it satisfies the [[ShareAlike_compatibility_process_and_criteria#Minimum_compatibility_criteria.|minimum criteria]] for compatibility set forth in our [[ShareAlike_compatibility_process_and_criteria|ShareAlike compatibility criteria]]. Overall, the MulanOWL BY-SA v1 and MulanOWL BY-PL-SA v1 are similar to CC BY-SA 4.0, and the effect of each license as applied to a creative work is largely the same. Inevitably, there are differences between the licenses, which are explained in more detail below.

'''Summary of comparison: MulanOWL BY-SA v1 and MulanOWL BY-PL-SA v1<ref>Note that CC reviewed the English language version of the MulanOWL BY-SA v1 and MulanOWL BY-PL-SA v1 to conduct this analysis.</ref> and BY-SA 4.0'''

*The specific attribution and marking requirements in the two licenses vary slightly. CC BY-SA allows for more flexibility depending on the context in which the work is used.

*MulanOWL BY-SA v1 and MulanOWL BY-PL-SA v1 do not terminate even upon breach, as long as the breach was cured prior to, or within 30 days of, receiving notice of termination. CC BY-SA terminates automatically upon breach, but is reinstated automatically if the breach is cured within 30 days of discovery.

*

{| style="border-collapse: collapse;" border="1" cellpadding="10"
|-
! style="background-color:#CCCCCC;" | Features || style="background-color:#CCCCCC;" | BY-SA 4.0 || style="background-color:#CCCCCC;" | MulanOWL BY-SA v1 || style="background-color:#CCCCCC;" | MulanOWL BY-PL-SA v1
|-
| License scope || Copyright, neighboring rights and sui generis database rights (SGDRs) (Sec 1d) || Copyright only, but related rights may not challenge rights granted by license (Sec 1) || Copyright and Patent rights, but related rights may not challenge rights granted by license (Sec 1 and Sec 2)
|-
| Attribution trigger || If there is applicable copyright in work, then when work or adaptation of work is shared. (Sec 3a)
<br>
If there are applicable SGDRs in work, then when all or a substantial portion of database contents is shared. (Sec 4c)
|| When work (modified or not) is distributed (Sec 3) || When work (modified or not) is distributed (Sec 4)
|-
| Attribution removal clause || Yes (Sec 3a3) || No || No
|-
| Attribution elements ||
#creator and attribution parties
#copyright notice
# license notice
# disclaimer notice
# URI or link to the licensed material
# indicate and link to license
(Sec 3a1)
<br>
||
#name of licensor
#copyright statement
#license notice
#modification statements
#patent statements
# trademark statements
# disclaimer statements
# URI or link to the licensed material
# indicate and link to license
# title and version of the work (optional)
(Sec 3)
||
#name of licensor
#copyright statement
#license notice
#modification statements
#patent statements
# trademark statements
# disclaimer statements
# URI or link to the licensed material
# indicate and link to license
# title and version of the work (optional)
(Sec 4)
|-
| Special marking requirement if work is modified || Yes (indicate if you modified and retain indication of previous modifications) (Sec 3a1B)
|| Yes (indicate if you modified and retain indication of previous modifications) (Sec 3(3) and Sec 3(4))|| Yes (indicate if you modified and retain indication of previous modifications) (Sec 4(3) and Sec 4(4))
|-
| ShareAlike trigger || When adaptation is shared (Sec 3b) || When adaptation is shared (Sec 3(3)) || When adaptation is shared (Sec 4(3))
|-
| ShareAlike scope || Must ShareAlike contributions to adaptations (Sec 3b);
<br>
Must ShareAlike database if it incorporates substantial portion of database contents (Sec 4b)
|| Must ShareAlike contributions to adaptations (Sec 3(3)) || Must ShareAlike contributions to adaptations (Sec 4(3))
|-
| Source requirement || None || None || None
|-
| Effective technological measures || May not be applied by licensees if they restrict access to the work or adaptations (Sec 2a5C)
<br>
Licensees have express permission to circumvent if applied by licensor (Sec 2a4)
|| Not expressly mentioned, but may not be applied by licensees if they restrict users freedoms to copy (2.1), to distribute (2.2.) or to modify (2.3) the work
|-
| Moral rights || Waived only to the extent necessary to allow the license to function. (Sec 2b1) || Author’s rights may not challenge the rights granted by license. (Sec 3)
|-
| Termination || Automatic upon breach (Sec 6a) || Automatic upon breach (Sec 8)
|-
| Reinstatement after termination || Requires express permission unless cured within 30 days of discovery of violation (Sec 6b) || None
|-
| Reps & warranties || Expressly disclaimed (Sec 5) || Not mentioned
|-
| Choice of law || None || None
|-
| Option to comply with other license versions
|| Yes, but limited. Licensees may choose to comply with a later version of BY-SA if such version is applied to an adaptation of the work.
(Secs 2a5B, 3b1)
|| Yes, licensees may choose to comply with the version of the FAL that was applied to the copy distributed to them or a later version. (Sec 9)
|}

== Notes ==
<references/>

ShareAlike compatibility analysis: Mulan

2023-09-15T00:05:16Z

CCID-yuanxiaoxu:

“Mulan Open Works License Attribution-ShareAlike, Version 1” (MulanOWL BY-SA v1, http://openworks.mulanos.cn/#/licenses/MulanOWL_BY-SA-v1) and “Mulan Open Works License Attribution-PatentLicensed-ShareAlike, Version 1” (MulanOWL BY-PL-SA v1, http://openworks.mulanos.cn/#/licenses/MulanOWL_BY-PL-SA-v1) were published in 2022. MulanOWL BY-SA v1 and MulanOWL BY-PL-SA v1 are copyright licenses with a ShareAlike mechanism and an attribution mechanism, and [http://freedomdefined.org/Licenses#Free_Art_License they do not violate the definition of Free Cultural Licenses]. Thus, it satisfies the [[ShareAlike_compatibility_process_and_criteria#Minimum_compatibility_criteria.|minimum criteria]] for compatibility set forth in our [[ShareAlike_compatibility_process_and_criteria|ShareAlike compatibility criteria]]. Overall, the MulanOWL BY-SA v1 and MulanOWL BY-PL-SA v1 are similar to CC BY-SA 4.0, and the effect of each license as applied to a creative work is largely the same. Inevitably, there are differences between the licenses, which are explained in more detail below.

'''Summary of comparison: MulanOWL BY-SA v1 and MulanOWL BY-PL-SA v1<ref>Note that CC reviewed the English language version of the MulanOWL BY-SA v1 and MulanOWL BY-PL-SA v1 to conduct this analysis.</ref> and BY-SA 4.0'''

*The specific attribution and marking requirements in the two licenses vary slightly. CC BY-SA allows for more flexibility depending on the context in which the work is used.

*MulanOWL BY-SA v1 and MulanOWL BY-PL-SA v1 do not terminate even upon breach, as long as the breach was cured prior to, or within 30 days of, receiving notice of termination. CC BY-SA terminates automatically upon breach, but is reinstated automatically if the breach is cured within 30 days of discovery.

*

{| style="border-collapse: collapse;" border="1" cellpadding="10"
|-
! style="background-color:#CCCCCC;" | Features || style="background-color:#CCCCCC;" | BY-SA 4.0 || style="background-color:#CCCCCC;" | MulanOWL BY-SA v1 || style="background-color:#CCCCCC;" | MulanOWL BY-PL-SA v1
|-
| License scope || Copyright, neighboring rights and sui generis database rights (SGDRs) (Sec 1d) || Copyright only, but related rights may not challenge rights granted by license (Sec 1) || Copyright and Patent rights, but related rights may not challenge rights granted by license (Sec 1 and Sec 2)
|-
| Attribution trigger || If there is applicable copyright in work, then when work or adaptation of work is shared. (Sec 3a)
<br>
If there are applicable SGDRs in work, then when all or a substantial portion of database contents is shared. (Sec 4c)
|| When work (modified or not) is distributed (Sec 3) || When work (modified or not) is distributed (Sec 4)
|-
| Attribution removal clause || Yes (Sec 3a3) || No || No
|-
| Attribution elements ||
#creator and attribution parties
#copyright notice
# license notice
# disclaimer notice
# URI or link to the licensed material
# indicate and link to license
(Sec 3a1)
<br>
||
#name of licensor
#copyright statement
#license notice
#modification statements
#patent statements
# trademark statements
# disclaimer statements
# URI or link to the licensed material
# indicate and link to license
# title and version of the work (optional)
(Sec 3)
||
#name of licensor
#copyright statement
#license notice
#modification statements
#patent statements
# trademark statements
# disclaimer statements
# URI or link to the licensed material
# indicate and link to license
# title and version of the work (optional)
(Sec 4)
|-
| Special marking requirement if work is modified || Yes (indicate if you modified and retain indication of previous modifications) (Sec 3a1B)
|| Yes (indicate if you modified and what type of modifications were made) (Sec 2.3)
|-
| ShareAlike trigger || When adaptation is shared (Sec 3b) || When you distribute an adaptation (Sec 2.3)
|-
| ShareAlike scope || Must ShareAlike contributions to adaptations (Sec 3b);
<br>
Must ShareAlike database if it incorporates substantial portion of database contents (Sec 4b)
|| Must ShareAlike contributions to adaptations (Sec 2.3)
<br>
Must ShareAlike larger work if incorporate original in a way that makes it no longer accessible apart from larger work (Sec 4)
|-
| Source requirement || None || None
|-
| Effective technological measures || May not be applied by licensees if they restrict access to the work or adaptations (Sec 2a5C)
<br>
Licensees have express permission to circumvent if applied by licensor (Sec 2a4)
|| Not expressly mentioned, but may not be applied by licensees if they restrict users freedoms to copy (2.1), to distribute (2.2.) or to modify (2.3) the work
|-
| Moral rights || Waived only to the extent necessary to allow the license to function. (Sec 2b1) || Author’s rights may not challenge the rights granted by license. (Sec 3)
|-
| Termination || Automatic upon breach (Sec 6a) || Automatic upon breach (Sec 8)
|-
| Reinstatement after termination || Requires express permission unless cured within 30 days of discovery of violation (Sec 6b) || None
|-
| Reps & warranties || Expressly disclaimed (Sec 5) || Not mentioned
|-
| Choice of law || None || None
|-
| Option to comply with other license versions
|| Yes, but limited. Licensees may choose to comply with a later version of BY-SA if such version is applied to an adaptation of the work.
(Secs 2a5B, 3b1)
|| Yes, licensees may choose to comply with the version of the FAL that was applied to the copy distributed to them or a later version. (Sec 9)
|}

== Notes ==
<references/>

ShareAlike compatibility analysis: Mulan

2023-09-14T23:55:22Z

CCID-yuanxiaoxu:

“Mulan Open Works License Attribution-ShareAlike, Version 1” (MulanOWL BY-SA v1, http://openworks.mulanos.cn/#/licenses/MulanOWL_BY-SA-v1) and “Mulan Open Works License Attribution-PatentLicensed-ShareAlike, Version 1” (MulanOWL BY-PL-SA v1, http://openworks.mulanos.cn/#/licenses/MulanOWL_BY-PL-SA-v1) were published in 2022. MulanOWL BY-SA v1 and MulanOWL BY-PL-SA v1 are copyright licenses with a ShareAlike mechanism and an attribution mechanism, and [http://freedomdefined.org/Licenses#Free_Art_License they do not violate the definition of Free Cultural Licenses]. Thus, it satisfies the [[ShareAlike_compatibility_process_and_criteria#Minimum_compatibility_criteria.|minimum criteria]] for compatibility set forth in our [[ShareAlike_compatibility_process_and_criteria|ShareAlike compatibility criteria]]. Overall, the MulanOWL BY-SA v1 and MulanOWL BY-PL-SA v1 are similar to CC BY-SA 4.0, and the effect of each license as applied to a creative work is largely the same. Inevitably, there are differences between the licenses, which are explained in more detail below.

'''Summary of comparison: MulanOWL BY-SA v1 and MulanOWL BY-PL-SA v1<ref>Note that CC reviewed the English language version of the MulanOWL BY-SA v1 and MulanOWL BY-PL-SA v1 to conduct this analysis.</ref> and BY-SA 4.0'''

*The specific attribution and marking requirements in the two licenses vary slightly. CC BY-SA has more total necessary elements for proper attribution, but allows for more flexibility depending on the context in which the work is used.

*MulanOWL BY-SA v1 and MulanOWL BY-PL-SA v1 do not terminate even upon breach, as long as the breach was cured prior to, or within 30 days of, receiving notice of termination. CC BY-SA terminates automatically upon breach, but is reinstated automatically if the breach is cured within 30 days of discovery.

*

{| style="border-collapse: collapse;" border="1" cellpadding="10"
|-
! style="background-color:#CCCCCC;" | Features || style="background-color:#CCCCCC;" | BY-SA 4.0 || style="background-color:#CCCCCC;" | MulanOWL BY-SA v1 || style="background-color:#CCCCCC;" | MulanOWL BY-PL-SA v1
|-
| License scope || Copyright, neighboring rights and sui generis database rights (SGDRs) (Sec 1d) || Copyright only, but related rights may not challenge rights granted by license (Sec 1) || Copyright and Patent rights, but related rights may not challenge rights granted by license (Sec 1 and Sec 2)
|-
| Attribution trigger || If there is applicable copyright in work, then when work or adaptation of work is shared. (Sec 3a)
<br>
If there are applicable SGDRs in work, then when all or a substantial portion of database contents is shared. (Sec 4c)
|| When work (modified or not) is distributed (Sec 2.2)
|-
| Attribution removal clause || Yes (Sec 3a3) || No
|-
| Attribution elements ||
#creator and attribution parties
#copyright notice
# license notice
# disclaimer notice
# URI or link to the licensed material
# indicate and link to license
(Sec 3a1)
<br>
||
#name of author(s),
#attach license to work or indicate where license can be found
# info on where to access the originals
(Sec 2.2)
|-
| Special marking requirement if work is modified || Yes (indicate if you modified and retain indication of previous modifications) (Sec 3a1B)
|| Yes (indicate if you modified and what type of modifications were made) (Sec 2.3)
|-
| ShareAlike trigger || When adaptation is shared (Sec 3b) || When you distribute an adaptation (Sec 2.3)
|-
| ShareAlike scope || Must ShareAlike contributions to adaptations (Sec 3b);
<br>
Must ShareAlike database if it incorporates substantial portion of database contents (Sec 4b)
|| Must ShareAlike contributions to adaptations (Sec 2.3)
<br>
Must ShareAlike larger work if incorporate original in a way that makes it no longer accessible apart from larger work (Sec 4)
|-
| Source requirement || None || None
|-
| Effective technological measures || May not be applied by licensees if they restrict access to the work or adaptations (Sec 2a5C)
<br>
Licensees have express permission to circumvent if applied by licensor (Sec 2a4)
|| Not expressly mentioned, but may not be applied by licensees if they restrict users freedoms to copy (2.1), to distribute (2.2.) or to modify (2.3) the work
|-
| Moral rights || Waived only to the extent necessary to allow the license to function. (Sec 2b1) || Author’s rights may not challenge the rights granted by license. (Sec 3)
|-
| Termination || Automatic upon breach (Sec 6a) || Automatic upon breach (Sec 8)
|-
| Reinstatement after termination || Requires express permission unless cured within 30 days of discovery of violation (Sec 6b) || None
|-
| Reps & warranties || Expressly disclaimed (Sec 5) || Not mentioned
|-
| Choice of law || None || None
|-
| Option to comply with other license versions
|| Yes, but limited. Licensees may choose to comply with a later version of BY-SA if such version is applied to an adaptation of the work.
(Secs 2a5B, 3b1)
|| Yes, licensees may choose to comply with the version of the FAL that was applied to the copy distributed to them or a later version. (Sec 9)
|}

== Notes ==
<references/>

ShareAlike compatibility analysis: Mulan

2023-09-14T23:44:49Z

CCID-yuanxiaoxu: Created page with "“Mulan Open Works License Attribution-ShareAlike, Version 1” (MulanOWL BY-SA v1, http://openworks.mulanos.cn/#/licenses/MulanOWL_BY-SA-v1) and “Mulan Open Works License..."

“Mulan Open Works License Attribution-ShareAlike, Version 1” (MulanOWL BY-SA v1, http://openworks.mulanos.cn/#/licenses/MulanOWL_BY-SA-v1) and “Mulan Open Works License Attribution-PatentLicensed-ShareAlike, Version 1” (MulanOWL BY-PL-SA v1, http://openworks.mulanos.cn/#/licenses/MulanOWL_BY-PL-SA-v1) were published in 2022. MulanOWL BY-SA v1 and MulanOWL BY-PL-SA v1 are copyright licenses with a ShareAlike mechanism and an attribution mechanism, and [http://freedomdefined.org/Licenses#Free_Art_License they do not violate the definition of Free Cultural Licenses]. Thus, it satisfies the [[ShareAlike_compatibility_process_and_criteria#Minimum_compatibility_criteria.|minimum criteria]] for compatibility set forth in our [[ShareAlike_compatibility_process_and_criteria|ShareAlike compatibility criteria]]. Overall, the MulanOWL BY-SA v1 and MulanOWL BY-PL-SA v1 are similar to CC BY-SA 4.0, and the effect of each license as applied to a creative work is largely the same. Inevitably, there are differences between the licenses, which are explained in more detail below.

'''Summary of comparison: MulanOWL BY-SA v1 and MulanOWL BY-PL-SA v1<ref>Note that CC reviewed the English language version of the MulanOWL BY-SA v1 and MulanOWL BY-PL-SA v1 to conduct this analysis.</ref> and BY-SA 4.0'''

*The tone and scope of the licenses differ. The FAL is written more broadly and in general terms, and is designed for use with creative works protected by copyright. BY-SA is written in more specific terms, and is designed for use with creative works as well as material restricted by other rights closely related to copyright, such as databases protected by a sui generis right. Although the FAL licenses only copyright, it does have a provision preventing licensors from using related rights to prevent exercise of the rights granted under the license. BY-SA, on the other hand, contains an open ended definition of the rights that are licensed, but expressly excludes certain types of rights from the reach of the license.<ref>The rights expressly excluded from the license are moral rights, publicity, privacy and personality rights, and patent and trademark rights. The licensor waives and/or cannot assert all of these rights except patent and trademark rights.</ref> As to those rights that are licensed, BY-SA requires compliance with its conditions (attribution, ShareAlike) even when those rights, and not copyright, are implicated.

*The specific attribution and marking requirements in the two licenses vary slightly. BY-SA has more total necessary elements for proper attribution, though it allows for flexibility depending on the context in which the work is used. Despite having fewer total attribution and marking requirements, the FAL does have some requirements that are not included in BY-SA, such as indicating where the licensed content can be found or how the licensed content was modified.

*MulanOWL BY-SA v1 and MulanOWL BY-PL-SA v1 do not terminate even upon breach, as long as the breach was cured prior to, or within 30 days of, receiving notice of termination. CC BY-SA terminates automatically upon breach, but is reinstated automatically if the breach is cured within 30 days of discovery.

*

{| style="border-collapse: collapse;" border="1" cellpadding="10"
|-
! style="background-color:#CCCCCC;" | Features || style="background-color:#CCCCCC;" | BY-SA 4.0 || style="background-color:#CCCCCC;" | FAL
|-
| License scope || Copyright, neighboring rights and sui generis database rights (SGDRs) (Sec 1d) || Copyright only, but related rights may not challenge rights granted by license (Secs 2, 3)
|-
| Attribution trigger || If there is applicable copyright in work, then when work or adaptation of work is shared. (Sec 3a)
<br>
If there are applicable SGDRs in work, then when all or a substantial portion of database contents is shared. (Sec 4c)
|| When work (modified or not) is distributed (Sec 2.2)
|-
| Attribution removal clause || Yes (Sec 3a3) || No
|-
| Attribution elements ||
#creator and attribution parties
#copyright notice
# license notice
# disclaimer notice
# URI or link to the licensed material
# indicate and link to license
(Sec 3a1)
<br>
||
#name of author(s),
#attach license to work or indicate where license can be found
# info on where to access the originals
(Sec 2.2)
|-
| Special marking requirement if work is modified || Yes (indicate if you modified and retain indication of previous modifications) (Sec 3a1B)
|| Yes (indicate if you modified and what type of modifications were made) (Sec 2.3)
|-
| ShareAlike trigger || When adaptation is shared (Sec 3b) || When you distribute an adaptation (Sec 2.3)
|-
| ShareAlike scope || Must ShareAlike contributions to adaptations (Sec 3b);
<br>
Must ShareAlike database if it incorporates substantial portion of database contents (Sec 4b)
|| Must ShareAlike contributions to adaptations (Sec 2.3)
<br>
Must ShareAlike larger work if incorporate original in a way that makes it no longer accessible apart from larger work (Sec 4)
|-
| Source requirement || None || None
|-
| Effective technological measures || May not be applied by licensees if they restrict access to the work or adaptations (Sec 2a5C)
<br>
Licensees have express permission to circumvent if applied by licensor (Sec 2a4)
|| Not expressly mentioned, but may not be applied by licensees if they restrict users freedoms to copy (2.1), to distribute (2.2.) or to modify (2.3) the work
|-
| Moral rights || Waived only to the extent necessary to allow the license to function. (Sec 2b1) || Author’s rights may not challenge the rights granted by license. (Sec 3)
|-
| Termination || Automatic upon breach (Sec 6a) || Automatic upon breach (Sec 8)
|-
| Reinstatement after termination || Requires express permission unless cured within 30 days of discovery of violation (Sec 6b) || None
|-
| Reps & warranties || Expressly disclaimed (Sec 5) || Not mentioned
|-
| Choice of law || None || None
|-
| Option to comply with other license versions
|| Yes, but limited. Licensees may choose to comply with a later version of BY-SA if such version is applied to an adaptation of the work.
(Secs 2a5B, 3b1)
|| Yes, licensees may choose to comply with the version of the FAL that was applied to the copy distributed to them or a later version. (Sec 9)
|}

== Notes ==
<references/>

Legal Tools Translation/4.0/Kurdish

2023-05-31T19:19:31Z

CCID-yuanxiaoxu: /* Jurisdictions */

==Jurisdictions==
Iran, Iraq

==Translation Status==
4.0: In progress Step 2. Preparing the translation draft <br />
CC0: In progress Step 2. Preparing the translation draft

==Key dates==
'''4.0:'''

First draft was submitted: N/A<br />
Public comment period: N/A<br />
Translation officially published: N/A

'''CC0:'''

First draft was submitted: N/A<br />
Public comment period: N/A<br />
Translation officially published: N/A

==Translation team==
The Khamoosh Collective, lead and coordinated by pantea Armanfar

==Translation process==

==Draft translation files==

==FINAL translation files==

4.0: To be published.

CC0: To be published.

Legal Tools Translation

2023-05-31T19:19:17Z

CCID-yuanxiaoxu: /* Translation status of the 4.0 licenses and of CC0 */

=Welcome to the CC Translation Project!=
''Please note this is an evolving project and we welcome feedback.''

This is the main portal for projects translating the suite of six CC licenses and the CC0 Public Domain Dedication. For information on translating CC license deeds, visit [[Translating_CC_Deeds|Translating CC Deeds]]. If you are interested in translating the licenses or other legal tools, please see the [[Legal Code Translation Policy]].

==Translations Generally==
Beginning with version 4.0, CC is supporting official linguistic translations of its six (6) core licenses. '''Please note that translations involve linguistic translation only—they do not adapt the licenses or CC0 to account for local law.''' As of December 2012, CC also supports official translations of CC0 version 1.0.

Please see the [[Legal Code Translation Policy]] for more information on how to start a project to translate CC0 or the CC licenses officially into your local language. CC's policy is to support a single official translation into any particular language, absent a compelling reason otherwise. All legal code translation projects must be approved by Creative Commons in advance; please do not start a legal code translation project without first contacting Creative Commons.

(For version 3.0 of the licenses, CC supports unofficial translations only. These are not official and not suitable for adoption, but are provided solely for information purposes. '''Please do not use translations of the 3.0 international licenses—licensors should not link to or otherwise identify any of the unofficial translations when applying licenses to their materials.''' Those interested in translating CC licenses should join a translation project for the 4.0 licenses. If you would like to read the process for unofficial translations of 3.0, it has been moved [[Unofficial_translation_process_for_3.0|to a separate page]] for historical information.)

==Translation Guide==
As we work with teams on translation projects, we are developing collections of advice and issues to guide future teams' efforts. These include general proofing advice, as well as common errors, and words and phrases that are of key importance or have presented difficulty in each particular legal tool.

*Read the [[Legal tools translation guide]].

<div id="Published_translations"></div>
==Translation status of the 4.0 licenses and of CC0==

{| class="wikitable sortable" style="border-collapse: collapse;" border="1" cellpadding="10"
|-
! style="background-color:#CCCCCC;" | Language (and link to language page) || style="background-color:#CCCCCC;" | 4.0 translation status || style="background-color:#CCCCCC;" | CC0 translation status
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Amharic Amharic] || In progress - final review (Step 7) || Not started
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Arabic Arabic] || Final - published February 2017 ([https://creativecommons.org/2017/02/23/arabic-croatian-translations/ read]) || Not started
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Bahasa_Indonesia Bahasa Indonesia] || Final - published July 2015 ([https://creativecommons.org/2015/08/05/4-0-bahasa-indonesia-translation-and-a-book/ read]) || Not started
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Basque Basque] || Final - published October 2018 ([https://creativecommons.org/2018/10/03/latvian-4-0-and-basque-4-0-and-cc0-translations-now-available/ read]) || Final - published October 2018 ([https://creativecommons.org/2018/10/03/latvian-4-0-and-basque-4-0-and-cc0-translations-now-available/ read])
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Belarusian Belarusian] || Not started || Not started
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Bulgarian Bulgarian] || In progress - public comment period (Step 4) || In progress - public comment period (Step 4)
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Catalan Catalan] || Not started || In progress - review of draft (Step 3)
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Chinese_-_Traditional_and_Simplified Chinese - Traditional and Simplified] || Simplified published in Dec 2019; <br/>Traditional published in January 2020 ([https://creativecommons.org/2020/01/02/cc-licenses-in-simplified-traditional-chinese/ read]) || Final - published March 2018 ([https://creativecommons.org/2018/03/12/cc0-now-available-simplified-traditional-chinese-languages/ read])
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/ChiShona ChiShona] || In Progress - preparing draft (Step 2) || Not started
|-
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Cree Cree] || Not started || Not started
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Croatian Croatian] || Final - published February 2017 ([https://creativecommons.org/2017/02/23/arabic-croatian-translations/ read]) || Final - published July 2020
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Czech Czech] || Final - published June 2019 ([https://creativecommons.org/2019/08/05/new-official-translations-of-cc-legal-tools-published-for-korean-and-czech/ read]) || In progress - public comment period (Step 4)
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Danish Danish] || Final - published March 2023 ([https://creativecommons.org/2023/03/06/new-official-translations-of-cc-legal-tools-published-in-danish-frisian-and-german// read]) || In progress - public comment period (Step 4)
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Dutch Dutch] || Final - published February 2015 ([https://creativecommons.org/2015/02/25/dutch-translation-of-4-0-published/ read]) || Final - published March 2014 ([https://creativecommons.org/2014/03/18/first-cc0-official-translation-in-dutch/ read])
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Estonian Estonian] || In progress - public comment period (Step 4) || In progress - public comment period (Step 4)
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Farsi Farsi] || In Progress|| In Progress
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Finnish Finnish] || Final - published November 2014 ([https://creativecommons.org/2014/11/12/finnish-translation-of-4-0-published/ read])|| Final - published January 2015
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/French French] || Final - published June 2017 ([https://creativecommons.org/2017/06/28/cc-accueille-les-francophones-welcome-cc-4-0-french-license-translations/ read]) || Final - published June 2014 ([https://creativecommons.org/2014/06/27/cc0-official-translation-into-french-published/ read])
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Frisian Frisian] || Final - published March 2023 ([https://creativecommons.org/2023/03/06/new-official-translations-of-cc-legal-tools-published-in-danish-frisian-and-german// read]) || Not Started
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/German German] || Final - published January 2017 ([https://creativecommons.org/2017/01/23/german-4-0/ read in English] and [https://netzpolitik.org/2017/offizielle-deutsche-uebersetzung-der-cc-lizenzversion-4-0-ist-da/ in German]) || Final - published March 2023 ([https://creativecommons.org/2023/03/06/new-official-translations-of-cc-legal-tools-published-in-danish-frisian-and-german// read])
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Greek Greek] || Final - published November 2018 ([https://creativecommons.org/2018/12/12/ccs-4-0-license-suite-now-in-greek/ read]) || Final - published November 2019
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Hindi Hindi] || Not started || Not started
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Hungarian Hungarian] || In progress - public comment period (Step 4) || In progress - public comment period (Step 4)
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Italian Italian] || Final - published July 2017 ([https://creativecommons.org/2017/07/31/annuncia-la-traduzione-4-0-della-licenza-italiano/ read]) || Final - published July 2017
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Irish Irish] || In progress - public comment period (Step 4) || In progress - public comment period (Step 4)
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Japanese Japanese] || Final - published July 2015 || Final - published April 2015 ([https://creativecommons.org/2015/05/05/japanese-translation-of-cc0-published/ read])
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Korean Korean] || Final - published August 2019 ([https://creativecommons.org/2019/08/05/new-official-translations-of-cc-legal-tools-published-for-korean-and-czech/ read]) || Final - published August 2019 ([https://creativecommons.org/2019/08/05/new-official-translations-of-cc-legal-tools-published-for-korean-and-czech/ read])
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Kurdish Kurdish Sorani] || In Progress|| In Progress
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Latvian Latvian] || Final - published October 2018 ([https://creativecommons.org/2018/10/03/latvian-4-0-and-basque-4-0-and-cc0-translations-now-available/ read]) || Final - published October 2018 ([https://creativecommons.org/2018/10/03/latvian-4-0-and-basque-4-0-and-cc0-translations-now-available/ read])
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Lithuanian Lithuanian] || Final - published June 2018 ([https://creativecommons.org/2018/06/12/lithuanian-translation-of-4-0-available-for-use/ read]) || Final - published June 2018 ([https://creativecommons.org/2018/06/12/lithuanian-translation-of-4-0-available-for-use/ read])
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Malay Malay] || Not started || In progress - preparing draft (Step 2)
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Maltese Maltese] || In progress - public comment period (Step 4) || In progress - public comment period (Step 4)
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/M%C4%81ori Māori] || Final - published July 2015 || Not started
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Norwegian Norwegian] || Final - published December 2014 ([https://creativecommons.org/2014/12/23/norwegian-translation-of-4-0-published/ read]) || Not started
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Papiamento Papiamento] || Step 1 || Not started
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Polish Polish] || Final - published April 2016 ([https://creativecommons.org/2016/11/15/polish-translation/ read in English] and in [http://creativecommons.pl/2016/11/licencje-4-0-po-polsku/ Polish]) || Final - published October 2015 ([https://creativecommons.org/2015/10/09/cc0-now-available-in-polish-official-translation-published/ read])
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Portuguese Portuguese] || Final - published June 2018 ([https://creativecommons.org/2018/06/26/portuguese-translation-of-4-0-now-available/ read]) || Not started
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Romanian Romanian] || Final - published July 2020 ([https://creativecommons.org/2020/07/15/cc-license-and-cc0-available-in-romanian/ read]) || Final - published July 2020 ([https://creativecommons.org/2020/07/15/cc-license-and-cc0-available-in-romanian/ read])
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Russian Russian] || Final - published April 2018 ([https://creativecommons.org/2018/04/20/russian-translation-of-4-0-published/ read]) || Not started
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Serbian Serbian] || In progress - public comment (Step 4) || In progress - public comment (Step 4)
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Slovak Slovak] || In progress - final review (Step 7) || In progress - public comment period (Step 4)
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Slovenian Slovenian] || Final - published June 2020 ([https://creativecommons.org/2020/06/08/the-cc-license-suite-4-0-and-cc0-are-now-available-in-slovenian/ read]) || Final - published June 2020 ([https://creativecommons.org/2020/06/08/the-cc-license-suite-4-0-and-cc0-are-now-available-in-slovenian/ read])
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Castellano Spanish (Castellano)] || Final - published September 2018 ([https://creativecommons.org/2018/09/11/spanish-translation-of-4-0-now-available-la-traduccion-al-castellano-de-la-version-4-0-de-las-licencias-esta-ahora-disponible/ read]) || Final - published June 2019 ([https://creativecommons.org/2019/06/10/spanish-cc0-translation/ read])
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Swedish Swedish] || Final - published January 2017 ([https://creativecommons.org/2017/01/11/announcing-swedish-translation-4-0-license/ read]) || Final - published January 2017
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Turkish Turkish] || Final - published May 2017 ([https://creativecommons.org/2017/05/25/creative-commons-4-0-license-now-turkish/ read in English] and in [http://creativecommons.org.tr/creative-commons-4-0-lisanslari-simdi-turkce/ Turkish]) || Not started
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Ukrainian Ukrainian] || Final - published June 2015 ([https://creativecommons.org/2015/06/24/ukrainian-translation-of-cc-4-0/ read]) || Not started
|}

[[Category:Legal]]
[[Category:Translation Project]]

Legal Tools Translation/4.0/Kurdish

2023-05-25T20:13:02Z

CCID-yuanxiaoxu: Created page with "==Jurisdictions== Iran, Iraq, Syria, Turkey ==Translation Status== 4.0: In progress Step 2. Preparing the translation draft <br /> CC0: In progress Step 2. Preparing the tran..."

==Jurisdictions==
Iran, Iraq, Syria, Turkey

==Translation Status==
4.0: In progress Step 2. Preparing the translation draft <br />
CC0: In progress Step 2. Preparing the translation draft

==Key dates==
'''4.0:'''

First draft was submitted: N/A<br />
Public comment period: N/A<br />
Translation officially published: N/A

'''CC0:'''

First draft was submitted: N/A<br />
Public comment period: N/A<br />
Translation officially published: N/A

==Translation team==
The Khamoosh Collective, lead and coordinated by pantea Armanfar

==Translation process==

==Draft translation files==

==FINAL translation files==

4.0: To be published.

CC0: To be published.

Legal Tools Translation/4.0/Farsi

2023-05-25T20:11:22Z

CCID-yuanxiaoxu: Created page with "==Jurisdictions== Iran, Afghanistan, Tajikistan ==Translation Status== 4.0: In progress Step 2. Preparing the translation draft <br /> CC0: In progress Step 2. Preparing the..."

==Jurisdictions==
Iran, Afghanistan, Tajikistan

==Translation Status==
4.0: In progress Step 2. Preparing the translation draft <br />
CC0: In progress Step 2. Preparing the translation draft

==Key dates==
'''4.0:'''

First draft was submitted: N/A<br />
Public comment period: N/A<br />
Translation officially published: N/A

'''CC0:'''

First draft was submitted: N/A<br />
Public comment period: N/A<br />
Translation officially published: N/A

==Translation team==
The Khamoosh Collective, lead and coordinated by pantea Armanfar

==Translation process==

==Draft translation files==

==FINAL translation files==

4.0: To be published.

CC0: To be published.

Legal Tools Translation

2023-05-25T20:06:56Z

CCID-yuanxiaoxu: /* Translation status of the 4.0 licenses and of CC0 */

=Welcome to the CC Translation Project!=
''Please note this is an evolving project and we welcome feedback.''

This is the main portal for projects translating the suite of six CC licenses and the CC0 Public Domain Dedication. For information on translating CC license deeds, visit [[Translating_CC_Deeds|Translating CC Deeds]]. If you are interested in translating the licenses or other legal tools, please see the [[Legal Code Translation Policy]].

==Translations Generally==
Beginning with version 4.0, CC is supporting official linguistic translations of its six (6) core licenses. '''Please note that translations involve linguistic translation only—they do not adapt the licenses or CC0 to account for local law.''' As of December 2012, CC also supports official translations of CC0 version 1.0.

Please see the [[Legal Code Translation Policy]] for more information on how to start a project to translate CC0 or the CC licenses officially into your local language. CC's policy is to support a single official translation into any particular language, absent a compelling reason otherwise. All legal code translation projects must be approved by Creative Commons in advance; please do not start a legal code translation project without first contacting Creative Commons.

(For version 3.0 of the licenses, CC supports unofficial translations only. These are not official and not suitable for adoption, but are provided solely for information purposes. '''Please do not use translations of the 3.0 international licenses—licensors should not link to or otherwise identify any of the unofficial translations when applying licenses to their materials.''' Those interested in translating CC licenses should join a translation project for the 4.0 licenses. If you would like to read the process for unofficial translations of 3.0, it has been moved [[Unofficial_translation_process_for_3.0|to a separate page]] for historical information.)

==Translation Guide==
As we work with teams on translation projects, we are developing collections of advice and issues to guide future teams' efforts. These include general proofing advice, as well as common errors, and words and phrases that are of key importance or have presented difficulty in each particular legal tool.

*Read the [[Legal tools translation guide]].

<div id="Published_translations"></div>
==Translation status of the 4.0 licenses and of CC0==

{| class="wikitable sortable" style="border-collapse: collapse;" border="1" cellpadding="10"
|-
! style="background-color:#CCCCCC;" | Language (and link to language page) || style="background-color:#CCCCCC;" | 4.0 translation status || style="background-color:#CCCCCC;" | CC0 translation status
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Amharic Amharic] || In progress - final review (Step 7) || Not started
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Arabic Arabic] || Final - published February 2017 ([https://creativecommons.org/2017/02/23/arabic-croatian-translations/ read]) || Not started
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Bahasa_Indonesia Bahasa Indonesia] || Final - published July 2015 ([https://creativecommons.org/2015/08/05/4-0-bahasa-indonesia-translation-and-a-book/ read]) || Not started
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Basque Basque] || Final - published October 2018 ([https://creativecommons.org/2018/10/03/latvian-4-0-and-basque-4-0-and-cc0-translations-now-available/ read]) || Final - published October 2018 ([https://creativecommons.org/2018/10/03/latvian-4-0-and-basque-4-0-and-cc0-translations-now-available/ read])
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Belarusian Belarusian] || Not started || Not started
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Bulgarian Bulgarian] || In progress - public comment period (Step 4) || In progress - public comment period (Step 4)
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Catalan Catalan] || Not started || In progress - review of draft (Step 3)
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Chinese_-_Traditional_and_Simplified Chinese - Traditional and Simplified] || Simplified published in Dec 2019; <br/>Traditional published in January 2020 ([https://creativecommons.org/2020/01/02/cc-licenses-in-simplified-traditional-chinese/ read]) || Final - published March 2018 ([https://creativecommons.org/2018/03/12/cc0-now-available-simplified-traditional-chinese-languages/ read])
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/ChiShona ChiShona] || In Progress - preparing draft (Step 2) || Not started
|-
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Cree Cree] || Not started || Not started
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Croatian Croatian] || Final - published February 2017 ([https://creativecommons.org/2017/02/23/arabic-croatian-translations/ read]) || Final - published July 2020
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Czech Czech] || Final - published June 2019 ([https://creativecommons.org/2019/08/05/new-official-translations-of-cc-legal-tools-published-for-korean-and-czech/ read]) || In progress - public comment period (Step 4)
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Danish Danish] || Final - published March 2023 ([https://creativecommons.org/2023/03/06/new-official-translations-of-cc-legal-tools-published-in-danish-frisian-and-german// read]) || In progress - public comment period (Step 4)
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Dutch Dutch] || Final - published February 2015 ([https://creativecommons.org/2015/02/25/dutch-translation-of-4-0-published/ read]) || Final - published March 2014 ([https://creativecommons.org/2014/03/18/first-cc0-official-translation-in-dutch/ read])
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Estonian Estonian] || In progress - public comment period (Step 4) || In progress - public comment period (Step 4)
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Farsi Farsi] || In Progress|| In Progress
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Finnish Finnish] || Final - published November 2014 ([https://creativecommons.org/2014/11/12/finnish-translation-of-4-0-published/ read])|| Final - published January 2015
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/French French] || Final - published June 2017 ([https://creativecommons.org/2017/06/28/cc-accueille-les-francophones-welcome-cc-4-0-french-license-translations/ read]) || Final - published June 2014 ([https://creativecommons.org/2014/06/27/cc0-official-translation-into-french-published/ read])
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Frisian Frisian] || Final - published March 2023 ([https://creativecommons.org/2023/03/06/new-official-translations-of-cc-legal-tools-published-in-danish-frisian-and-german// read]) || Not Started
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/German German] || Final - published January 2017 ([https://creativecommons.org/2017/01/23/german-4-0/ read in English] and [https://netzpolitik.org/2017/offizielle-deutsche-uebersetzung-der-cc-lizenzversion-4-0-ist-da/ in German]) || Final - published March 2023 ([https://creativecommons.org/2023/03/06/new-official-translations-of-cc-legal-tools-published-in-danish-frisian-and-german// read])
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Greek Greek] || Final - published November 2018 ([https://creativecommons.org/2018/12/12/ccs-4-0-license-suite-now-in-greek/ read]) || Final - published November 2019
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Hindi Hindi] || Not started || Not started
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Hungarian Hungarian] || In progress - public comment period (Step 4) || In progress - public comment period (Step 4)
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Italian Italian] || Final - published July 2017 ([https://creativecommons.org/2017/07/31/annuncia-la-traduzione-4-0-della-licenza-italiano/ read]) || Final - published July 2017
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Irish Irish] || In progress - public comment period (Step 4) || In progress - public comment period (Step 4)
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Japanese Japanese] || Final - published July 2015 || Final - published April 2015 ([https://creativecommons.org/2015/05/05/japanese-translation-of-cc0-published/ read])
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Korean Korean] || Final - published August 2019 ([https://creativecommons.org/2019/08/05/new-official-translations-of-cc-legal-tools-published-for-korean-and-czech/ read]) || Final - published August 2019 ([https://creativecommons.org/2019/08/05/new-official-translations-of-cc-legal-tools-published-for-korean-and-czech/ read])
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Kurdish Kurdish] || In Progress|| In Progress
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Latvian Latvian] || Final - published October 2018 ([https://creativecommons.org/2018/10/03/latvian-4-0-and-basque-4-0-and-cc0-translations-now-available/ read]) || Final - published October 2018 ([https://creativecommons.org/2018/10/03/latvian-4-0-and-basque-4-0-and-cc0-translations-now-available/ read])
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Lithuanian Lithuanian] || Final - published June 2018 ([https://creativecommons.org/2018/06/12/lithuanian-translation-of-4-0-available-for-use/ read]) || Final - published June 2018 ([https://creativecommons.org/2018/06/12/lithuanian-translation-of-4-0-available-for-use/ read])
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Malay Malay] || Not started || In progress - preparing draft (Step 2)
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Maltese Maltese] || In progress - public comment period (Step 4) || In progress - public comment period (Step 4)
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/M%C4%81ori Māori] || Final - published July 2015 || Not started
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Norwegian Norwegian] || Final - published December 2014 ([https://creativecommons.org/2014/12/23/norwegian-translation-of-4-0-published/ read]) || Not started
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Papiamento Papiamento] || Step 1 || Not started
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Polish Polish] || Final - published April 2016 ([https://creativecommons.org/2016/11/15/polish-translation/ read in English] and in [http://creativecommons.pl/2016/11/licencje-4-0-po-polsku/ Polish]) || Final - published October 2015 ([https://creativecommons.org/2015/10/09/cc0-now-available-in-polish-official-translation-published/ read])
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Portuguese Portuguese] || Final - published June 2018 ([https://creativecommons.org/2018/06/26/portuguese-translation-of-4-0-now-available/ read]) || Not started
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Romanian Romanian] || Final - published July 2020 ([https://creativecommons.org/2020/07/15/cc-license-and-cc0-available-in-romanian/ read]) || Final - published July 2020 ([https://creativecommons.org/2020/07/15/cc-license-and-cc0-available-in-romanian/ read])
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Russian Russian] || Final - published April 2018 ([https://creativecommons.org/2018/04/20/russian-translation-of-4-0-published/ read]) || Not started
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Serbian Serbian] || In progress - public comment (Step 4) || In progress - public comment (Step 4)
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Slovak Slovak] || In progress - final review (Step 7) || In progress - public comment period (Step 4)
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Slovenian Slovenian] || Final - published June 2020 ([https://creativecommons.org/2020/06/08/the-cc-license-suite-4-0-and-cc0-are-now-available-in-slovenian/ read]) || Final - published June 2020 ([https://creativecommons.org/2020/06/08/the-cc-license-suite-4-0-and-cc0-are-now-available-in-slovenian/ read])
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Castellano Spanish (Castellano)] || Final - published September 2018 ([https://creativecommons.org/2018/09/11/spanish-translation-of-4-0-now-available-la-traduccion-al-castellano-de-la-version-4-0-de-las-licencias-esta-ahora-disponible/ read]) || Final - published June 2019 ([https://creativecommons.org/2019/06/10/spanish-cc0-translation/ read])
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Swedish Swedish] || Final - published January 2017 ([https://creativecommons.org/2017/01/11/announcing-swedish-translation-4-0-license/ read]) || Final - published January 2017
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Turkish Turkish] || Final - published May 2017 ([https://creativecommons.org/2017/05/25/creative-commons-4-0-license-now-turkish/ read in English] and in [http://creativecommons.org.tr/creative-commons-4-0-lisanslari-simdi-turkce/ Turkish]) || Not started
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Ukrainian Ukrainian] || Final - published June 2015 ([https://creativecommons.org/2015/06/24/ukrainian-translation-of-cc-4-0/ read]) || Not started
|}

[[Category:Legal]]
[[Category:Translation Project]]

Legal Tools Translation/4.0/Papiamento

2023-03-09T17:59:22Z

CCID-yuanxiaoxu: Created page with "==Jurisdictions== Aruba ==Translation Status== 4.0: Step 1 CC0: Not started ==Key dates== '''4.0:''' '''CC0:''' Not started. ==Translation team== ==Translation process=..."

==Jurisdictions==
Aruba

==Translation Status==
4.0: Step 1
CC0: Not started

==Key dates==
'''4.0:'''

'''CC0:'''

Not started.

==Translation team==

==Translation process==

==Draft translation files==

==FINAL translation files==

Legal Tools Translation/4.0/Frisian

2023-03-09T17:58:32Z

CCID-yuanxiaoxu: /* FINAL translation files */

==Jurisdictions==
Netherlands

==Translation Status==
4.0: Completed <br />
CC0: Not started

==Key dates==
'''4.0:'''

First draft was submitted: 25 November 2022<br />
Public comment period: Comment period was 2-30 December 2022. The draft is available [https://docs.google.com/document/d/1zrFwf8R2ZGRGrh2u9fHvkvBp1Xt7NExQwz1TsSwMs5c/ here] and comments can be added on the [https://wiki.creativecommons.org/wiki/Talk:Legal_Tools_Translation/4.0/Frisian Discussion] space.<br />
Translation officially published: March 2023

'''CC0:'''

Not started.

==Translation team==
Friduwih Riemersma.

==Translation process==
The first translation drafts of BY-NC-SA was created by Friduwih Riemersma. CC community members are reviewing and revising the draft.

==Draft translation files==

==FINAL translation files==

4.0: .

CC0: To be published.

Legal Tools Translation/4.0/Frisian

2023-03-09T17:58:11Z

CCID-yuanxiaoxu: /* Key dates */

Legal Tools Translation/4.0/Frisian

2023-03-09T17:57:53Z

CCID-yuanxiaoxu: /* Translation Status */

==Jurisdictions==
Netherlands

==Translation Status==
4.0: Completed <br />
CC0: Not started

==Key dates==
'''4.0:'''

First draft was submitted: 25 November 2022<br />
Public comment period: Comment period was 2-30 December 2022. The draft is available [https://docs.google.com/document/d/1zrFwf8R2ZGRGrh2u9fHvkvBp1Xt7NExQwz1TsSwMs5c/ here] and comments can be added on the [https://wiki.creativecommons.org/wiki/Talk:Legal_Tools_Translation/4.0/Frisian Discussion] space.<br />
Translation officially published: TBA

'''CC0:'''

Not started.

==Translation team==
Friduwih Riemersma.

==Translation process==
The first translation drafts of BY-NC-SA was created by Friduwih Riemersma. CC community members are reviewing and revising the draft.

==Draft translation files==

==FINAL translation files==

4.0: To be published.

CC0: To be published.

Legal Tools Translation

2023-03-09T17:56:56Z

CCID-yuanxiaoxu: /* Translation status of the 4.0 licenses and of CC0 */

=Welcome to the CC Translation Project!=
''Please note this is an evolving project and we welcome feedback.''

This is the main portal for projects translating the suite of six CC licenses and the CC0 Public Domain Dedication. For information on translating CC license deeds, visit [[Translating_CC_Deeds|Translating CC Deeds]]. If you are interested in translating the licenses or other legal tools, please see the [[Legal Code Translation Policy]].

==Translations Generally==
Beginning with version 4.0, CC is supporting official linguistic translations of its six (6) core licenses. '''Please note that translations involve linguistic translation only—they do not adapt the licenses or CC0 to account for local law.''' As of December 2012, CC also supports official translations of CC0 version 1.0.

Please see the [[Legal Code Translation Policy]] for more information on how to start a project to translate CC0 or the CC licenses officially into your local language. CC's policy is to support a single official translation into any particular language, absent a compelling reason otherwise. All legal code translation projects must be approved by Creative Commons in advance; please do not start a legal code translation project without first contacting Creative Commons.

(For version 3.0 of the licenses, CC supports unofficial translations only. These are not official and not suitable for adoption, but are provided solely for information purposes. '''Please do not use translations of the 3.0 international licenses—licensors should not link to or otherwise identify any of the unofficial translations when applying licenses to their materials.''' Those interested in translating CC licenses should join a translation project for the 4.0 licenses. If you would like to read the process for unofficial translations of 3.0, it has been moved [[Unofficial_translation_process_for_3.0|to a separate page]] for historical information.)

==Translation Guide==
As we work with teams on translation projects, we are developing collections of advice and issues to guide future teams' efforts. These include general proofing advice, as well as common errors, and words and phrases that are of key importance or have presented difficulty in each particular legal tool.

*Read the [[Legal tools translation guide]].

<div id="Published_translations"></div>
==Translation status of the 4.0 licenses and of CC0==

{| class="wikitable sortable" style="border-collapse: collapse;" border="1" cellpadding="10"
|-
! style="background-color:#CCCCCC;" | Language (and link to language page) || style="background-color:#CCCCCC;" | 4.0 translation status || style="background-color:#CCCCCC;" | CC0 translation status
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Amharic Amharic] || In progress - final review (Step 7) || Not started
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Arabic Arabic] || Final - published February 2017 ([https://creativecommons.org/2017/02/23/arabic-croatian-translations/ read]) || Not started
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Bahasa_Indonesia Bahasa Indonesia] || Final - published July 2015 ([https://creativecommons.org/2015/08/05/4-0-bahasa-indonesia-translation-and-a-book/ read]) || Not started
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Basque Basque] || Final - published October 2018 ([https://creativecommons.org/2018/10/03/latvian-4-0-and-basque-4-0-and-cc0-translations-now-available/ read]) || Final - published October 2018 ([https://creativecommons.org/2018/10/03/latvian-4-0-and-basque-4-0-and-cc0-translations-now-available/ read])
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Belarusian Belarusian] || Not started || Not started
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Bulgarian Bulgarian] || In progress - public comment period (Step 4) || In progress - public comment period (Step 4)
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Catalan Catalan] || Not started || In progress - review of draft (Step 3)
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Chinese_-_Traditional_and_Simplified Chinese - Traditional and Simplified] || Simplified published in Dec 2019; <br/>Traditional published in January 2020 ([https://creativecommons.org/2020/01/02/cc-licenses-in-simplified-traditional-chinese/ read]) || Final - published March 2018 ([https://creativecommons.org/2018/03/12/cc0-now-available-simplified-traditional-chinese-languages/ read])
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/ChiShona ChiShona] || In Progress - preparing draft (Step 2) || Not started
|-
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Cree Cree] || Not started || Not started
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Croatian Croatian] || Final - published February 2017 ([https://creativecommons.org/2017/02/23/arabic-croatian-translations/ read]) || Final - published July 2020
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Czech Czech] || Final - published June 2019 ([https://creativecommons.org/2019/08/05/new-official-translations-of-cc-legal-tools-published-for-korean-and-czech/ read]) || In progress - public comment period (Step 4)
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Danish Danish] || Final - published March 2023 ([https://creativecommons.org/2023/03/06/new-official-translations-of-cc-legal-tools-published-in-danish-frisian-and-german// read]) || In progress - public comment period (Step 4)
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Dutch Dutch] || Final - published February 2015 ([https://creativecommons.org/2015/02/25/dutch-translation-of-4-0-published/ read]) || Final - published March 2014 ([https://creativecommons.org/2014/03/18/first-cc0-official-translation-in-dutch/ read])
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Estonian Estonian] || In progress - public comment period (Step 4) || In progress - public comment period (Step 4)
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Finnish Finnish] || Final - published November 2014 ([https://creativecommons.org/2014/11/12/finnish-translation-of-4-0-published/ read])|| Final - published January 2015
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/French French] || Final - published June 2017 ([https://creativecommons.org/2017/06/28/cc-accueille-les-francophones-welcome-cc-4-0-french-license-translations/ read]) || Final - published June 2014 ([https://creativecommons.org/2014/06/27/cc0-official-translation-into-french-published/ read])
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Frisian Frisian] || Final - published March 2023 ([https://creativecommons.org/2023/03/06/new-official-translations-of-cc-legal-tools-published-in-danish-frisian-and-german// read]) || Not Started
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/German German] || Final - published January 2017 ([https://creativecommons.org/2017/01/23/german-4-0/ read in English] and [https://netzpolitik.org/2017/offizielle-deutsche-uebersetzung-der-cc-lizenzversion-4-0-ist-da/ in German]) || Final - published March 2023 ([https://creativecommons.org/2023/03/06/new-official-translations-of-cc-legal-tools-published-in-danish-frisian-and-german// read])
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Greek Greek] || Final - published November 2018 ([https://creativecommons.org/2018/12/12/ccs-4-0-license-suite-now-in-greek/ read]) || Final - published November 2019
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Hindi Hindi] || Not started || Not started
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Hungarian Hungarian] || In progress - public comment period (Step 4) || In progress - public comment period (Step 4)
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Italian Italian] || Final - published July 2017 ([https://creativecommons.org/2017/07/31/annuncia-la-traduzione-4-0-della-licenza-italiano/ read]) || Final - published July 2017
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Irish Irish] || In progress - public comment period (Step 4) || In progress - public comment period (Step 4)
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Japanese Japanese] || Final - published July 2015 || Final - published April 2015 ([https://creativecommons.org/2015/05/05/japanese-translation-of-cc0-published/ read])
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Korean Korean] || Final - published August 2019 ([https://creativecommons.org/2019/08/05/new-official-translations-of-cc-legal-tools-published-for-korean-and-czech/ read]) || Final - published August 2019 ([https://creativecommons.org/2019/08/05/new-official-translations-of-cc-legal-tools-published-for-korean-and-czech/ read])
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Latvian Latvian] || Final - published October 2018 ([https://creativecommons.org/2018/10/03/latvian-4-0-and-basque-4-0-and-cc0-translations-now-available/ read]) || Final - published October 2018 ([https://creativecommons.org/2018/10/03/latvian-4-0-and-basque-4-0-and-cc0-translations-now-available/ read])
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Lithuanian Lithuanian] || Final - published June 2018 ([https://creativecommons.org/2018/06/12/lithuanian-translation-of-4-0-available-for-use/ read]) || Final - published June 2018 ([https://creativecommons.org/2018/06/12/lithuanian-translation-of-4-0-available-for-use/ read])
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Malay Malay] || Not started || In progress - preparing draft (Step 2)
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Maltese Maltese] || In progress - public comment period (Step 4) || In progress - public comment period (Step 4)
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/M%C4%81ori Māori] || Final - published July 2015 || Not started
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Norwegian Norwegian] || Final - published December 2014 ([https://creativecommons.org/2014/12/23/norwegian-translation-of-4-0-published/ read]) || Not started
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Papiamento Papiamento] || Step 1 || Not started
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Polish Polish] || Final - published April 2016 ([https://creativecommons.org/2016/11/15/polish-translation/ read in English] and in [http://creativecommons.pl/2016/11/licencje-4-0-po-polsku/ Polish]) || Final - published October 2015 ([https://creativecommons.org/2015/10/09/cc0-now-available-in-polish-official-translation-published/ read])
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Portuguese Portuguese] || Final - published June 2018 ([https://creativecommons.org/2018/06/26/portuguese-translation-of-4-0-now-available/ read]) || Not started
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Romanian Romanian] || Final - published July 2020 ([https://creativecommons.org/2020/07/15/cc-license-and-cc0-available-in-romanian/ read]) || Final - published July 2020 ([https://creativecommons.org/2020/07/15/cc-license-and-cc0-available-in-romanian/ read])
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Russian Russian] || Final - published April 2018 ([https://creativecommons.org/2018/04/20/russian-translation-of-4-0-published/ read]) || Not started
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Serbian Serbian] || In progress - public comment (Step 4) || In progress - public comment (Step 4)
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Slovak Slovak] || In progress - final review (Step 7) || In progress - public comment period (Step 4)
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Slovenian Slovenian] || Final - published June 2020 ([https://creativecommons.org/2020/06/08/the-cc-license-suite-4-0-and-cc0-are-now-available-in-slovenian/ read]) || Final - published June 2020 ([https://creativecommons.org/2020/06/08/the-cc-license-suite-4-0-and-cc0-are-now-available-in-slovenian/ read])
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Castellano Spanish (Castellano)] || Final - published September 2018 ([https://creativecommons.org/2018/09/11/spanish-translation-of-4-0-now-available-la-traduccion-al-castellano-de-la-version-4-0-de-las-licencias-esta-ahora-disponible/ read]) || Final - published June 2019 ([https://creativecommons.org/2019/06/10/spanish-cc0-translation/ read])
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Swedish Swedish] || Final - published January 2017 ([https://creativecommons.org/2017/01/11/announcing-swedish-translation-4-0-license/ read]) || Final - published January 2017
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Turkish Turkish] || Final - published May 2017 ([https://creativecommons.org/2017/05/25/creative-commons-4-0-license-now-turkish/ read in English] and in [http://creativecommons.org.tr/creative-commons-4-0-lisanslari-simdi-turkce/ Turkish]) || Not started
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Ukrainian Ukrainian] || Final - published June 2015 ([https://creativecommons.org/2015/06/24/ukrainian-translation-of-cc-4-0/ read]) || Not started
|}

[[Category:Legal]]
[[Category:Translation Project]]

Legal Tools Translation

2023-03-09T17:56:12Z

CCID-yuanxiaoxu: /* Translation status of the 4.0 licenses and of CC0 */

=Welcome to the CC Translation Project!=
''Please note this is an evolving project and we welcome feedback.''

This is the main portal for projects translating the suite of six CC licenses and the CC0 Public Domain Dedication. For information on translating CC license deeds, visit [[Translating_CC_Deeds|Translating CC Deeds]]. If you are interested in translating the licenses or other legal tools, please see the [[Legal Code Translation Policy]].

==Translations Generally==
Beginning with version 4.0, CC is supporting official linguistic translations of its six (6) core licenses. '''Please note that translations involve linguistic translation only—they do not adapt the licenses or CC0 to account for local law.''' As of December 2012, CC also supports official translations of CC0 version 1.0.

Please see the [[Legal Code Translation Policy]] for more information on how to start a project to translate CC0 or the CC licenses officially into your local language. CC's policy is to support a single official translation into any particular language, absent a compelling reason otherwise. All legal code translation projects must be approved by Creative Commons in advance; please do not start a legal code translation project without first contacting Creative Commons.

(For version 3.0 of the licenses, CC supports unofficial translations only. These are not official and not suitable for adoption, but are provided solely for information purposes. '''Please do not use translations of the 3.0 international licenses—licensors should not link to or otherwise identify any of the unofficial translations when applying licenses to their materials.''' Those interested in translating CC licenses should join a translation project for the 4.0 licenses. If you would like to read the process for unofficial translations of 3.0, it has been moved [[Unofficial_translation_process_for_3.0|to a separate page]] for historical information.)

==Translation Guide==
As we work with teams on translation projects, we are developing collections of advice and issues to guide future teams' efforts. These include general proofing advice, as well as common errors, and words and phrases that are of key importance or have presented difficulty in each particular legal tool.

*Read the [[Legal tools translation guide]].

<div id="Published_translations"></div>
==Translation status of the 4.0 licenses and of CC0==

{| class="wikitable sortable" style="border-collapse: collapse;" border="1" cellpadding="10"
|-
! style="background-color:#CCCCCC;" | Language (and link to language page) || style="background-color:#CCCCCC;" | 4.0 translation status || style="background-color:#CCCCCC;" | CC0 translation status
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Amharic Amharic] || In progress - final review (Step 7) || Not started
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Arabic Arabic] || Final - published February 2017 ([https://creativecommons.org/2017/02/23/arabic-croatian-translations/ read]) || Not started
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Bahasa_Indonesia Bahasa Indonesia] || Final - published July 2015 ([https://creativecommons.org/2015/08/05/4-0-bahasa-indonesia-translation-and-a-book/ read]) || Not started
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Basque Basque] || Final - published October 2018 ([https://creativecommons.org/2018/10/03/latvian-4-0-and-basque-4-0-and-cc0-translations-now-available/ read]) || Final - published October 2018 ([https://creativecommons.org/2018/10/03/latvian-4-0-and-basque-4-0-and-cc0-translations-now-available/ read])
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Belarusian Belarusian] || Not started || Not started
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Bulgarian Bulgarian] || In progress - public comment period (Step 4) || In progress - public comment period (Step 4)
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Catalan Catalan] || Not started || In progress - review of draft (Step 3)
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Chinese_-_Traditional_and_Simplified Chinese - Traditional and Simplified] || Simplified published in Dec 2019; <br/>Traditional published in January 2020 ([https://creativecommons.org/2020/01/02/cc-licenses-in-simplified-traditional-chinese/ read]) || Final - published March 2018 ([https://creativecommons.org/2018/03/12/cc0-now-available-simplified-traditional-chinese-languages/ read])
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/ChiShona ChiShona] || In Progress - preparing draft (Step 2) || Not started
|-
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Cree Cree] || Not started || Not started
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Croatian Croatian] || Final - published February 2017 ([https://creativecommons.org/2017/02/23/arabic-croatian-translations/ read]) || Final - published July 2020
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Czech Czech] || Final - published June 2019 ([https://creativecommons.org/2019/08/05/new-official-translations-of-cc-legal-tools-published-for-korean-and-czech/ read]) || In progress - public comment period (Step 4)
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Danish Danish] || Final - published March 2023 ([https://creativecommons.org/2023/03/06/new-official-translations-of-cc-legal-tools-published-in-danish-frisian-and-german// read]) || In progress - public comment period (Step 4)
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Dutch Dutch] || Final - published February 2015 ([https://creativecommons.org/2015/02/25/dutch-translation-of-4-0-published/ read]) || Final - published March 2014 ([https://creativecommons.org/2014/03/18/first-cc0-official-translation-in-dutch/ read])
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Estonian Estonian] || In progress - public comment period (Step 4) || In progress - public comment period (Step 4)
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Finnish Finnish] || Final - published November 2014 ([https://creativecommons.org/2014/11/12/finnish-translation-of-4-0-published/ read])|| Final - published January 2015
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/French French] || Final - published June 2017 ([https://creativecommons.org/2017/06/28/cc-accueille-les-francophones-welcome-cc-4-0-french-license-translations/ read]) || Final - published June 2014 ([https://creativecommons.org/2014/06/27/cc0-official-translation-into-french-published/ read])
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Frisian Frisian] || Final - published March 2023 ([https://creativecommons.org/2023/03/06/new-official-translations-of-cc-legal-tools-published-in-danish-frisian-and-german// read]) || Not Started
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/German German] || Final - published January 2017 ([https://creativecommons.org/2017/01/23/german-4-0/ read in English] and [https://netzpolitik.org/2017/offizielle-deutsche-uebersetzung-der-cc-lizenzversion-4-0-ist-da/ in German]) || Final - published March 2023 ([https://creativecommons.org/2023/03/06/new-official-translations-of-cc-legal-tools-published-in-danish-frisian-and-german// read])
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Greek Greek] || Final - published November 2018 ([https://creativecommons.org/2018/12/12/ccs-4-0-license-suite-now-in-greek/ read]) || Final - published November 2019
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Hindi Hindi] || Not started || Not started
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Hungarian Hungarian] || In progress - public comment period (Step 4) || In progress - public comment period (Step 4)
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Italian Italian] || Final - published July 2017 ([https://creativecommons.org/2017/07/31/annuncia-la-traduzione-4-0-della-licenza-italiano/ read]) || Final - published July 2017
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Irish Irish] || In progress - public comment period (Step 4) || In progress - public comment period (Step 4)
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Japanese Japanese] || Final - published July 2015 || Final - published April 2015 ([https://creativecommons.org/2015/05/05/japanese-translation-of-cc0-published/ read])
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Korean Korean] || Final - published August 2019 ([https://creativecommons.org/2019/08/05/new-official-translations-of-cc-legal-tools-published-for-korean-and-czech/ read]) || Final - published August 2019 ([https://creativecommons.org/2019/08/05/new-official-translations-of-cc-legal-tools-published-for-korean-and-czech/ read])
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Latvian Latvian] || Final - published October 2018 ([https://creativecommons.org/2018/10/03/latvian-4-0-and-basque-4-0-and-cc0-translations-now-available/ read]) || Final - published October 2018 ([https://creativecommons.org/2018/10/03/latvian-4-0-and-basque-4-0-and-cc0-translations-now-available/ read])
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Lithuanian Lithuanian] || Final - published June 2018 ([https://creativecommons.org/2018/06/12/lithuanian-translation-of-4-0-available-for-use/ read]) || Final - published June 2018 ([https://creativecommons.org/2018/06/12/lithuanian-translation-of-4-0-available-for-use/ read])
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Malay Malay] || Not started || In progress - preparing draft (Step 2)
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Maltese Maltese] || In progress - public comment period (Step 4) || In progress - public comment period (Step 4)
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/M%C4%81ori Māori] || Final - published July 2015 || Not started
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Norwegian Norwegian] || Final - published December 2014 ([https://creativecommons.org/2014/12/23/norwegian-translation-of-4-0-published/ read]) || Not started
|
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Papiamento Papiamento] || Step 1 || Not started
|
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Polish Polish] || Final - published April 2016 ([https://creativecommons.org/2016/11/15/polish-translation/ read in English] and in [http://creativecommons.pl/2016/11/licencje-4-0-po-polsku/ Polish]) || Final - published October 2015 ([https://creativecommons.org/2015/10/09/cc0-now-available-in-polish-official-translation-published/ read])
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Portuguese Portuguese] || Final - published June 2018 ([https://creativecommons.org/2018/06/26/portuguese-translation-of-4-0-now-available/ read]) || Not started
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Romanian Romanian] || Final - published July 2020 ([https://creativecommons.org/2020/07/15/cc-license-and-cc0-available-in-romanian/ read]) || Final - published July 2020 ([https://creativecommons.org/2020/07/15/cc-license-and-cc0-available-in-romanian/ read])
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Russian Russian] || Final - published April 2018 ([https://creativecommons.org/2018/04/20/russian-translation-of-4-0-published/ read]) || Not started
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Serbian Serbian] || In progress - public comment (Step 4) || In progress - public comment (Step 4)
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Slovak Slovak] || In progress - final review (Step 7) || In progress - public comment period (Step 4)
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Slovenian Slovenian] || Final - published June 2020 ([https://creativecommons.org/2020/06/08/the-cc-license-suite-4-0-and-cc0-are-now-available-in-slovenian/ read]) || Final - published June 2020 ([https://creativecommons.org/2020/06/08/the-cc-license-suite-4-0-and-cc0-are-now-available-in-slovenian/ read])
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Castellano Spanish (Castellano)] || Final - published September 2018 ([https://creativecommons.org/2018/09/11/spanish-translation-of-4-0-now-available-la-traduccion-al-castellano-de-la-version-4-0-de-las-licencias-esta-ahora-disponible/ read]) || Final - published June 2019 ([https://creativecommons.org/2019/06/10/spanish-cc0-translation/ read])
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Swedish Swedish] || Final - published January 2017 ([https://creativecommons.org/2017/01/11/announcing-swedish-translation-4-0-license/ read]) || Final - published January 2017
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Turkish Turkish] || Final - published May 2017 ([https://creativecommons.org/2017/05/25/creative-commons-4-0-license-now-turkish/ read in English] and in [http://creativecommons.org.tr/creative-commons-4-0-lisanslari-simdi-turkce/ Turkish]) || Not started
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Ukrainian Ukrainian] || Final - published June 2015 ([https://creativecommons.org/2015/06/24/ukrainian-translation-of-cc-4-0/ read]) || Not started
|}

[[Category:Legal]]
[[Category:Translation Project]]

Legal Tools Translation

2023-02-07T22:45:45Z

CCID-yuanxiaoxu: /* Translation status of the 4.0 licenses and of CC0 */

=Welcome to the CC Translation Project!=
''Please note this is an evolving project and we welcome feedback.''

This is the main portal for projects translating the suite of six CC licenses and the CC0 Public Domain Dedication. For information on translating CC license deeds, visit [[Translating_CC_Deeds|Translating CC Deeds]]. If you are interested in translating the licenses or other legal tools, please see the [[Legal Code Translation Policy]].

==Translations Generally==
Beginning with version 4.0, CC is supporting official linguistic translations of its six (6) core licenses. '''Please note that translations involve linguistic translation only—they do not adapt the licenses or CC0 to account for local law.''' As of December 2012, CC also supports official translations of CC0 version 1.0.

Please see the [[Legal Code Translation Policy]] for more information on how to start a project to translate CC0 or the CC licenses officially into your local language. CC's policy is to support a single official translation into any particular language, absent a compelling reason otherwise. All legal code translation projects must be approved by Creative Commons in advance; please do not start a legal code translation project without first contacting Creative Commons.

(For version 3.0 of the licenses, CC supports unofficial translations only. These are not official and not suitable for adoption, but are provided solely for information purposes. '''Please do not use translations of the 3.0 international licenses—licensors should not link to or otherwise identify any of the unofficial translations when applying licenses to their materials.''' Those interested in translating CC licenses should join a translation project for the 4.0 licenses. If you would like to read the process for unofficial translations of 3.0, it has been moved [[Unofficial_translation_process_for_3.0|to a separate page]] for historical information.)

==Translation Guide==
As we work with teams on translation projects, we are developing collections of advice and issues to guide future teams' efforts. These include general proofing advice, as well as common errors, and words and phrases that are of key importance or have presented difficulty in each particular legal tool.

*Read the [[Legal tools translation guide]].

<div id="Published_translations"></div>
==Translation status of the 4.0 licenses and of CC0==

{| class="wikitable sortable" style="border-collapse: collapse;" border="1" cellpadding="10"
|-
! style="background-color:#CCCCCC;" | Language (and link to language page) || style="background-color:#CCCCCC;" | 4.0 translation status || style="background-color:#CCCCCC;" | CC0 translation status
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Amharic Amharic] || In progress - final review (Step 7) || Not started
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Arabic Arabic] || Final - published February 2017 ([https://creativecommons.org/2017/02/23/arabic-croatian-translations/ read]) || Not started
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Bahasa_Indonesia Bahasa Indonesia] || Final - published July 2015 ([https://creativecommons.org/2015/08/05/4-0-bahasa-indonesia-translation-and-a-book/ read]) || Not started
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Basque Basque] || Final - published October 2018 ([https://creativecommons.org/2018/10/03/latvian-4-0-and-basque-4-0-and-cc0-translations-now-available/ read]) || Final - published October 2018 ([https://creativecommons.org/2018/10/03/latvian-4-0-and-basque-4-0-and-cc0-translations-now-available/ read])
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Belarusian Belarusian] || Not started || Not started
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Bulgarian Bulgarian] || In progress - public comment period (Step 4) || In progress - public comment period (Step 4)
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Catalan Catalan] || Not started || In progress - review of draft (Step 3)
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Chinese_-_Traditional_and_Simplified Chinese - Traditional and Simplified] || Simplified published in Dec 2019; <br/>Traditional published in January 2020 ([https://creativecommons.org/2020/01/02/cc-licenses-in-simplified-traditional-chinese/ read]) || Final - published March 2018 ([https://creativecommons.org/2018/03/12/cc0-now-available-simplified-traditional-chinese-languages/ read])
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/ChiShona ChiShona] || In Progress - preparing draft (Step 2) || Not started
|-
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Cree Cree] || Not started || Not started
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Croatian Croatian] || Final - published February 2017 ([https://creativecommons.org/2017/02/23/arabic-croatian-translations/ read]) || Final - published July 2020
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Czech Czech] || Final - published June 2019 ([https://creativecommons.org/2019/08/05/new-official-translations-of-cc-legal-tools-published-for-korean-and-czech/ read]) || In progress - public comment period (Step 4)
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Danish Danish] || In progress - public comment period (Step 4) || In progress - public comment period (Step 4)
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Dutch Dutch] || Final - published February 2015 ([https://creativecommons.org/2015/02/25/dutch-translation-of-4-0-published/ read]) || Final - published March 2014 ([https://creativecommons.org/2014/03/18/first-cc0-official-translation-in-dutch/ read])
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Estonian Estonian] || In progress - public comment period (Step 4) || In progress - public comment period (Step 4)
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Finnish Finnish] || Final - published November 2014 ([https://creativecommons.org/2014/11/12/finnish-translation-of-4-0-published/ read])|| Final - published January 2015
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/French French] || Final - published June 2017 ([https://creativecommons.org/2017/06/28/cc-accueille-les-francophones-welcome-cc-4-0-french-license-translations/ read]) || Final - published June 2014 ([https://creativecommons.org/2014/06/27/cc0-official-translation-into-french-published/ read])
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Frisian Frisian] || In progress - Step 9 || Not Started
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/German German] || Final - published January 2017 ([https://creativecommons.org/2017/01/23/german-4-0/ read in English] and [https://netzpolitik.org/2017/offizielle-deutsche-uebersetzung-der-cc-lizenzversion-4-0-ist-da/ in German]) || In progress - final review (Step 7)
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Greek Greek] || Final - published November 2018 ([https://creativecommons.org/2018/12/12/ccs-4-0-license-suite-now-in-greek/ read]) || Final - published November 2019
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Hindi Hindi] || Not started || Not started
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Hungarian Hungarian] || In progress - public comment period (Step 4) || In progress - public comment period (Step 4)
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Italian Italian] || Final - published July 2017 ([https://creativecommons.org/2017/07/31/annuncia-la-traduzione-4-0-della-licenza-italiano/ read]) || Final - published July 2017
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Irish Irish] || In progress - public comment period (Step 4) || In progress - public comment period (Step 4)
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Japanese Japanese] || Final - published July 2015 || Final - published April 2015 ([https://creativecommons.org/2015/05/05/japanese-translation-of-cc0-published/ read])
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Korean Korean] || Final - published August 2019 ([https://creativecommons.org/2019/08/05/new-official-translations-of-cc-legal-tools-published-for-korean-and-czech/ read]) || Final - published August 2019 ([https://creativecommons.org/2019/08/05/new-official-translations-of-cc-legal-tools-published-for-korean-and-czech/ read])
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Latvian Latvian] || Final - published October 2018 ([https://creativecommons.org/2018/10/03/latvian-4-0-and-basque-4-0-and-cc0-translations-now-available/ read]) || Final - published October 2018 ([https://creativecommons.org/2018/10/03/latvian-4-0-and-basque-4-0-and-cc0-translations-now-available/ read])
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Lithuanian Lithuanian] || Final - published June 2018 ([https://creativecommons.org/2018/06/12/lithuanian-translation-of-4-0-available-for-use/ read]) || Final - published June 2018 ([https://creativecommons.org/2018/06/12/lithuanian-translation-of-4-0-available-for-use/ read])
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Malay Malay] || Not started || In progress - preparing draft (Step 2)
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Maltese Maltese] || In progress - public comment period (Step 4) || In progress - public comment period (Step 4)
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/M%C4%81ori Māori] || Final - published July 2015 || Not started
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Norwegian Norwegian] || Final - published December 2014 ([https://creativecommons.org/2014/12/23/norwegian-translation-of-4-0-published/ read]) || Not started
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Polish Polish] || Final - published April 2016 ([https://creativecommons.org/2016/11/15/polish-translation/ read in English] and in [http://creativecommons.pl/2016/11/licencje-4-0-po-polsku/ Polish]) || Final - published October 2015 ([https://creativecommons.org/2015/10/09/cc0-now-available-in-polish-official-translation-published/ read])
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Portuguese Portuguese] || Final - published June 2018 ([https://creativecommons.org/2018/06/26/portuguese-translation-of-4-0-now-available/ read]) || Not started
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Romanian Romanian] || Final - published July 2020 ([https://creativecommons.org/2020/07/15/cc-license-and-cc0-available-in-romanian/ read]) || Final - published July 2020 ([https://creativecommons.org/2020/07/15/cc-license-and-cc0-available-in-romanian/ read])
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Russian Russian] || Final - published April 2018 ([https://creativecommons.org/2018/04/20/russian-translation-of-4-0-published/ read]) || Not started
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Serbian Serbian] || In progress - public comment (Step 4) || In progress - public comment (Step 4)
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Slovak Slovak] || In progress - final review (Step 7) || In progress - public comment period (Step 4)
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Slovenian Slovenian] || Final - published June 2020 ([https://creativecommons.org/2020/06/08/the-cc-license-suite-4-0-and-cc0-are-now-available-in-slovenian/ read]) || Final - published June 2020 ([https://creativecommons.org/2020/06/08/the-cc-license-suite-4-0-and-cc0-are-now-available-in-slovenian/ read])
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Castellano Spanish (Castellano)] || Final - published September 2018 ([https://creativecommons.org/2018/09/11/spanish-translation-of-4-0-now-available-la-traduccion-al-castellano-de-la-version-4-0-de-las-licencias-esta-ahora-disponible/ read]) || Final - published June 2019 ([https://creativecommons.org/2019/06/10/spanish-cc0-translation/ read])
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Swedish Swedish] || Final - published January 2017 ([https://creativecommons.org/2017/01/11/announcing-swedish-translation-4-0-license/ read]) || Final - published January 2017
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Turkish Turkish] || Final - published May 2017 ([https://creativecommons.org/2017/05/25/creative-commons-4-0-license-now-turkish/ read in English] and in [http://creativecommons.org.tr/creative-commons-4-0-lisanslari-simdi-turkce/ Turkish]) || Not started
|-
| [https://wiki.creativecommons.org/wiki/Legal_Tools_Translation/4.0/Ukrainian Ukrainian] || Final - published June 2015 ([https://creativecommons.org/2015/06/24/ukrainian-translation-of-cc-4-0/ read]) || Not started
|}

[[Category:Legal]]
[[Category:Translation Project]]

Legal Code Translation Policy

2023-02-07T22:36:57Z

CCID-yuanxiaoxu: /* Step 10. Publication. */

Creative Commons has established the following Official Legal Code Translation Process and Policy (“Legal Code Translation Policy”) to facilitate adoption and understanding of our licenses as tools for sharing creative works and data. This Legal Code Translation Policy was established as of 2013 October 29 and is updated and revised by Creative Commons in its discretion. Any non-trivial revisions will be logged and dated at the bottom of this page.

'''Watch this explanatory video:'''

[[File:How-to-translate-licenses.png |link=https://www.youtube.com/watch?v=yhHPORrnMns]]

==Overview==
The legal code for the international Creative Commons licenses and for CC0 is designed for use worldwide, without any need for adaptation to local laws. For these tools to reach their fullest potential, CC encourages linguistic translations of the legal codes and deeds into as many languages as possible. This page describes the policy and process for developing official translations of Creative Commons legal code.

The process for developing new translations (each is called a “translation project”) is coordinated and overseen by CC’s legal team in collaboration with the global network team. Creative Commons reserves the exclusive right to approve and host official translations of its legal tools, as well as to modify this process and adjust translation projects at any time. Per our policy, each official translation is hosted at a specified uniform resource indicator on CC’s website. The English original and the official translations will all be treated as equivalents. Translations of CC licenses that are not made in accordance with this policy are unauthorized modifications of our licenses per the [[Modifying_the_CC_licenses#License_Modification_Policy|License Modification Policy]].

==Translation process==
===Step 1. Beginning new translation projects.===
Anyone may initiate a translation project with CC. To express interest, please email legal [at] creativecommons [dot] org identifying the language you would like to coordinate.

Note that CC’s policy is to publish a single, official translation for any given language unless an important reason exists to allow more than one. This mirrors CC’s policy for translations of deeds. Anyone wanting to coordinate translation projects is expected to accommodate and encourage participation of others in the CC community, including from other jurisdictions where the language is spoken. CC will help coordinate this collaboration.

Once a new translation project is begun, CC will update its [[Legal_Tools_Translation|public tracking chart]] and create and populate a language-specific translation page for public tracking, which will be continually updated by CC throughout the translation process.

===Step 2. Preparing the translation draft.===
Please refer to the [[Legal_tools_translation_guide|legal tools translation guide]] while creating your translation because it contains information about common issues that arise when translating the text of the licenses and CC0. When translating the 4.0 license suite, please begin with BY-NC-SA using the worksheet [[Legal_Code_Translation_Policy#Supporting_documents|here]]. Typically, teams begin only with BY-NC-SA and defer creating the other five licenses until after the public comment period. If you are translating CC0, use this [[Legal_Code_Translation_Policy#Supporting_documents|worksheet]].

Once the draft is complete, the translation team should send it to legal[at]creativecommons[dot]org, along with a writeup of the following:
*Explanation of word choice for the following terms:
**For version 4.0:
***Adapted Material
***Copyright and Similar Rights
***Downstream recipients
***Licensed Material
***Share
***ShareAlike
**For CC0:
***Copyright and Related Rights
***Affirmer
***Work
***License
***Waiver
*Description of which concepts were challenging to translate and how decisions were made
*Explanation of variations compared to terminology used on deed translation
*Explanation of variations compared to terminology used in ports of same language
*Names of translators

CC Legal will use this explanation during their Step 3 review, and will add it to language wiki page as part of public documentation of translation process.

===Step 3. Review of draft.===
CC Legal will conduct a review of the draft translation using the following checklist:
#Use Google Translate to read through from top to bottom, looking for glaring errors like commercial uses allowed in NC license, for example.
#Use Google Translate to ensure there are no references to specific local legislation.
#Check that numbering and ordering of sections matches the English.
#Check that cross-references within text are correct.
#Make sure each defined term is in the same order as the English, and uses same capitalization throughout document.
#Go through relevant issues list, checking draft on each point using Google Translate and asking questions of team as needed: 4.0 issues list [[Legal_tools_translation_guide#4.0_license_suite_issues|here]], CC0 issues list [[Legal_tools_translation_guide#CC0_issues|here]]
#Check draft license translation against translations of deed to see if any notable changes in terminology. If yes, ask team for more information.

CC Legal will correspond with the translation team to clarify questions and make changes until a final draft translation is completed. Note that this step will reveal whether there are updates needed for the deed translations. The translation team is responsible for ensuring that the deed is fully translated. For help translating the deeds, see the instructions [[Translating_CC_Deeds|here]].

===Step 4. Public comment period.===
The public comment period is designed to ensure the highest quality linguistic translations possible. The translation team posts the draft on the CC wiki and in appropriate channels for public comment and feedback for a reasonable period of time (typically about 30-45 days, but may be shortened or extended if circumstances warrant). We encourage teams to seek as much input as possible, including by reaching out directly to local experts where possible.

At the conclusion of the public comment period, the translation team sends CC Legal a written summary of input received and how issues were resolved, along with the revised translation. CC Legal reviews the public comment summary from the translation team and asks questions as needed.

===Step 5. Creating the rest of the license suite.===
Note that this step only applies to translation of the version 4.0 CC license suite. Once all open issues are resolved with CC Legal after public comment, the translation team should create the other 5 licenses in the suite. For help in this process, refer to this [https://wiki.creativecommons.org/images/d/d1/Building_the_4.0_Suite.pdf guide]. Please consult CC Legal if you have any questions about word choices or anything else when creating the rest of the suite.

===Step 6. Readying files for staging server.===
At this point, the team converts the file(s) to HTML and sends the HTML file(s) to legal [at] creativecommons [dot] org. CC puts the file(s) on the staging server and sends the link(s) to the translation team.

''NOTE: To create the HTML files, we recommend using the English legal code pages - [https://creativecommons.org/licenses/by/4.0/legalcode https://creativecommons.org/licenses/by/4.0/legalcode] et. al. - as templates for your own. You can access the HTML page for each license in Github, where the files are stored with comments.

*BY-NC-SA is [https://github.com/creativecommons/creativecommons.org/blob/master/docroot/legalcode/by-nc-sa_4.0.html here]
*BY is [https://github.com/creativecommons/creativecommons.org/blob/master/docroot/legalcode/by_4.0.html here]
*BY-SA is [https://github.com/creativecommons/creativecommons.org/blob/master/docroot/legalcode/by-sa_4.0.html here]
*BY-NC-ND is [https://github.com/creativecommons/creativecommons.org/blob/master/docroot/legalcode/by-nc-nd_4.0.html here]
*BY-NC is [https://github.com/creativecommons/creativecommons.org/blob/master/docroot/legalcode/by-nc_4.0.html here]
*BY-ND is [https://github.com/creativecommons/creativecommons.org/blob/master/docroot/legalcode/by-nd_4.0.html here]
*CC0 is [https://github.com/creativecommons/creativecommons.org/blob/master/docroot/legalcode/zero_1.0.html here]

Copy and paste the appropriate license text into a file using a text editor or HTML editor. Then, copy and paste your appropriate translation text over the English text, being careful not to copy over the existing HTML tags, and re-check the code to ensure that there are no mistakes. Please ensure that all the XHTML files are saved using UTF-8 encoding, which generally will be the default. Then save each file separately according to the following convention:''
*''CC0'':
** ''zero_1.0_[language code].html''

''(For example, "zero_1.0_fr.html" would be the naming for the French translation.)''

*''4.0''
**''by_4.0_[language code].html''
**''by-sa_4.0_[language code].html''
**'' [...]''

===Step 7. Final review.===

The translation team and CC Legal conduct a final review of all files on the staging server. This review should involve a check of both the substance and formatting of the files.

During this final review, CC Legal will use the following checklist:
#Use Google Translate to read through from top to bottom, looking for glaring errors like commercial uses allowed in NC license, for example. [Note: in the case of 4.0, this may be the first time the translations of licenses other than BY-NC-SA have been reviewed, so pay special attention to the changes made to those files.]
#Pay special attention to the license titles - are they correct and consistent throughout each file? Compare to titles on license deeds.
#Check that formatting appears correct as compared to English (same number of provisions, identical section numbering, bold font)
#Check that language list contains all published translations, including English
#Check all links in the files
#Check that deeds are fully translated
#For version 4.0, cut and paste each file into a Word doc and run the following comparisons:
#*BY-NC-SA to BY; compare to [https://wiki.creativecommons.org/images/c/c4/Making_BY_%28comparison%29.pdf this]
#*BY-NC-SA to BY-SA; compare to [https://wiki.creativecommons.org/images/6/64/Making_BY-SA_%28comparison%29.pdf this]
#*BY-NC-SA to BY-NC; compare to [https://wiki.creativecommons.org/images/6/6f/Making_BY-NC_%28comparison%29.pdf this]
#*BY-NC-SA to BY-ND; compare to [https://wiki.creativecommons.org/images/a/a2/Making_BY-ND_%28comparison%29.pdf this]
#*BY-NC-SA to BY-NC-ND; compare to [https://wiki.creativecommons.org/images/7/70/Making_BY-NC-ND_%28comparison%29.pdf this]

This stage continues until all identified problems are resolved.

===Step 8. General Counsel sign-off.===
Once the translation team and CC have signed off on all files, CC Legal sends the file(s) to General Counsel for final sign-off. CC Legal will coordinate details for blog post announcement with translation team at this point.

===Step 9. Publication.===
CC will alert the translation team and publish announcement on the CC blog and social media. CC Legal will update wiki tracking sheet with publication dates. Translation team should update Transifex so that deeds link to published translation rather than English legal code.

==Key Resources==
* [[Legal tools translation guide]]
* [[Media:Building_the_4.0_Suite.pdf|Building the 4.0 Suite (.pdf)]]
* [[Media:Making_BY_(comparison).pdf|Making the BY license (comparison) (.pdf)]]
* [[Media:Making_BY-SA_(comparison).pdf|Making the BY-SA license (comparison) (.pdf)]]
* [[Media:Making_BY-NC_(comparison).pdf|Making the BY-NC license (comparison) (.pdf)]]
* [[Media:Making_BY-ND_(comparison).pdf|Making the BY-ND license (comparison) (.pdf)]]
* [[Media:Making_BY-NC-ND_(comparison).pdf|Making the BY-NC-ND license (comparison) (.pdf)]]
* 4.0 translation worksheet: [https://docs.google.com/document/d/1Vq6b89z6HWP1KZ66FNvx9E1GTeyAguPKk_zb4jXg4u8/ Google Doc], [[Media:4.0_translation_worksheet_(BY-NC-SA)(Feb_2015).odt|.odt]], [[Media:4.0_translation_worksheet_(BY-NC-SA)(Feb_2015).docx|.docx]], [[Media:4.0_translation_worksheet_(BY-NC-SA)(Feb_2015).pdf|.pdf]] (updated 2016 November 23)
* CC0 translation worksheet: [https://docs.google.com/document/d/12bmP4guaewK2U0eGQIFd-2N5XVlpB1rGULfxHthhODA/ Google Doc], [[Media:CC0_translation_worksheet.odt|.odt]], [[Media:CC0_translation_worksheet.docx|.docx]], [[Media:CC0_translation_worksheet.pdf|.pdf]] (updated 2016 November 23)

==Changelog==
* 2019 September 17: Moved formatting check to Step 7 since that is when bold and other formatting is added; changed instructions for converting to HTML
* 2019 September 3: Revised process to better reflect current practice in terms of who and how translations are initiated, and added far more detail about different steps in the process.
* 2018 May 26: As of January 2018, the Affiliate Network transitioned to a Global Network, where everyone - individuals and institutions - are welcome. This policy reflects the new structure.
* 2017 March 14: Moved "Creating the files" from [[Legal tools translation guide]] to this page
* 2016 November 21: Removed the obligation to send the translation proposal using the forms
* 2016 November 4: Added detailed new steps to the translation process
* 2015 April 17: Clarification that unofficial translations violate License Modification Policy
* 2015 February 4: Change in supplemental material requirements, added CC0 translation worksheet
* 2014 February 4: Additional supplemental material requirements, new version of internal checklist posted
* 2014 January 24: More detailed summary.
* 2013 October 29: Policy established.

[[Category:Translation Project]]

Legal Code Translation Policy

2023-02-07T22:36:35Z

CCID-yuanxiaoxu:

Creative Commons has established the following Official Legal Code Translation Process and Policy (“Legal Code Translation Policy”) to facilitate adoption and understanding of our licenses as tools for sharing creative works and data. This Legal Code Translation Policy was established as of 2013 October 29 and is updated and revised by Creative Commons in its discretion. Any non-trivial revisions will be logged and dated at the bottom of this page.

'''Watch this explanatory video:'''

[[File:How-to-translate-licenses.png |link=https://www.youtube.com/watch?v=yhHPORrnMns]]

==Overview==
The legal code for the international Creative Commons licenses and for CC0 is designed for use worldwide, without any need for adaptation to local laws. For these tools to reach their fullest potential, CC encourages linguistic translations of the legal codes and deeds into as many languages as possible. This page describes the policy and process for developing official translations of Creative Commons legal code.

The process for developing new translations (each is called a “translation project”) is coordinated and overseen by CC’s legal team in collaboration with the global network team. Creative Commons reserves the exclusive right to approve and host official translations of its legal tools, as well as to modify this process and adjust translation projects at any time. Per our policy, each official translation is hosted at a specified uniform resource indicator on CC’s website. The English original and the official translations will all be treated as equivalents. Translations of CC licenses that are not made in accordance with this policy are unauthorized modifications of our licenses per the [[Modifying_the_CC_licenses#License_Modification_Policy|License Modification Policy]].

==Translation process==
===Step 1. Beginning new translation projects.===
Anyone may initiate a translation project with CC. To express interest, please email legal [at] creativecommons [dot] org identifying the language you would like to coordinate.

Note that CC’s policy is to publish a single, official translation for any given language unless an important reason exists to allow more than one. This mirrors CC’s policy for translations of deeds. Anyone wanting to coordinate translation projects is expected to accommodate and encourage participation of others in the CC community, including from other jurisdictions where the language is spoken. CC will help coordinate this collaboration.

Once a new translation project is begun, CC will update its [[Legal_Tools_Translation|public tracking chart]] and create and populate a language-specific translation page for public tracking, which will be continually updated by CC throughout the translation process.

===Step 2. Preparing the translation draft.===
Please refer to the [[Legal_tools_translation_guide|legal tools translation guide]] while creating your translation because it contains information about common issues that arise when translating the text of the licenses and CC0. When translating the 4.0 license suite, please begin with BY-NC-SA using the worksheet [[Legal_Code_Translation_Policy#Supporting_documents|here]]. Typically, teams begin only with BY-NC-SA and defer creating the other five licenses until after the public comment period. If you are translating CC0, use this [[Legal_Code_Translation_Policy#Supporting_documents|worksheet]].

Once the draft is complete, the translation team should send it to legal[at]creativecommons[dot]org, along with a writeup of the following:
*Explanation of word choice for the following terms:
**For version 4.0:
***Adapted Material
***Copyright and Similar Rights
***Downstream recipients
***Licensed Material
***Share
***ShareAlike
**For CC0:
***Copyright and Related Rights
***Affirmer
***Work
***License
***Waiver
*Description of which concepts were challenging to translate and how decisions were made
*Explanation of variations compared to terminology used on deed translation
*Explanation of variations compared to terminology used in ports of same language
*Names of translators

CC Legal will use this explanation during their Step 3 review, and will add it to language wiki page as part of public documentation of translation process.

===Step 3. Review of draft.===
CC Legal will conduct a review of the draft translation using the following checklist:
#Use Google Translate to read through from top to bottom, looking for glaring errors like commercial uses allowed in NC license, for example.
#Use Google Translate to ensure there are no references to specific local legislation.
#Check that numbering and ordering of sections matches the English.
#Check that cross-references within text are correct.
#Make sure each defined term is in the same order as the English, and uses same capitalization throughout document.
#Go through relevant issues list, checking draft on each point using Google Translate and asking questions of team as needed: 4.0 issues list [[Legal_tools_translation_guide#4.0_license_suite_issues|here]], CC0 issues list [[Legal_tools_translation_guide#CC0_issues|here]]
#Check draft license translation against translations of deed to see if any notable changes in terminology. If yes, ask team for more information.

CC Legal will correspond with the translation team to clarify questions and make changes until a final draft translation is completed. Note that this step will reveal whether there are updates needed for the deed translations. The translation team is responsible for ensuring that the deed is fully translated. For help translating the deeds, see the instructions [[Translating_CC_Deeds|here]].

===Step 4. Public comment period.===
The public comment period is designed to ensure the highest quality linguistic translations possible. The translation team posts the draft on the CC wiki and in appropriate channels for public comment and feedback for a reasonable period of time (typically about 30-45 days, but may be shortened or extended if circumstances warrant). We encourage teams to seek as much input as possible, including by reaching out directly to local experts where possible.

At the conclusion of the public comment period, the translation team sends CC Legal a written summary of input received and how issues were resolved, along with the revised translation. CC Legal reviews the public comment summary from the translation team and asks questions as needed.

===Step 5. Creating the rest of the license suite.===
Note that this step only applies to translation of the version 4.0 CC license suite. Once all open issues are resolved with CC Legal after public comment, the translation team should create the other 5 licenses in the suite. For help in this process, refer to this [https://wiki.creativecommons.org/images/d/d1/Building_the_4.0_Suite.pdf guide]. Please consult CC Legal if you have any questions about word choices or anything else when creating the rest of the suite.

===Step 6. Readying files for staging server.===
At this point, the team converts the file(s) to HTML and sends the HTML file(s) to legal [at] creativecommons [dot] org. CC puts the file(s) on the staging server and sends the link(s) to the translation team.

''NOTE: To create the HTML files, we recommend using the English legal code pages - [https://creativecommons.org/licenses/by/4.0/legalcode https://creativecommons.org/licenses/by/4.0/legalcode] et. al. - as templates for your own. You can access the HTML page for each license in Github, where the files are stored with comments.

*BY-NC-SA is [https://github.com/creativecommons/creativecommons.org/blob/master/docroot/legalcode/by-nc-sa_4.0.html here]
*BY is [https://github.com/creativecommons/creativecommons.org/blob/master/docroot/legalcode/by_4.0.html here]
*BY-SA is [https://github.com/creativecommons/creativecommons.org/blob/master/docroot/legalcode/by-sa_4.0.html here]
*BY-NC-ND is [https://github.com/creativecommons/creativecommons.org/blob/master/docroot/legalcode/by-nc-nd_4.0.html here]
*BY-NC is [https://github.com/creativecommons/creativecommons.org/blob/master/docroot/legalcode/by-nc_4.0.html here]
*BY-ND is [https://github.com/creativecommons/creativecommons.org/blob/master/docroot/legalcode/by-nd_4.0.html here]
*CC0 is [https://github.com/creativecommons/creativecommons.org/blob/master/docroot/legalcode/zero_1.0.html here]

Copy and paste the appropriate license text into a file using a text editor or HTML editor. Then, copy and paste your appropriate translation text over the English text, being careful not to copy over the existing HTML tags, and re-check the code to ensure that there are no mistakes. Please ensure that all the XHTML files are saved using UTF-8 encoding, which generally will be the default. Then save each file separately according to the following convention:''
*''CC0'':
** ''zero_1.0_[language code].html''

''(For example, "zero_1.0_fr.html" would be the naming for the French translation.)''

*''4.0''
**''by_4.0_[language code].html''
**''by-sa_4.0_[language code].html''
**'' [...]''

===Step 7. Final review.===

The translation team and CC Legal conduct a final review of all files on the staging server. This review should involve a check of both the substance and formatting of the files.

During this final review, CC Legal will use the following checklist:
#Use Google Translate to read through from top to bottom, looking for glaring errors like commercial uses allowed in NC license, for example. [Note: in the case of 4.0, this may be the first time the translations of licenses other than BY-NC-SA have been reviewed, so pay special attention to the changes made to those files.]
#Pay special attention to the license titles - are they correct and consistent throughout each file? Compare to titles on license deeds.
#Check that formatting appears correct as compared to English (same number of provisions, identical section numbering, bold font)
#Check that language list contains all published translations, including English
#Check all links in the files
#Check that deeds are fully translated
#For version 4.0, cut and paste each file into a Word doc and run the following comparisons:
#*BY-NC-SA to BY; compare to [https://wiki.creativecommons.org/images/c/c4/Making_BY_%28comparison%29.pdf this]
#*BY-NC-SA to BY-SA; compare to [https://wiki.creativecommons.org/images/6/64/Making_BY-SA_%28comparison%29.pdf this]
#*BY-NC-SA to BY-NC; compare to [https://wiki.creativecommons.org/images/6/6f/Making_BY-NC_%28comparison%29.pdf this]
#*BY-NC-SA to BY-ND; compare to [https://wiki.creativecommons.org/images/a/a2/Making_BY-ND_%28comparison%29.pdf this]
#*BY-NC-SA to BY-NC-ND; compare to [https://wiki.creativecommons.org/images/7/70/Making_BY-NC-ND_%28comparison%29.pdf this]

This stage continues until all identified problems are resolved.

===Step 8. General Counsel sign-off.===
Once the translation team and CC have signed off on all files, CC Legal sends the file(s) to General Counsel for final sign-off. CC Legal will coordinate details for blog post announcement with translation team at this point.

===Step 10. Publication.===
Once the pull request is merged by the tech team, CC will alert the translation team and publish announcement on the CC blog and social media. CC Legal will update wiki tracking sheet with publication dates. Translation team should update Transifex so that deeds link to published translation rather than English legal code.

==Key Resources==
* [[Legal tools translation guide]]
* [[Media:Building_the_4.0_Suite.pdf|Building the 4.0 Suite (.pdf)]]
* [[Media:Making_BY_(comparison).pdf|Making the BY license (comparison) (.pdf)]]
* [[Media:Making_BY-SA_(comparison).pdf|Making the BY-SA license (comparison) (.pdf)]]
* [[Media:Making_BY-NC_(comparison).pdf|Making the BY-NC license (comparison) (.pdf)]]
* [[Media:Making_BY-ND_(comparison).pdf|Making the BY-ND license (comparison) (.pdf)]]
* [[Media:Making_BY-NC-ND_(comparison).pdf|Making the BY-NC-ND license (comparison) (.pdf)]]
* 4.0 translation worksheet: [https://docs.google.com/document/d/1Vq6b89z6HWP1KZ66FNvx9E1GTeyAguPKk_zb4jXg4u8/ Google Doc], [[Media:4.0_translation_worksheet_(BY-NC-SA)(Feb_2015).odt|.odt]], [[Media:4.0_translation_worksheet_(BY-NC-SA)(Feb_2015).docx|.docx]], [[Media:4.0_translation_worksheet_(BY-NC-SA)(Feb_2015).pdf|.pdf]] (updated 2016 November 23)
* CC0 translation worksheet: [https://docs.google.com/document/d/12bmP4guaewK2U0eGQIFd-2N5XVlpB1rGULfxHthhODA/ Google Doc], [[Media:CC0_translation_worksheet.odt|.odt]], [[Media:CC0_translation_worksheet.docx|.docx]], [[Media:CC0_translation_worksheet.pdf|.pdf]] (updated 2016 November 23)

==Changelog==
* 2019 September 17: Moved formatting check to Step 7 since that is when bold and other formatting is added; changed instructions for converting to HTML
* 2019 September 3: Revised process to better reflect current practice in terms of who and how translations are initiated, and added far more detail about different steps in the process.
* 2018 May 26: As of January 2018, the Affiliate Network transitioned to a Global Network, where everyone - individuals and institutions - are welcome. This policy reflects the new structure.
* 2017 March 14: Moved "Creating the files" from [[Legal tools translation guide]] to this page
* 2016 November 21: Removed the obligation to send the translation proposal using the forms
* 2016 November 4: Added detailed new steps to the translation process
* 2015 April 17: Clarification that unofficial translations violate License Modification Policy
* 2015 February 4: Change in supplemental material requirements, added CC0 translation worksheet
* 2014 February 4: Additional supplemental material requirements, new version of internal checklist posted
* 2014 January 24: More detailed summary.
* 2013 October 29: Policy established.

[[Category:Translation Project]]

Company of Biologists - Development

2023-01-13T23:31:02Z

CCID-yuanxiaoxu:

{{Organization
|Mainurl=https://journals.biologists.com/dev
|License short name=copyright
|Open or Free Statement=no
|Organization Type=research organization
|Affiliation=Company of Biologists
|Tag=research,journal,cellular and molecular development
|Status=good
|License_provider=
}}

Recommended practices for attribution

2022-12-15T21:04:44Z

CCID-yuanxiaoxu: /* Other guides to attribution */

You can use CC-licensed materials as long as you follow the license conditions. One condition of all CC licenses is attribution: crediting the author and noting the source and the license. Generally speaking, attribution must reasonably include all relevant information supplied by the licensor. Because each use case is different, you can decide what form of attribution is most suitable for your specific situation. The following examples are intended to illustrate what typical prudent practices look like. We expect community norms and expectations to evolve with time, and will adapt this guide accordingly.
In addition to attribution, there are also [https://wiki.creativecommons.org/wiki/Considerations_for_licensors_and_licensees#Considerations_for_licensees|other things to consider as a licensor or a licensee]. If you are a licensor and would like to learn how to license your own material, take a look at [https://wiki.creativecommons.org/wiki/Marking_your_work_with_a_CC_license our guide on how to mark your work with a CC license].

==Basic components of attribution==

[[File:19th_century_tassel_from_Smithsonian.jpeg|290px|left]]

Whenever you are reusing CC licensed works, we recommend that the attribution include the '''T'''itle, '''A'''uthor, '''S'''ource, and '''L'''icense. This is true whether you’re sharing the work as-is or if you have made an adaptation. To remember these attribution elements, it’s helpful to think of the acronym: '''TASL'''.

Let’s now go through '''TASL''' — we will explain each element in more detail:

'''Title''': What is the name of the work?

:If a title was provided for the work, include it as a part of the attribution. Sometimes a title is not provided; in that case, there’s no need to mention the title.

:The inclusion of title is a requirement of all CC licenses version 3.0 or earlier, and it is optional for the 4.0 suites. See [https://wiki.creativecommons.org/wiki/Recommended_practices_for_attribution#License_details License details].

'''Author''': Who allows you to use the work?

:We often use “author” as a shorthand when we are, legally speaking, referring to the “licensor” (a.k.a., the “copyright holder” or “rightsholder”). This is because, in most CC-licensed works, the licensor is the same person or entity as the author. When an author is licensing their work under a CC license, and has made their name available, include the author’s name as a component in your attribution. Sometimes, the licensor may want you to give credit to some other entity, like a company or institution, or the licensor may want to be credited by a pseudonym instead of their real name. In rare cases, the licensor may not want to be attributed at all. In all of these cases, do what the licensor requests.

:Sometimes, the author will also provide a copyright notice, which consists of the copyright symbol, year of publication, and the name of the author/licensor. Include the copyright notice as a part of your attribution if such information is provided.

'''Source''': Where can people find the work?

:Please make it possible for future users to find the source of the material by including a URL or hyperlink where the work resides. This often is where you found the work. If you found it somewhere other than the original site, try to include information about the original site where the work was first shared publicly. It is also better to use the original URL instead of a shortened link, whether you are hyperlinking or printing out the entire URL.

'''License''': How can you use the work?

:You must specify which CC license was applied to the work you are reusing. Each of the six different CC licenses come with distinct requirements for re-use. We recommend that you name and provide a link to the license, e.g., [http://creativecommons.org/licenses/by/4.0 CC BY 4.0] (http://creativecommons.org/licenses/by/4.0) for a work licensed under CC BY 4.0.

:Consider also including the “disclaimer of warranties,” which clarifies that the author makes no representations or warranties about the non-infringement or absence of other defects concerning the CC-licensed work. In plain English, this means that the users will use the work at their own risk.

:To sum up, if the licensor has provided any information related to TASL, consider including them in your attribution. We also recommend providing links to the Title, Author, Source, and License, where possible, so future users can easily access the information they need on a work and the license terms.
<hr>
===Reasonable attribution===

The CC licenses ask you to be reasonable:

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 90%;">You may satisfy the attribution requirement in any reasonable manner based on the medium, means and context in which the Licensed Material is used. For example, it may be reasonable to satisfy some or all of the conditions by retaining a copyright notice, or by providing a URI or hyperlink associated with the Licensed Material, if the copyright notice or webpage includes some or all of the required information.</div>

There is no single best or correct way of attribution, as long as your attribution is reasonable and suited to the medium you're working with.
<hr>

===License details===

If you have any doubts or questions, you can read the complete attribution requirements which are spelled out in detail in the legal code of every CC license, eg. http://creativecommons.org/licenses/by/4.0/legalcode This [[License_Versions#Detailed_attribution_comparison_chart|chart compares the detailed requirements across all versions of CC licenses.]]

==Examples of attribution==

We will now look at some examples in different media.

===Attributing an image===

Here is a photo. Below, we will go over some good and bad examples of how people might attribute it.

[[File:8256206923_c77e85319e_n.jpg]]
<hr>

====This is a great attribution====
<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">
"[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Creative Commons 10th Birthday Celebration San Francisco]" by [http://www.flickr.com/photos/sixteenmilesofstring/ Timothy Vollmer] is licensed under [http://creativecommons.org/licenses/by/4.0/ CC BY 4.0]</div>

''Let’s go through TASL:''
:'''T'''itle? "Creative Commons 10th Birthday Celebration San Francisco"
:'''A'''uthor? "[http://www.flickr.com/photos/sixteenmilesofstring/ Timothy Vollmer]" - linked to his profile page
:'''S'''ource? "[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Creative Commons 10th Birthday Celebration San Francisco]" - linked to original Flickr page
:'''L'''icense? "[http://creativecommons.org/licenses/by/4.0/ CC BY 4.0]" - linked to license deed

Most importantly, this attribution reasonably includes all the relevant information provided by the author.
<hr>

====This is a pretty good attribution====

<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Photo] by Timothy Vollmer/ [http://creativecommons.org/licenses/by/2.0/ CC BY]</div>

''Let’s go through TASL:''
:'''T'''itle? Title is not noted but at least the source is linked.
:'''A'''uthor? "Timothy Vollmer"
:'''S'''ource? "[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Photo]" - linked to original Flickr page
:'''L'''icense? "[http://creativecommons.org/licenses/by/4.0/ CC BY]" - linked to license deed

As you see, a good attribution includes all the essential '''TASL''' elements, even though they may not mirror the format of credit the author has requested.
<hr>

==== This is an incorrect attribution====
<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">Photo: Creative Commons</div>

''Let’s go through TASL'':
:'''T'''itle? Title of the image is not noted
:'''A'''uthor? Author is not noted (It is a common mistake to attribute CC-licensed photos to CC, but Creative Commons is not the author!)
:'''S'''ource? No link to the original source
:'''L'''icense? There is no mention of a license nor a link to the license. "Creative Commons" is the name of an organization; it does not equate to any of the licenses maintained by the Creative Commons.
<hr>

====This is a great attribution for an image you modified slightly====
:[[File:Cropped_tvol_cupcake.png|300px]]

<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">"[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Creative Commons 10th Birthday Celebration San Francisco]" by [http://www.flickr.com/photos/sixteenmilesofstring/ Timothy Vollmer], used under [http://creativecommons.org/licenses/by/4.0/ CC BY 4.0] / Cropped from original</div>

Here, information on '''T'''itle, '''A'''uthor, '''S'''ource, and '''L'''icense are all included as requested by the author. The slight modification is also noted and briefly described.

Note if the modification changes the work’s meaning in a way that would be considered creative — that is, not a purely mechanical change or a simple crop/excerpt that keeps the original message undistorted, it would be considered creating a new adaptation of the original work. You cannot rely on a CC license that does not allow adaptation (e.g., CC BY-ND or CC BY-NC-ND) when making such modifications.

<hr>

====This is a great attribution for when you have created an adaptation====

:[[File:8256206923_c77e85319e_n_90fied.jpg|300px]]

<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">This work, "90fied", is adapted from "[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Creative Commons 10th Birthday Celebration San Francisco]" by [http://www.flickr.com/photos/sixteenmilesofstring/ Timothy Vollmer], used under [http://creativecommons.org/licenses/by/4.0/ CC BY 4.0]. "90fied" is licensed under [http://creativecommons.org/licenses/by/4.0/ CC BY 4.0] by [Your name here].</div>

''Let’s go through TASL:''

Original '''T'''itle, '''A'''uthor, '''S'''ource, and '''L'''icense are all noted.

The original work is referenced and the fact that it is an adaptation is also noted, so viewers can see what has changed.

The author and other attribution information for the new adapted work is also noted.

Note: If you're at a point where you are licensing works that are adaptations, go to [[Marking your work with a CC license]].
<hr>

===Attributing music===

====When you incorporate music in an audio or video recording====
Music (both the underlying composition and the sound recordings) — such as a song, or a recording of natural sounds — can be attributed within the audio/video, and in the description text of the audio/video. How to attribute a CC licensed music in an audio or video recording will largely depend on what is reasonable for a chosen medium and platform.

Caution: Licenses with “ND” do not allow for adaptations. Your use of CC-licensed music is often an adaptation!

It is considered adaptation if you incorporate CC-licensed music into your work in a way that the CC-licensed music can no longer be seen as a stand-alone piece. For example, if you are using a song as background music in a podcast or in a video, it is considered an adaptation of the song.

Keep in mind that CC BY-ND and CC BY-NC-ND do not allow adaptations (although you may be authorized by law to do so, such as under a users’ right like fair use, or you may ask for the author’s permission independent of the CC license).
<hr>

[[File:Smithsonian_music_stand.jpeg|left|250px]]

=====This is a great attribution of background music in a podcast or a video=====
When reasonable to do so, we recommend that you include attribution both in the description box and in the podcast recording or the video recording itself.

If you are using the following song in a podcast: ‘Day Bird’ by Broke for Free ([https://brokeforfree.com brokeforfree.com]), this would be a great way to provide attribution (which you can see in [https://soundcloud.com/wearecc/open-minds-podcast-catherine-stihler-ceo-of-creative-commons the Creative Commons podcast]) —

:At the end of the podcast audio recording, the host says:
:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 90%;">Special thanks to the musician Broke for Free, whose track “Day Bird” you heard at the beginning of this episode and you are listening to right now. It's under the Creative Commons Attribution License, meaning it's free for anyone to use. You can find it at the Free Music Archive—freemusicarchive.org</div>

:In the description box, the information text reads:
:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 90%;">Theme music: “Day Bird” by Broke for Free ([https://brokeforfree.com brokeforfree.com]). Available for use under the CC BY 3.0 license ([https://creativecommons.org/licenses/by/3.0/ creativecommons.org/licenses/by/3.0/]), at [https://freemusicarchive.org/music/Broke_For_Free/Directionless_EP/Broke_For_Free_-_Directionless_EP_-_03_Day_Bird|the Free Music Archive].</div>

''Let’s go through TASL:''

:'''T'''itle? Both the recording and the description box include the title of the work, “Day Bird”

:'''A'''uthor? "Broke for Free," again, noted both in the recording and in the description box

:'''S'''ource? Both the author’s page and the archive’s page are included with links

:'''L'''icense? "CC BY 3.0" — linked to license deed

You cannot talk over, or remix, music licensed under CC BY-ND or CC BY-NC-ND.

<hr>

=====This is a bad attribution of background music in a podcast or a video=====

A bad attribution is one where you do not provide enough information for a user to find the music you are using. The following is a bad attribution for the same song:

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">No attribution is included in the podcast recording or the video itself.

In the description box, it says: “ Creative Commons music.”</div>

''Let’s go through TASL:''

:'''T'''itle? Title is not noted

:'''A'''uthor? Author is not noted

:'''S'''ource? Source is not noted; users cannot find the specific song used in the podcast

:'''L'''icense? No information on the CC license

The attribution information is not sufficient for people to find the song you have re-used.
<hr>

====When you are not adding new elements to the music====
When you re-use music without adding new elements to it, you are not making an adaptation. In that case, you can rely on any of the CC licenses, including CC BY-ND and CC BY-NC-ND. We recommend providing attribution information in writing.

[[File:Wiki_page_attributing_night_owl.png|400px]]

On [https://commons.wikimedia.org/wiki/File:Broke_For_Free_-_01_-_Night_Owl.ogg this Wikipedia page], you can see an example of great attribution for the sharing another soundtrack, “Night Owl” by Broke for Free, when it’s without adaptation.

''Let’s go through TASL:''

'''T'''itle? Title of the work, “Night Owl,” is noted

'''A'''uthor? "Broke for Free," noted and linked to the author’s webpage

'''S'''ource? A link is provided for the source

'''L'''icense? "CC BY 3.0" — linked to license deed
<hr>

===Attributing text===
Let’s take [https://github.com/getify/You-Dont-Know-JS ''You Don't Know JS Yet'' (2nd Edition)] as an example, and go over what your attribution may look like if you reuse the book series. The information under the “License & Copyright” section looks like this on the webpage where the book series was originally shared:
:[[File:attributing_You_Don't_Know_JS_Yet_(2nd_Edition).png|200px]]

We recommend that you retain all the information provided by the author of the book series when it is reasonable for you to do so. For example, if you are distributing digital copies or excerpts of the book series in a free seminar, or using parts of the book in a free online course or presentation, the attribution will likely look something like this:

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">This chapter is from “[https://github.com/getify/You-Dont-Know-JS You Don't Know JS Yet (2nd Edition)]” by [https://github.com/getify Kyle Simpson]. The book is licensed under the [https://creativecommons.org/licenses/by-nc-nd/4.0/ CC BY-NC-ND 4.0 license]. © 2019-2022 Kyle Simpson.</div>

On the other hand, if you are distributing hard copies of the book series or excerpts from the book series, instead of using hyperlinks, you may wish to include the links so it’s easier for users to locate the original source of the book, the author, and the CC license:

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">This chapter is from “You Don't Know JS Yet (2nd Edition)” (https://github.com/getify/You-Dont-Know-JS) by Kyle Simpson (https://github.com/getify). The book is licensed under the CC BY-NC-ND 4.0 license (https://creativecommons.org/licenses/by-nc-nd/4.0/). © 2019-2022 Kyle Simpson.</div>

Note that the CC BY-NC-ND license includes the NoDerivatives requirement, which indicates that no adaptations are allowed. You cannot make any adaptations relying on the CC BY-NC-CD license the author chose for the book. If you would like to make a translation of the book, for example, you will need to ask the author for permission first.

The CC BY-NC-ND license also includes the NonCommercial requirement. To learn more, take a look at [https://en.wikipedia.org/wiki/Creative_Commons_NonCommercial_license our guide about the NonCommercial licenses].
<hr>

=== Attributing materials from multiple sources ===

:[[File:Saylor_marking_example.jpg]]

''Let’s go through TASL:''

:'''T'''itle? Specific works are named, e.g., "Box-and-whisker Plots"

:'''A'''uthor? Different authors noted for the different works

:'''S'''ource? Original materials are linked for each work

:'''L'''icense? The different licenses (Creative Commons Attribution for Collaborative Statistics and Creative Commons Attribution-Noncommercial-ShareAlike for the Khan Academy video) are spelled out and linked for each work

:Lastly, it is clear which attribution belongs to which work.

You can visit the [http://www.saylor.org/courses/ma121/ Saylor.org Introduction to Statistics course page] to see how they marked it up directly.
<hr>

=== Publishing attribution on a separate web page ===
As stated above, recommended attribution depends on the medium you're working with. For media such as offline materials, video, audio, and images, consider publishing a web page with attribution information. For example, on a webpage featuring your audio recording, provide a credit list of material you used that adheres to best practices above. Doing so allows not only your material, but the materials you attribute, to be found by search engines and other web discovery tools. If possible within the medium, make the Author, Source, and License links the user can follow.

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">'''Example:'''<br>This video features the song [http://ccmixter.org/media/files/victor/6374 "Desaprendere (Treatment)"] by [http://fourstones.net/ fourstones], available under a Creative Commons [http://creativecommons.org/licenses/by-nc/2.5/ Attribution-Noncommercial 2.5 license].</div>

<hr>

==Citing public domain materials==
Although attribution is not a legal obligation under [https://creativecommons.org/share-your-work/public-domain/cc0/ CC0 dedication]’s or [https://creativecommons.org/share-your-work/public-domain/pdm/ CC Public Domain Mark]’s licensing terms, we recommend that you consider including information about the hosting institution for public domain materials when it is reasonable to do so. Citing public domain works in this way not only encourages institutions to digitize and share more public domain materials in their physical collections, but also empowers users to easily locate the original source.

Here is an example of citing the source of a public domain image. The following public domain image is digitized and hosted by the Rijksmuseum (the national museum of the Netherlands). The Rijksmuseum has applied a CC0 dedication to the image.

:[[File:Attributing_the_milkmaid.png|300px]]

You may provide credit in the following format:

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">“[http://hdl.handle.net/10934/RM0001.COLLECT.6417 The Milkmaid]” by Vermeer. The Rijksmuseum collection. The image is dedicated to the public domain under [https://creativecommons.org/share-your-work/public-domain/cc0/ CC0]. </div>

In most cases, people credit the source regardless of the work’s copyright status. Especially in an academic setting, providing source information about other people’s works has long been considered crucial to academic integrity. Copyright cannot be the only checkbox when deciding whether a source will be credited. You can learn more about [https://creativecommons.org/faq/#what-is-the-difference-between-plagiarism-and-copyright-infringement-and-what-role-do-cc-licenses-play-to-address-plagiarism how our licenses interact with academic citation standards in our FAQ].

== Common pitfalls ==

Below are some practices that you may wish to avoid. These practices are not always contrary to the Creative Commons licensing terms, but they often make it more challenging for users to find the original source and/or author.

'''Attribute in alt text'''
:Alt text is intended to provide accessible information about visual materials for users with cognitive disabilities or visual impairment. Using this field for licensing information makes browsing difficult for those users.

'''Attribute in metadata fields only'''
:While it is great to include attribution in metadata fields (such as EXIF for images), in most cases this is not the only place to include attribution information. This is because many users are likely not aware of, and will never see, attribution information included in metadata.

'''Credit authors by names other than the ones they have selected'''
:Many people believe that attribution must be given to the real name of the author of a work, but this is not the case — always give attribution to the name the author has specified, even if it is a pseudonym. If the author does not give a name or explicitly requests to be anonymous, you must give the other attribution information (i.e., “T” and “SL” from “TASL”) without crediting the author.

'''Credit a site (or Creative Commons itself!) instead of the author'''
:Unless an author specifically requests users to only credit a site, crediting the site where you have found the material cannot substitute crediting the author. An author may have uploaded material to a site under a CC license, but in most cases, the copyright is still held by the author, and it is the copyright holder who needs to be credited. For example, many photos sourced from Wikimedia Commons are attributed to Wikimedia when they must be attributed to the authors.

[[Category:Marking]]
[[Category:Licensing]]
[[Category:Community]]
[[Category:Media]]
[[Category:HOWTO]]
[[Category:Guide]]
{{Best Practice}}

Recommended practices for attribution

2022-12-07T20:50:38Z

CCID-yuanxiaoxu: /* Other guides to attribution */

You can use CC-licensed materials as long as you follow the license conditions. One condition of all CC licenses is attribution: crediting the author and noting the source and the license. Generally speaking, attribution must reasonably include all relevant information supplied by the licensor. Because each use case is different, you can decide what form of attribution is most suitable for your specific situation. The following examples are intended to illustrate what typical prudent practices look like. We expect community norms and expectations to evolve with time, and will adapt this guide accordingly.
In addition to attribution, there are also [https://wiki.creativecommons.org/wiki/Considerations_for_licensors_and_licensees#Considerations_for_licensees|other things to consider as a licensor or a licensee]. If you are a licensor and would like to learn how to license your own material, take a look at [https://wiki.creativecommons.org/wiki/Marking_your_work_with_a_CC_license our guide on how to mark your work with a CC license].

==Basic components of attribution==

[[File:19th_century_tassel_from_Smithsonian.jpeg|290px|left]]

Whenever you are reusing CC licensed works, we recommend that the attribution include the '''T'''itle, '''A'''uthor, '''S'''ource, and '''L'''icense. This is true whether you’re sharing the work as-is or if you have made an adaptation. To remember these attribution elements, it’s helpful to think of the acronym: '''TASL'''.

Let’s now go through '''TASL''' — we will explain each element in more detail:

'''Title''': What is the name of the work?

:If a title was provided for the work, include it as a part of the attribution. Sometimes a title is not provided; in that case, there’s no need to mention the title.

:The inclusion of title is a requirement of all CC licenses version 3.0 or earlier, and it is optional for the 4.0 suites. See [https://wiki.creativecommons.org/wiki/Recommended_practices_for_attribution#License_details License details].

'''Author''': Who allows you to use the work?

:We often use “author” as a shorthand when we are, legally speaking, referring to the “licensor” (a.k.a., the “copyright holder” or “rightsholder”). This is because, in most CC-licensed works, the licensor is the same person or entity as the author. When an author is licensing their work under a CC license, and has made their name available, include the author’s name as a component in your attribution. Sometimes, the licensor may want you to give credit to some other entity, like a company or institution, or the licensor may want to be credited by a pseudonym instead of their real name. In rare cases, the licensor may not want to be attributed at all. In all of these cases, do what the licensor requests.

:Sometimes, the author will also provide a copyright notice, which consists of the copyright symbol, year of publication, and the name of the author/licensor. Include the copyright notice as a part of your attribution if such information is provided.

'''Source''': Where can people find the work?

:Please make it possible for future users to find the source of the material by including a URL or hyperlink where the work resides. This often is where you found the work. If you found it somewhere other than the original site, try to include information about the original site where the work was first shared publicly. It is also better to use the original URL instead of a shortened link, whether you are hyperlinking or printing out the entire URL.

'''License''': How can you use the work?

:You must specify which CC license was applied to the work you are reusing. Each of the six different CC licenses come with distinct requirements for re-use. We recommend that you name and provide a link to the license, e.g., [http://creativecommons.org/licenses/by/4.0 CC BY 4.0] (http://creativecommons.org/licenses/by/4.0) for a work licensed under CC BY 4.0.

:Consider also including the “disclaimer of warranties,” which clarifies that the author makes no representations or warranties about the non-infringement or absence of other defects concerning the CC-licensed work. In plain English, this means that the users will use the work at their own risk.

:To sum up, if the licensor has provided any information related to TASL, consider including them in your attribution. We also recommend providing links to the Title, Author, Source, and License, where possible, so future users can easily access the information they need on a work and the license terms.
<hr>
===Reasonable attribution===

The CC licenses ask you to be reasonable:

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 90%;">You may satisfy the attribution requirement in any reasonable manner based on the medium, means and context in which the Licensed Material is used. For example, it may be reasonable to satisfy some or all of the conditions by retaining a copyright notice, or by providing a URI or hyperlink associated with the Licensed Material, if the copyright notice or webpage includes some or all of the required information.</div>

There is no single best or correct way of attribution, as long as your attribution is reasonable and suited to the medium you're working with.
<hr>

===License details===

If you have any doubts or questions, you can read the complete attribution requirements which are spelled out in detail in the legal code of every CC license, eg. http://creativecommons.org/licenses/by/4.0/legalcode This [[License_Versions#Detailed_attribution_comparison_chart|chart compares the detailed requirements across all versions of CC licenses.]]

==Examples of attribution==

We will now look at some examples in different media.

===Attributing an image===

Here is a photo. Below, we will go over some good and bad examples of how people might attribute it.

[[File:8256206923_c77e85319e_n.jpg]]
<hr>

====This is a great attribution====
<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">
"[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Creative Commons 10th Birthday Celebration San Francisco]" by [http://www.flickr.com/photos/sixteenmilesofstring/ Timothy Vollmer] is licensed under [http://creativecommons.org/licenses/by/4.0/ CC BY 4.0]</div>

''Let’s go through TASL:''
:'''T'''itle? "Creative Commons 10th Birthday Celebration San Francisco"
:'''A'''uthor? "[http://www.flickr.com/photos/sixteenmilesofstring/ Timothy Vollmer]" - linked to his profile page
:'''S'''ource? "[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Creative Commons 10th Birthday Celebration San Francisco]" - linked to original Flickr page
:'''L'''icense? "[http://creativecommons.org/licenses/by/4.0/ CC BY 4.0]" - linked to license deed

Most importantly, this attribution reasonably includes all the relevant information provided by the author.
<hr>

====This is a pretty good attribution====

<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Photo] by Timothy Vollmer/ [http://creativecommons.org/licenses/by/2.0/ CC BY]</div>

''Let’s go through TASL:''
:'''T'''itle? Title is not noted but at least the source is linked.
:'''A'''uthor? "Timothy Vollmer"
:'''S'''ource? "[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Photo]" - linked to original Flickr page
:'''L'''icense? "[http://creativecommons.org/licenses/by/4.0/ CC BY]" - linked to license deed

As you see, a good attribution includes all the essential '''TASL''' elements, even though they may not mirror the format of credit the author has requested.
<hr>

==== This is an incorrect attribution====
<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">Photo: Creative Commons</div>

''Let’s go through TASL'':
:'''T'''itle? Title of the image is not noted
:'''A'''uthor? Author is not noted (It is a common mistake to attribute CC-licensed photos to CC, but Creative Commons is not the author!)
:'''S'''ource? No link to the original source
:'''L'''icense? There is no mention of a license nor a link to the license. "Creative Commons" is the name of an organization; it does not equate to any of the licenses maintained by the Creative Commons.
<hr>

====This is a great attribution for an image you modified slightly====
:[[File:Cropped_tvol_cupcake.png|300px]]

<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">"[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Creative Commons 10th Birthday Celebration San Francisco]" by [http://www.flickr.com/photos/sixteenmilesofstring/ Timothy Vollmer], used under [http://creativecommons.org/licenses/by/4.0/ CC BY 4.0] / Cropped from original</div>

Here, information on '''T'''itle, '''A'''uthor, '''S'''ource, and '''L'''icense are all included as requested by the author. The slight modification is also noted and briefly described.

Note if the modification changes the work’s meaning in a way that would be considered creative — that is, not a purely mechanical change or a simple crop/excerpt that keeps the original message undistorted, it would be considered creating a new adaptation of the original work. You cannot rely on a CC license that does not allow adaptation (e.g., CC BY-ND or CC BY-NC-ND) when making such modifications.

<hr>

====This is a great attribution for when you have created an adaptation====

:[[File:8256206923_c77e85319e_n_90fied.jpg|300px]]

<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">This work, "90fied", is adapted from "[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Creative Commons 10th Birthday Celebration San Francisco]" by [http://www.flickr.com/photos/sixteenmilesofstring/ Timothy Vollmer], used under [http://creativecommons.org/licenses/by/4.0/ CC BY 4.0]. "90fied" is licensed under [http://creativecommons.org/licenses/by/4.0/ CC BY 4.0] by [Your name here].</div>

''Let’s go through TASL:''

Original '''T'''itle, '''A'''uthor, '''S'''ource, and '''L'''icense are all noted.

The original work is referenced and the fact that it is an adaptation is also noted, so viewers can see what has changed.

The author and other attribution information for the new adapted work is also noted.

Note: If you're at a point where you are licensing works that are adaptations, go to [[Marking your work with a CC license]].
<hr>

===Attributing music===

====When you incorporate music in an audio or video recording====
Music (both the underlying composition and the sound recordings) — such as a song, or a recording of natural sounds — can be attributed within the audio/video, and in the description text of the audio/video. How to attribute a CC licensed music in an audio or video recording will largely depend on what is reasonable for a chosen medium and platform.

Caution: Licenses with “ND” do not allow for adaptations. Your use of CC-licensed music is often an adaptation!

It is considered adaptation if you incorporate CC-licensed music into your work in a way that the CC-licensed music can no longer be seen as a stand-alone piece. For example, if you are using a song as background music in a podcast or in a video, it is considered an adaptation of the song.

Keep in mind that CC BY-ND and CC BY-NC-ND do not allow adaptations (although you may be authorized by law to do so, such as under a users’ right like fair use, or you may ask for the author’s permission independent of the CC license).
<hr>

[[File:Smithsonian_music_stand.jpeg|left|250px]]

=====This is a great attribution of background music in a podcast or a video=====
When reasonable to do so, we recommend that you include attribution both in the description box and in the podcast recording or the video recording itself.

If you are using the following song in a podcast: ‘Day Bird’ by Broke for Free ([https://brokeforfree.com brokeforfree.com]), this would be a great way to provide attribution (which you can see in [https://soundcloud.com/wearecc/open-minds-podcast-catherine-stihler-ceo-of-creative-commons the Creative Commons podcast]) —

:At the end of the podcast audio recording, the host says:
:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 90%;">Special thanks to the musician Broke for Free, whose track “Day Bird” you heard at the beginning of this episode and you are listening to right now. It's under the Creative Commons Attribution License, meaning it's free for anyone to use. You can find it at the Free Music Archive—freemusicarchive.org</div>

:In the description box, the information text reads:
:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 90%;">Theme music: “Day Bird” by Broke for Free ([https://brokeforfree.com brokeforfree.com]). Available for use under the CC BY 3.0 license ([https://creativecommons.org/licenses/by/3.0/ creativecommons.org/licenses/by/3.0/]), at [https://freemusicarchive.org/music/Broke_For_Free/Directionless_EP/Broke_For_Free_-_Directionless_EP_-_03_Day_Bird|the Free Music Archive].</div>

''Let’s go through TASL:''

:'''T'''itle? Both the recording and the description box include the title of the work, “Day Bird”

:'''A'''uthor? "Broke for Free," again, noted both in the recording and in the description box

:'''S'''ource? Both the author’s page and the archive’s page are included with links

:'''L'''icense? "CC BY 3.0" — linked to license deed

You cannot talk over, or remix, music licensed under CC BY-ND or CC BY-NC-ND.

<hr>

=====This is a bad attribution of background music in a podcast or a video=====

A bad attribution is one where you do not provide enough information for a user to find the music you are using. The following is a bad attribution for the same song:

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">No attribution is included in the podcast recording or the video itself.

In the description box, it says: “ Creative Commons music.”</div>

''Let’s go through TASL:''

:'''T'''itle? Title is not noted

:'''A'''uthor? Author is not noted

:'''S'''ource? Source is not noted; users cannot find the specific song used in the podcast

:'''L'''icense? No information on the CC license

The attribution information is not sufficient for people to find the song you have re-used.
<hr>

====When you are not adding new elements to the music====
When you re-use music without adding new elements to it, you are not making an adaptation. In that case, you can rely on any of the CC licenses, including CC BY-ND and CC BY-NC-ND. We recommend providing attribution information in writing.

[[File:Wiki_page_attributing_night_owl.png|400px]]

On [https://commons.wikimedia.org/wiki/File:Broke_For_Free_-_01_-_Night_Owl.ogg this Wikipedia page], you can see an example of great attribution for the sharing another soundtrack, “Night Owl” by Broke for Free, when it’s without adaptation.

''Let’s go through TASL:''

'''T'''itle? Title of the work, “Night Owl,” is noted

'''A'''uthor? "Broke for Free," noted and linked to the author’s webpage

'''S'''ource? A link is provided for the source

'''L'''icense? "CC BY 3.0" — linked to license deed
<hr>

===Attributing text===
Let’s take [https://github.com/getify/You-Dont-Know-JS ''You Don't Know JS Yet'' (2nd Edition)] as an example, and go over what your attribution may look like if you reuse the book series. The information under the “License & Copyright” section looks like this on the webpage where the book series was originally shared:
:[[File:attributing_You_Don't_Know_JS_Yet_(2nd_Edition).png|200px]]

We recommend that you retain all the information provided by the author of the book series when it is reasonable for you to do so. For example, if you are distributing digital copies or excerpts of the book series in a free seminar, or using parts of the book in a free online course or presentation, the attribution will likely look something like this:

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">This chapter is from “[https://github.com/getify/You-Dont-Know-JS You Don't Know JS Yet (2nd Edition)]” by [https://github.com/getify Kyle Simpson]. The book is licensed under the [https://creativecommons.org/licenses/by-nc-nd/4.0/ CC BY-NC-ND 4.0 license]. © 2019-2022 Kyle Simpson.</div>

On the other hand, if you are distributing hard copies of the book series or excerpts from the book series, instead of using hyperlinks, you may wish to include the links so it’s easier for users to locate the original source of the book, the author, and the CC license:

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">This chapter is from “You Don't Know JS Yet (2nd Edition)” (https://github.com/getify/You-Dont-Know-JS) by Kyle Simpson (https://github.com/getify). The book is licensed under the CC BY-NC-ND 4.0 license (https://creativecommons.org/licenses/by-nc-nd/4.0/). © 2019-2022 Kyle Simpson.</div>

Note that the CC BY-NC-ND license includes the NoDerivatives requirement, which indicates that no adaptations are allowed. You cannot make any adaptations relying on the CC BY-NC-CD license the author chose for the book. If you would like to make a translation of the book, for example, you will need to ask the author for permission first.

The CC BY-NC-ND license also includes the NonCommercial requirement. To learn more, take a look at [https://en.wikipedia.org/wiki/Creative_Commons_NonCommercial_license our guide about the NonCommercial licenses].
<hr>

=== Attributing materials from multiple sources ===

:[[File:Saylor_marking_example.jpg]]

''Let’s go through TASL:''

:'''T'''itle? Specific works are named, e.g., "Box-and-whisker Plots"

:'''A'''uthor? Different authors noted for the different works

:'''S'''ource? Original materials are linked for each work

:'''L'''icense? The different licenses (Creative Commons Attribution for Collaborative Statistics and Creative Commons Attribution-Noncommercial-ShareAlike for the Khan Academy video) are spelled out and linked for each work

:Lastly, it is clear which attribution belongs to which work.

You can visit the [http://www.saylor.org/courses/ma121/ Saylor.org Introduction to Statistics course page] to see how they marked it up directly.
<hr>

=== Publishing attribution on a separate web page ===
As stated above, recommended attribution depends on the medium you're working with. For media such as offline materials, video, audio, and images, consider publishing a web page with attribution information. For example, on a webpage featuring your audio recording, provide a credit list of material you used that adheres to best practices above. Doing so allows not only your material, but the materials you attribute, to be found by search engines and other web discovery tools. If possible within the medium, make the Author, Source, and License links the user can follow.

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">'''Example:'''<br>This video features the song [http://ccmixter.org/media/files/victor/6374 "Desaprendere (Treatment)"] by [http://fourstones.net/ fourstones], available under a Creative Commons [http://creativecommons.org/licenses/by-nc/2.5/ Attribution-Noncommercial 2.5 license].</div>

<hr>

==Citing public domain materials==
Although attribution is not a legal obligation under [https://creativecommons.org/share-your-work/public-domain/cc0/ CC0 dedication]’s or [https://creativecommons.org/share-your-work/public-domain/pdm/ CC Public Domain Mark]’s licensing terms, we recommend that you consider including information about the hosting institution for public domain materials when it is reasonable to do so. Citing public domain works in this way not only encourages institutions to digitize and share more public domain materials in their physical collections, but also empowers users to easily locate the original source.

Here is an example of citing the source of a public domain image. The following public domain image is digitized and hosted by the Rijksmuseum (the national museum of the Netherlands). The Rijksmuseum has applied a CC0 dedication to the image.

:[[File:Attributing_the_milkmaid.png|300px]]

You may provide credit in the following format:

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">“[http://hdl.handle.net/10934/RM0001.COLLECT.6417 The Milkmaid]” by Vermeer. The Rijksmuseum collection. The image is dedicated to the public domain under [https://creativecommons.org/share-your-work/public-domain/cc0/ CC0]. </div>

In most cases, people credit the source regardless of the work’s copyright status. Especially in an academic setting, providing source information about other people’s works has long been considered crucial to academic integrity. Copyright cannot be the only checkbox when deciding whether a source will be credited. You can learn more about [https://creativecommons.org/faq/#what-is-the-difference-between-plagiarism-and-copyright-infringement-and-what-role-do-cc-licenses-play-to-address-plagiarism how our licenses interact with academic citation standards in our FAQ].

== Common pitfalls ==

Below are some practices that you may wish to avoid. These practices are not always contrary to the Creative Commons licensing terms, but they often make it more challenging for users to find the original source and/or author.

'''Attribute in alt text'''
:Alt text is intended to provide accessible information about visual materials for users with cognitive disabilities or visual impairment. Using this field for licensing information makes browsing difficult for those users.

'''Attribute in metadata fields only'''
:While it is great to include attribution in metadata fields (such as EXIF for images), in most cases this is not the only place to include attribution information. This is because many users are likely not aware of, and will never see, attribution information included in metadata.

'''Credit authors by names other than the ones they have selected'''
:Many people believe that attribution must be given to the real name of the author of a work, but this is not the case — always give attribution to the name the author has specified, even if it is a pseudonym. If the author does not give a name or explicitly requests to be anonymous, you must give the other attribution information (i.e., “T” and “SL” from “TASL”) without crediting the author.

'''Credit a site (or Creative Commons itself!) instead of the author'''
:Unless an author specifically requests users to only credit a site, crediting the site where you have found the material cannot substitute crediting the author. An author may have uploaded material to a site under a CC license, but in most cases, the copyright is still held by the author, and it is the copyright holder who needs to be credited. For example, many photos sourced from Wikimedia Commons are attributed to Wikimedia when they must be attributed to the authors.

== Other guides to attribution ==

* [http://creativecommons.org.au/materials/attribution.pdf Attributing Creative Commons Material] (pdf) - Creative Commons Australia's publication is full of examples with colorful imagery.
* [http://www.newmediarights.org/guide/how_to/creative_commons/best_practices_creative_commons_attributions How to attribute works you reuse under a Creative Commons license] by New Media Rights provides real world examples by different media type.

[[Category:Marking]]
[[Category:Licensing]]
[[Category:Community]]
[[Category:Media]]
[[Category:HOWTO]]
[[Category:Guide]]
{{Best Practice}}

Recommended practices for attribution

2022-12-07T20:42:16Z

CCID-yuanxiaoxu: /* Attributing public domain materials */

You can use CC-licensed materials as long as you follow the license conditions. One condition of all CC licenses is attribution: crediting the author and noting the source and the license. Generally speaking, attribution must reasonably include all relevant information supplied by the licensor. Because each use case is different, you can decide what form of attribution is most suitable for your specific situation. The following examples are intended to illustrate what typical prudent practices look like. We expect community norms and expectations to evolve with time, and will adapt this guide accordingly.
In addition to attribution, there are also [https://wiki.creativecommons.org/wiki/Considerations_for_licensors_and_licensees#Considerations_for_licensees|other things to consider as a licensor or a licensee]. If you are a licensor and would like to learn how to license your own material, take a look at [https://wiki.creativecommons.org/wiki/Marking_your_work_with_a_CC_license our guide on how to mark your work with a CC license].

==Basic components of attribution==

[[File:19th_century_tassel_from_Smithsonian.jpeg|290px|left]]

Whenever you are reusing CC licensed works, we recommend that the attribution include the '''T'''itle, '''A'''uthor, '''S'''ource, and '''L'''icense. This is true whether you’re sharing the work as-is or if you have made an adaptation. To remember these attribution elements, it’s helpful to think of the acronym: '''TASL'''.

Let’s now go through '''TASL''' — we will explain each element in more detail:

'''Title''': What is the name of the work?

:If a title was provided for the work, include it as a part of the attribution. Sometimes a title is not provided; in that case, there’s no need to mention the title.

:The inclusion of title is a requirement of all CC licenses version 3.0 or earlier, and it is optional for the 4.0 suites. See [https://wiki.creativecommons.org/wiki/Recommended_practices_for_attribution#License_details License details].

'''Author''': Who allows you to use the work?

:We often use “author” as a shorthand when we are, legally speaking, referring to the “licensor” (a.k.a., the “copyright holder” or “rightsholder”). This is because, in most CC-licensed works, the licensor is the same person or entity as the author. When an author is licensing their work under a CC license, and has made their name available, include the author’s name as a component in your attribution. Sometimes, the licensor may want you to give credit to some other entity, like a company or institution, or the licensor may want to be credited by a pseudonym instead of their real name. In rare cases, the licensor may not want to be attributed at all. In all of these cases, do what the licensor requests.

:Sometimes, the author will also provide a copyright notice, which consists of the copyright symbol, year of publication, and the name of the author/licensor. Include the copyright notice as a part of your attribution if such information is provided.

'''Source''': Where can people find the work?

:Please make it possible for future users to find the source of the material by including a URL or hyperlink where the work resides. This often is where you found the work. If you found it somewhere other than the original site, try to include information about the original site where the work was first shared publicly. It is also better to use the original URL instead of a shortened link, whether you are hyperlinking or printing out the entire URL.

'''License''': How can you use the work?

:You must specify which CC license was applied to the work you are reusing. Each of the six different CC licenses come with distinct requirements for re-use. We recommend that you name and provide a link to the license, e.g., [http://creativecommons.org/licenses/by/4.0 CC BY 4.0] (http://creativecommons.org/licenses/by/4.0) for a work licensed under CC BY 4.0.

:Consider also including the “disclaimer of warranties,” which clarifies that the author makes no representations or warranties about the non-infringement or absence of other defects concerning the CC-licensed work. In plain English, this means that the users will use the work at their own risk.

:To sum up, if the licensor has provided any information related to TASL, consider including them in your attribution. We also recommend providing links to the Title, Author, Source, and License, where possible, so future users can easily access the information they need on a work and the license terms.
<hr>
===Reasonable attribution===

The CC licenses ask you to be reasonable:

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 90%;">You may satisfy the attribution requirement in any reasonable manner based on the medium, means and context in which the Licensed Material is used. For example, it may be reasonable to satisfy some or all of the conditions by retaining a copyright notice, or by providing a URI or hyperlink associated with the Licensed Material, if the copyright notice or webpage includes some or all of the required information.</div>

There is no single best or correct way of attribution, as long as your attribution is reasonable and suited to the medium you're working with.
<hr>

===License details===

If you have any doubts or questions, you can read the complete attribution requirements which are spelled out in detail in the legal code of every CC license, eg. http://creativecommons.org/licenses/by/4.0/legalcode This [[License_Versions#Detailed_attribution_comparison_chart|chart compares the detailed requirements across all versions of CC licenses.]]

==Examples of attribution==

We will now look at some examples in different media.

===Attributing an image===

Here is a photo. Below, we will go over some good and bad examples of how people might attribute it.

[[File:8256206923_c77e85319e_n.jpg]]
<hr>

====This is a great attribution====
<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">
"[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Creative Commons 10th Birthday Celebration San Francisco]" by [http://www.flickr.com/photos/sixteenmilesofstring/ Timothy Vollmer] is licensed under [http://creativecommons.org/licenses/by/4.0/ CC BY 4.0]</div>

''Let’s go through TASL:''
:'''T'''itle? "Creative Commons 10th Birthday Celebration San Francisco"
:'''A'''uthor? "[http://www.flickr.com/photos/sixteenmilesofstring/ Timothy Vollmer]" - linked to his profile page
:'''S'''ource? "[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Creative Commons 10th Birthday Celebration San Francisco]" - linked to original Flickr page
:'''L'''icense? "[http://creativecommons.org/licenses/by/4.0/ CC BY 4.0]" - linked to license deed

Most importantly, this attribution reasonably includes all the relevant information provided by the author.
<hr>

====This is a pretty good attribution====

<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Photo] by Timothy Vollmer/ [http://creativecommons.org/licenses/by/2.0/ CC BY]</div>

''Let’s go through TASL:''
:'''T'''itle? Title is not noted but at least the source is linked.
:'''A'''uthor? "Timothy Vollmer"
:'''S'''ource? "[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Photo]" - linked to original Flickr page
:'''L'''icense? "[http://creativecommons.org/licenses/by/4.0/ CC BY]" - linked to license deed

As you see, a good attribution includes all the essential '''TASL''' elements, even though they may not mirror the format of credit the author has requested.
<hr>

==== This is an incorrect attribution====
<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">Photo: Creative Commons</div>

''Let’s go through TASL'':
:'''T'''itle? Title of the image is not noted
:'''A'''uthor? Author is not noted (It is a common mistake to attribute CC-licensed photos to CC, but Creative Commons is not the author!)
:'''S'''ource? No link to the original source
:'''L'''icense? There is no mention of a license nor a link to the license. "Creative Commons" is the name of an organization; it does not equate to any of the licenses maintained by the Creative Commons.
<hr>

====This is a great attribution for an image you modified slightly====
:[[File:Cropped_tvol_cupcake.png|300px]]

<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">"[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Creative Commons 10th Birthday Celebration San Francisco]" by [http://www.flickr.com/photos/sixteenmilesofstring/ Timothy Vollmer], used under [http://creativecommons.org/licenses/by/4.0/ CC BY 4.0] / Cropped from original</div>

Here, information on '''T'''itle, '''A'''uthor, '''S'''ource, and '''L'''icense are all included as requested by the author. The slight modification is also noted and briefly described.

Note if the modification changes the work’s meaning in a way that would be considered creative — that is, not a purely mechanical change or a simple crop/excerpt that keeps the original message undistorted, it would be considered creating a new adaptation of the original work. You cannot rely on a CC license that does not allow adaptation (e.g., CC BY-ND or CC BY-NC-ND) when making such modifications.

<hr>

====This is a great attribution for when you have created an adaptation====

:[[File:8256206923_c77e85319e_n_90fied.jpg|300px]]

<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">This work, "90fied", is adapted from "[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Creative Commons 10th Birthday Celebration San Francisco]" by [http://www.flickr.com/photos/sixteenmilesofstring/ Timothy Vollmer], used under [http://creativecommons.org/licenses/by/4.0/ CC BY 4.0]. "90fied" is licensed under [http://creativecommons.org/licenses/by/4.0/ CC BY 4.0] by [Your name here].</div>

''Let’s go through TASL:''

Original '''T'''itle, '''A'''uthor, '''S'''ource, and '''L'''icense are all noted.

The original work is referenced and the fact that it is an adaptation is also noted, so viewers can see what has changed.

The author and other attribution information for the new adapted work is also noted.

Note: If you're at a point where you are licensing works that are adaptations, go to [[Marking your work with a CC license]].
<hr>

===Attributing music===

====When you incorporate music in an audio or video recording====
Music (both the underlying composition and the sound recordings) — such as a song, or a recording of natural sounds — can be attributed within the audio/video, and in the description text of the audio/video. How to attribute a CC licensed music in an audio or video recording will largely depend on what is reasonable for a chosen medium and platform.

Caution: Licenses with “ND” do not allow for adaptations. Your use of CC-licensed music is often an adaptation!

It is considered adaptation if you incorporate CC-licensed music into your work in a way that the CC-licensed music can no longer be seen as a stand-alone piece. For example, if you are using a song as background music in a podcast or in a video, it is considered an adaptation of the song.

Keep in mind that CC BY-ND and CC BY-NC-ND do not allow adaptations (although you may be authorized by law to do so, such as under a users’ right like fair use, or you may ask for the author’s permission independent of the CC license).
<hr>

[[File:Smithsonian_music_stand.jpeg|left|250px]]

=====This is a great attribution of background music in a podcast or a video=====
When reasonable to do so, we recommend that you include attribution both in the description box and in the podcast recording or the video recording itself.

If you are using the following song in a podcast: ‘Day Bird’ by Broke for Free ([https://brokeforfree.com brokeforfree.com]), this would be a great way to provide attribution (which you can see in [https://soundcloud.com/wearecc/open-minds-podcast-catherine-stihler-ceo-of-creative-commons the Creative Commons podcast]) —

:At the end of the podcast audio recording, the host says:
:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 90%;">Special thanks to the musician Broke for Free, whose track “Day Bird” you heard at the beginning of this episode and you are listening to right now. It's under the Creative Commons Attribution License, meaning it's free for anyone to use. You can find it at the Free Music Archive—freemusicarchive.org</div>

:In the description box, the information text reads:
:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 90%;">Theme music: “Day Bird” by Broke for Free ([https://brokeforfree.com brokeforfree.com]). Available for use under the CC BY 3.0 license ([https://creativecommons.org/licenses/by/3.0/ creativecommons.org/licenses/by/3.0/]), at [https://freemusicarchive.org/music/Broke_For_Free/Directionless_EP/Broke_For_Free_-_Directionless_EP_-_03_Day_Bird|the Free Music Archive].</div>

''Let’s go through TASL:''

:'''T'''itle? Both the recording and the description box include the title of the work, “Day Bird”

:'''A'''uthor? "Broke for Free," again, noted both in the recording and in the description box

:'''S'''ource? Both the author’s page and the archive’s page are included with links

:'''L'''icense? "CC BY 3.0" — linked to license deed

You cannot talk over, or remix, music licensed under CC BY-ND or CC BY-NC-ND.

<hr>

=====This is a bad attribution of background music in a podcast or a video=====

A bad attribution is one where you do not provide enough information for a user to find the music you are using. The following is a bad attribution for the same song:

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">No attribution is included in the podcast recording or the video itself.

In the description box, it says: “ Creative Commons music.”</div>

''Let’s go through TASL:''

:'''T'''itle? Title is not noted

:'''A'''uthor? Author is not noted

:'''S'''ource? Source is not noted; users cannot find the specific song used in the podcast

:'''L'''icense? No information on the CC license

The attribution information is not sufficient for people to find the song you have re-used.
<hr>

====When you are not adding new elements to the music====
When you re-use music without adding new elements to it, you are not making an adaptation. In that case, you can rely on any of the CC licenses, including CC BY-ND and CC BY-NC-ND. We recommend providing attribution information in writing.

[[File:Wiki_page_attributing_night_owl.png|400px]]

On [https://commons.wikimedia.org/wiki/File:Broke_For_Free_-_01_-_Night_Owl.ogg this Wikipedia page], you can see an example of great attribution for the sharing another soundtrack, “Night Owl” by Broke for Free, when it’s without adaptation.

''Let’s go through TASL:''

'''T'''itle? Title of the work, “Night Owl,” is noted

'''A'''uthor? "Broke for Free," noted and linked to the author’s webpage

'''S'''ource? A link is provided for the source

'''L'''icense? "CC BY 3.0" — linked to license deed
<hr>

===Attributing text===
Let’s take [https://github.com/getify/You-Dont-Know-JS ''You Don't Know JS Yet'' (2nd Edition)] as an example, and go over what your attribution may look like if you reuse the book series. The information under the “License & Copyright” section looks like this on the webpage where the book series was originally shared:
:[[File:attributing_You_Don't_Know_JS_Yet_(2nd_Edition).png|200px]]

We recommend that you retain all the information provided by the author of the book series when it is reasonable for you to do so. For example, if you are distributing digital copies or excerpts of the book series in a free seminar, or using parts of the book in a free online course or presentation, the attribution will likely look something like this:

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">This chapter is from “[https://github.com/getify/You-Dont-Know-JS You Don't Know JS Yet (2nd Edition)]” by [https://github.com/getify Kyle Simpson]. The book is licensed under the [https://creativecommons.org/licenses/by-nc-nd/4.0/ CC BY-NC-ND 4.0 license]. © 2019-2022 Kyle Simpson.</div>

On the other hand, if you are distributing hard copies of the book series or excerpts from the book series, instead of using hyperlinks, you may wish to include the links so it’s easier for users to locate the original source of the book, the author, and the CC license:

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">This chapter is from “You Don't Know JS Yet (2nd Edition)” (https://github.com/getify/You-Dont-Know-JS) by Kyle Simpson (https://github.com/getify). The book is licensed under the CC BY-NC-ND 4.0 license (https://creativecommons.org/licenses/by-nc-nd/4.0/). © 2019-2022 Kyle Simpson.</div>

Note that the CC BY-NC-ND license includes the NoDerivatives requirement, which indicates that no adaptations are allowed. You cannot make any adaptations relying on the CC BY-NC-CD license the author chose for the book. If you would like to make a translation of the book, for example, you will need to ask the author for permission first.

The CC BY-NC-ND license also includes the NonCommercial requirement. To learn more, take a look at [https://en.wikipedia.org/wiki/Creative_Commons_NonCommercial_license our guide about the NonCommercial licenses].
<hr>

=== Attributing materials from multiple sources ===

:[[File:Saylor_marking_example.jpg]]

''Let’s go through TASL:''

:'''T'''itle? Specific works are named, e.g., "Box-and-whisker Plots"

:'''A'''uthor? Different authors noted for the different works

:'''S'''ource? Original materials are linked for each work

:'''L'''icense? The different licenses (Creative Commons Attribution for Collaborative Statistics and Creative Commons Attribution-Noncommercial-ShareAlike for the Khan Academy video) are spelled out and linked for each work

:Lastly, it is clear which attribution belongs to which work.

You can visit the [http://www.saylor.org/courses/ma121/ Saylor.org Introduction to Statistics course page] to see how they marked it up directly.
<hr>

=== Publishing attribution on a separate web page ===
As stated above, recommended attribution depends on the medium you're working with. For media such as offline materials, video, audio, and images, consider publishing a web page with attribution information. For example, on a webpage featuring your audio recording, provide a credit list of material you used that adheres to best practices above. Doing so allows not only your material, but the materials you attribute, to be found by search engines and other web discovery tools. If possible within the medium, make the Author, Source, and License links the user can follow.

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">'''Example:'''<br>This video features the song [http://ccmixter.org/media/files/victor/6374 "Desaprendere (Treatment)"] by [http://fourstones.net/ fourstones], available under a Creative Commons [http://creativecommons.org/licenses/by-nc/2.5/ Attribution-Noncommercial 2.5 license].</div>

<hr>

==Citing public domain materials==
Although attribution is not a legal obligation under [https://creativecommons.org/share-your-work/public-domain/cc0/ CC0 dedication]’s or [https://creativecommons.org/share-your-work/public-domain/pdm/ CC Public Domain Mark]’s licensing terms, we recommend that you consider including information about the hosting institution for public domain materials when it is reasonable to do so. Citing public domain works in this way not only encourages institutions to digitize and share more public domain materials in their physical collections, but also empowers users to easily locate the original source.

Here is an example of citing the source of a public domain image. The following public domain image is digitized and hosted by the Rijksmuseum (the national museum of the Netherlands). The Rijksmuseum has applied a CC0 dedication to the image.

:[[File:Attributing_the_milkmaid.png|300px]]

You may provide credit in the following format:

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">“[http://hdl.handle.net/10934/RM0001.COLLECT.6417 The Milkmaid]” by Vermeer. The Rijksmuseum collection. The image is dedicated to the public domain under [https://creativecommons.org/share-your-work/public-domain/cc0/ CC0]. </div>

In most cases, people credit the source regardless of the work’s copyright status. Especially in an academic setting, providing source information about other people’s works has long been considered crucial to academic integrity. Copyright cannot be the only checkbox when deciding whether a source will be credited. You can learn more about [https://creativecommons.org/faq/#what-is-the-difference-between-plagiarism-and-copyright-infringement-and-what-role-do-cc-licenses-play-to-address-plagiarism how our licenses interact with academic citation standards in our FAQ].

== Common pitfalls ==

Below are some practices that you may wish to avoid. These practices are not always contrary to the Creative Commons licensing terms, but they often make it more challenging for users to find the original source and/or author.

'''Attribute in alt text'''
:Alt text is intended to provide accessible information about visual materials for users with cognitive disabilities or visual impairment. Using this field for licensing information makes browsing difficult for those users.

'''Attribute in metadata fields only'''
:While it is great to include attribution in metadata fields (such as EXIF for images), in most cases this is not the only place to include attribution information. This is because many users are likely not aware of, and will never see, attribution information included in metadata.

'''Credit authors by names other than the ones they have selected'''
:Many people believe that attribution must be given to the real name of the author of a work, but this is not the case — always give attribution to the name the author has specified, even if it is a pseudonym. If the author does not give a name or explicitly requests to be anonymous, you must give the other attribution information (i.e., “T” and “SL” from “TASL”) without crediting the author.

'''Credit a site (or Creative Commons itself!) instead of the author'''
:Unless an author specifically requests users to only credit a site, crediting the site where you have found the material cannot substitute crediting the author. An author may have uploaded material to a site under a CC license, but in most cases, the copyright is still held by the author, and it is the copyright holder who needs to be credited. For example, many photos sourced from Wikimedia Commons are attributed to Wikimedia when they must be attributed to the authors.

== Other guides to attribution ==

* [http://creativecommons.org.au/materials/attribution.pdf Attributing Creative Commons Material] (pdf) - Creative Commons Australia's publication is full of examples with colorful imagery.
* [http://www.newmediarights.org/guide/how_to/creative_commons/best_practices_creative_commons_attributions How to attribute works you reuse under a Creative Commons license] by New Media Rights provides real world examples by different media type

[[Category:Marking]]
[[Category:Licensing]]
[[Category:Community]]
[[Category:Media]]
[[Category:HOWTO]]
[[Category:Guide]]
{{Best Practice}}

Recommended practices for attribution

2022-12-07T20:41:13Z

CCID-yuanxiaoxu: /* Attributing public domain materials */

You can use CC-licensed materials as long as you follow the license conditions. One condition of all CC licenses is attribution: crediting the author and noting the source and the license. Generally speaking, attribution must reasonably include all relevant information supplied by the licensor. Because each use case is different, you can decide what form of attribution is most suitable for your specific situation. The following examples are intended to illustrate what typical prudent practices look like. We expect community norms and expectations to evolve with time, and will adapt this guide accordingly.
In addition to attribution, there are also [https://wiki.creativecommons.org/wiki/Considerations_for_licensors_and_licensees#Considerations_for_licensees|other things to consider as a licensor or a licensee]. If you are a licensor and would like to learn how to license your own material, take a look at [https://wiki.creativecommons.org/wiki/Marking_your_work_with_a_CC_license our guide on how to mark your work with a CC license].

==Basic components of attribution==

[[File:19th_century_tassel_from_Smithsonian.jpeg|290px|left]]

Whenever you are reusing CC licensed works, we recommend that the attribution include the '''T'''itle, '''A'''uthor, '''S'''ource, and '''L'''icense. This is true whether you’re sharing the work as-is or if you have made an adaptation. To remember these attribution elements, it’s helpful to think of the acronym: '''TASL'''.

Let’s now go through '''TASL''' — we will explain each element in more detail:

'''Title''': What is the name of the work?

:If a title was provided for the work, include it as a part of the attribution. Sometimes a title is not provided; in that case, there’s no need to mention the title.

:The inclusion of title is a requirement of all CC licenses version 3.0 or earlier, and it is optional for the 4.0 suites. See [https://wiki.creativecommons.org/wiki/Recommended_practices_for_attribution#License_details License details].

'''Author''': Who allows you to use the work?

:We often use “author” as a shorthand when we are, legally speaking, referring to the “licensor” (a.k.a., the “copyright holder” or “rightsholder”). This is because, in most CC-licensed works, the licensor is the same person or entity as the author. When an author is licensing their work under a CC license, and has made their name available, include the author’s name as a component in your attribution. Sometimes, the licensor may want you to give credit to some other entity, like a company or institution, or the licensor may want to be credited by a pseudonym instead of their real name. In rare cases, the licensor may not want to be attributed at all. In all of these cases, do what the licensor requests.

:Sometimes, the author will also provide a copyright notice, which consists of the copyright symbol, year of publication, and the name of the author/licensor. Include the copyright notice as a part of your attribution if such information is provided.

'''Source''': Where can people find the work?

:Please make it possible for future users to find the source of the material by including a URL or hyperlink where the work resides. This often is where you found the work. If you found it somewhere other than the original site, try to include information about the original site where the work was first shared publicly. It is also better to use the original URL instead of a shortened link, whether you are hyperlinking or printing out the entire URL.

'''License''': How can you use the work?

:You must specify which CC license was applied to the work you are reusing. Each of the six different CC licenses come with distinct requirements for re-use. We recommend that you name and provide a link to the license, e.g., [http://creativecommons.org/licenses/by/4.0 CC BY 4.0] (http://creativecommons.org/licenses/by/4.0) for a work licensed under CC BY 4.0.

:Consider also including the “disclaimer of warranties,” which clarifies that the author makes no representations or warranties about the non-infringement or absence of other defects concerning the CC-licensed work. In plain English, this means that the users will use the work at their own risk.

:To sum up, if the licensor has provided any information related to TASL, consider including them in your attribution. We also recommend providing links to the Title, Author, Source, and License, where possible, so future users can easily access the information they need on a work and the license terms.
<hr>
===Reasonable attribution===

The CC licenses ask you to be reasonable:

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 90%;">You may satisfy the attribution requirement in any reasonable manner based on the medium, means and context in which the Licensed Material is used. For example, it may be reasonable to satisfy some or all of the conditions by retaining a copyright notice, or by providing a URI or hyperlink associated with the Licensed Material, if the copyright notice or webpage includes some or all of the required information.</div>

There is no single best or correct way of attribution, as long as your attribution is reasonable and suited to the medium you're working with.
<hr>

===License details===

If you have any doubts or questions, you can read the complete attribution requirements which are spelled out in detail in the legal code of every CC license, eg. http://creativecommons.org/licenses/by/4.0/legalcode This [[License_Versions#Detailed_attribution_comparison_chart|chart compares the detailed requirements across all versions of CC licenses.]]

==Examples of attribution==

We will now look at some examples in different media.

===Attributing an image===

Here is a photo. Below, we will go over some good and bad examples of how people might attribute it.

[[File:8256206923_c77e85319e_n.jpg]]
<hr>

====This is a great attribution====
<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">
"[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Creative Commons 10th Birthday Celebration San Francisco]" by [http://www.flickr.com/photos/sixteenmilesofstring/ Timothy Vollmer] is licensed under [http://creativecommons.org/licenses/by/4.0/ CC BY 4.0]</div>

''Let’s go through TASL:''
:'''T'''itle? "Creative Commons 10th Birthday Celebration San Francisco"
:'''A'''uthor? "[http://www.flickr.com/photos/sixteenmilesofstring/ Timothy Vollmer]" - linked to his profile page
:'''S'''ource? "[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Creative Commons 10th Birthday Celebration San Francisco]" - linked to original Flickr page
:'''L'''icense? "[http://creativecommons.org/licenses/by/4.0/ CC BY 4.0]" - linked to license deed

Most importantly, this attribution reasonably includes all the relevant information provided by the author.
<hr>

====This is a pretty good attribution====

<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Photo] by Timothy Vollmer/ [http://creativecommons.org/licenses/by/2.0/ CC BY]</div>

''Let’s go through TASL:''
:'''T'''itle? Title is not noted but at least the source is linked.
:'''A'''uthor? "Timothy Vollmer"
:'''S'''ource? "[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Photo]" - linked to original Flickr page
:'''L'''icense? "[http://creativecommons.org/licenses/by/4.0/ CC BY]" - linked to license deed

As you see, a good attribution includes all the essential '''TASL''' elements, even though they may not mirror the format of credit the author has requested.
<hr>

==== This is an incorrect attribution====
<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">Photo: Creative Commons</div>

''Let’s go through TASL'':
:'''T'''itle? Title of the image is not noted
:'''A'''uthor? Author is not noted (It is a common mistake to attribute CC-licensed photos to CC, but Creative Commons is not the author!)
:'''S'''ource? No link to the original source
:'''L'''icense? There is no mention of a license nor a link to the license. "Creative Commons" is the name of an organization; it does not equate to any of the licenses maintained by the Creative Commons.
<hr>

====This is a great attribution for an image you modified slightly====
:[[File:Cropped_tvol_cupcake.png|300px]]

<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">"[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Creative Commons 10th Birthday Celebration San Francisco]" by [http://www.flickr.com/photos/sixteenmilesofstring/ Timothy Vollmer], used under [http://creativecommons.org/licenses/by/4.0/ CC BY 4.0] / Cropped from original</div>

Here, information on '''T'''itle, '''A'''uthor, '''S'''ource, and '''L'''icense are all included as requested by the author. The slight modification is also noted and briefly described.

Note if the modification changes the work’s meaning in a way that would be considered creative — that is, not a purely mechanical change or a simple crop/excerpt that keeps the original message undistorted, it would be considered creating a new adaptation of the original work. You cannot rely on a CC license that does not allow adaptation (e.g., CC BY-ND or CC BY-NC-ND) when making such modifications.

<hr>

====This is a great attribution for when you have created an adaptation====

:[[File:8256206923_c77e85319e_n_90fied.jpg|300px]]

<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">This work, "90fied", is adapted from "[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Creative Commons 10th Birthday Celebration San Francisco]" by [http://www.flickr.com/photos/sixteenmilesofstring/ Timothy Vollmer], used under [http://creativecommons.org/licenses/by/4.0/ CC BY 4.0]. "90fied" is licensed under [http://creativecommons.org/licenses/by/4.0/ CC BY 4.0] by [Your name here].</div>

''Let’s go through TASL:''

Original '''T'''itle, '''A'''uthor, '''S'''ource, and '''L'''icense are all noted.

The original work is referenced and the fact that it is an adaptation is also noted, so viewers can see what has changed.

The author and other attribution information for the new adapted work is also noted.

Note: If you're at a point where you are licensing works that are adaptations, go to [[Marking your work with a CC license]].
<hr>

===Attributing music===

====When you incorporate music in an audio or video recording====
Music (both the underlying composition and the sound recordings) — such as a song, or a recording of natural sounds — can be attributed within the audio/video, and in the description text of the audio/video. How to attribute a CC licensed music in an audio or video recording will largely depend on what is reasonable for a chosen medium and platform.

Caution: Licenses with “ND” do not allow for adaptations. Your use of CC-licensed music is often an adaptation!

It is considered adaptation if you incorporate CC-licensed music into your work in a way that the CC-licensed music can no longer be seen as a stand-alone piece. For example, if you are using a song as background music in a podcast or in a video, it is considered an adaptation of the song.

Keep in mind that CC BY-ND and CC BY-NC-ND do not allow adaptations (although you may be authorized by law to do so, such as under a users’ right like fair use, or you may ask for the author’s permission independent of the CC license).
<hr>

[[File:Smithsonian_music_stand.jpeg|left|250px]]

=====This is a great attribution of background music in a podcast or a video=====
When reasonable to do so, we recommend that you include attribution both in the description box and in the podcast recording or the video recording itself.

If you are using the following song in a podcast: ‘Day Bird’ by Broke for Free ([https://brokeforfree.com brokeforfree.com]), this would be a great way to provide attribution (which you can see in [https://soundcloud.com/wearecc/open-minds-podcast-catherine-stihler-ceo-of-creative-commons the Creative Commons podcast]) —

:At the end of the podcast audio recording, the host says:
:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 90%;">Special thanks to the musician Broke for Free, whose track “Day Bird” you heard at the beginning of this episode and you are listening to right now. It's under the Creative Commons Attribution License, meaning it's free for anyone to use. You can find it at the Free Music Archive—freemusicarchive.org</div>

:In the description box, the information text reads:
:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 90%;">Theme music: “Day Bird” by Broke for Free ([https://brokeforfree.com brokeforfree.com]). Available for use under the CC BY 3.0 license ([https://creativecommons.org/licenses/by/3.0/ creativecommons.org/licenses/by/3.0/]), at [https://freemusicarchive.org/music/Broke_For_Free/Directionless_EP/Broke_For_Free_-_Directionless_EP_-_03_Day_Bird|the Free Music Archive].</div>

''Let’s go through TASL:''

:'''T'''itle? Both the recording and the description box include the title of the work, “Day Bird”

:'''A'''uthor? "Broke for Free," again, noted both in the recording and in the description box

:'''S'''ource? Both the author’s page and the archive’s page are included with links

:'''L'''icense? "CC BY 3.0" — linked to license deed

You cannot talk over, or remix, music licensed under CC BY-ND or CC BY-NC-ND.

<hr>

=====This is a bad attribution of background music in a podcast or a video=====

A bad attribution is one where you do not provide enough information for a user to find the music you are using. The following is a bad attribution for the same song:

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">No attribution is included in the podcast recording or the video itself.

In the description box, it says: “ Creative Commons music.”</div>

''Let’s go through TASL:''

:'''T'''itle? Title is not noted

:'''A'''uthor? Author is not noted

:'''S'''ource? Source is not noted; users cannot find the specific song used in the podcast

:'''L'''icense? No information on the CC license

The attribution information is not sufficient for people to find the song you have re-used.
<hr>

====When you are not adding new elements to the music====
When you re-use music without adding new elements to it, you are not making an adaptation. In that case, you can rely on any of the CC licenses, including CC BY-ND and CC BY-NC-ND. We recommend providing attribution information in writing.

[[File:Wiki_page_attributing_night_owl.png|400px]]

On [https://commons.wikimedia.org/wiki/File:Broke_For_Free_-_01_-_Night_Owl.ogg this Wikipedia page], you can see an example of great attribution for the sharing another soundtrack, “Night Owl” by Broke for Free, when it’s without adaptation.

''Let’s go through TASL:''

'''T'''itle? Title of the work, “Night Owl,” is noted

'''A'''uthor? "Broke for Free," noted and linked to the author’s webpage

'''S'''ource? A link is provided for the source

'''L'''icense? "CC BY 3.0" — linked to license deed
<hr>

===Attributing text===
Let’s take [https://github.com/getify/You-Dont-Know-JS ''You Don't Know JS Yet'' (2nd Edition)] as an example, and go over what your attribution may look like if you reuse the book series. The information under the “License & Copyright” section looks like this on the webpage where the book series was originally shared:
:[[File:attributing_You_Don't_Know_JS_Yet_(2nd_Edition).png|200px]]

We recommend that you retain all the information provided by the author of the book series when it is reasonable for you to do so. For example, if you are distributing digital copies or excerpts of the book series in a free seminar, or using parts of the book in a free online course or presentation, the attribution will likely look something like this:

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">This chapter is from “[https://github.com/getify/You-Dont-Know-JS You Don't Know JS Yet (2nd Edition)]” by [https://github.com/getify Kyle Simpson]. The book is licensed under the [https://creativecommons.org/licenses/by-nc-nd/4.0/ CC BY-NC-ND 4.0 license]. © 2019-2022 Kyle Simpson.</div>

On the other hand, if you are distributing hard copies of the book series or excerpts from the book series, instead of using hyperlinks, you may wish to include the links so it’s easier for users to locate the original source of the book, the author, and the CC license:

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">This chapter is from “You Don't Know JS Yet (2nd Edition)” (https://github.com/getify/You-Dont-Know-JS) by Kyle Simpson (https://github.com/getify). The book is licensed under the CC BY-NC-ND 4.0 license (https://creativecommons.org/licenses/by-nc-nd/4.0/). © 2019-2022 Kyle Simpson.</div>

Note that the CC BY-NC-ND license includes the NoDerivatives requirement, which indicates that no adaptations are allowed. You cannot make any adaptations relying on the CC BY-NC-CD license the author chose for the book. If you would like to make a translation of the book, for example, you will need to ask the author for permission first.

The CC BY-NC-ND license also includes the NonCommercial requirement. To learn more, take a look at [https://en.wikipedia.org/wiki/Creative_Commons_NonCommercial_license our guide about the NonCommercial licenses].
<hr>

=== Attributing materials from multiple sources ===

:[[File:Saylor_marking_example.jpg]]

''Let’s go through TASL:''

:'''T'''itle? Specific works are named, e.g., "Box-and-whisker Plots"

:'''A'''uthor? Different authors noted for the different works

:'''S'''ource? Original materials are linked for each work

:'''L'''icense? The different licenses (Creative Commons Attribution for Collaborative Statistics and Creative Commons Attribution-Noncommercial-ShareAlike for the Khan Academy video) are spelled out and linked for each work

:Lastly, it is clear which attribution belongs to which work.

You can visit the [http://www.saylor.org/courses/ma121/ Saylor.org Introduction to Statistics course page] to see how they marked it up directly.
<hr>

=== Publishing attribution on a separate web page ===
As stated above, recommended attribution depends on the medium you're working with. For media such as offline materials, video, audio, and images, consider publishing a web page with attribution information. For example, on a webpage featuring your audio recording, provide a credit list of material you used that adheres to best practices above. Doing so allows not only your material, but the materials you attribute, to be found by search engines and other web discovery tools. If possible within the medium, make the Author, Source, and License links the user can follow.

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">'''Example:'''<br>This video features the song [http://ccmixter.org/media/files/victor/6374 "Desaprendere (Treatment)"] by [http://fourstones.net/ fourstones], available under a Creative Commons [http://creativecommons.org/licenses/by-nc/2.5/ Attribution-Noncommercial 2.5 license].</div>

<hr>

==Attributing public domain materials==
Although attribution is not a legal obligation under [https://creativecommons.org/share-your-work/public-domain/cc0/ CC0 dedication]’s or [https://creativecommons.org/share-your-work/public-domain/pdm/ CC Public Domain Mark]’s licensing terms, we recommend that you consider including information about the hosting institution for public domain materials when it is reasonable to do so. Citing public domain works in this way not only encourages institutions to digitize and share more public domain materials in their physical collections, but also empowers users to easily locate the original source.

Here is an example of citing the source of a public domain image. The following public domain image is digitized and hosted by the Rijksmuseum (the national museum of the Netherlands). The Rijksmuseum has applied a CC0 dedication to the image.

:[[File:Attributing_the_milkmaid.png|300px]]

You may provide credit in the following format:

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">“[http://hdl.handle.net/10934/RM0001.COLLECT.6417 The Milkmaid]” by Vermeer. The Rijksmuseum collection. The image is dedicated to the public domain under [https://creativecommons.org/share-your-work/public-domain/cc0/ CC0]. </div>

In most cases, people credit the source regardless of the work’s copyright status. Especially in an academic setting, providing source information about other people’s works has long been considered crucial to academic integrity. Copyright cannot be the only checkbox when deciding whether a source will be attributed. You can learn more about [https://creativecommons.org/faq/#what-is-the-difference-between-plagiarism-and-copyright-infringement-and-what-role-do-cc-licenses-play-to-address-plagiarism how our licenses interact with academic citation standards in our FAQ].

== Common pitfalls ==

Below are some practices that you may wish to avoid. These practices are not always contrary to the Creative Commons licensing terms, but they often make it more challenging for users to find the original source and/or author.

'''Attribute in alt text'''
:Alt text is intended to provide accessible information about visual materials for users with cognitive disabilities or visual impairment. Using this field for licensing information makes browsing difficult for those users.

'''Attribute in metadata fields only'''
:While it is great to include attribution in metadata fields (such as EXIF for images), in most cases this is not the only place to include attribution information. This is because many users are likely not aware of, and will never see, attribution information included in metadata.

'''Credit authors by names other than the ones they have selected'''
:Many people believe that attribution must be given to the real name of the author of a work, but this is not the case — always give attribution to the name the author has specified, even if it is a pseudonym. If the author does not give a name or explicitly requests to be anonymous, you must give the other attribution information (i.e., “T” and “SL” from “TASL”) without crediting the author.

'''Credit a site (or Creative Commons itself!) instead of the author'''
:Unless an author specifically requests users to only credit a site, crediting the site where you have found the material cannot substitute crediting the author. An author may have uploaded material to a site under a CC license, but in most cases, the copyright is still held by the author, and it is the copyright holder who needs to be credited. For example, many photos sourced from Wikimedia Commons are attributed to Wikimedia when they must be attributed to the authors.

== Other guides to attribution ==

* [http://creativecommons.org.au/materials/attribution.pdf Attributing Creative Commons Material] (pdf) - Creative Commons Australia's publication is full of examples with colorful imagery.
* [http://www.newmediarights.org/guide/how_to/creative_commons/best_practices_creative_commons_attributions How to attribute works you reuse under a Creative Commons license] by New Media Rights provides real world examples by different media type

[[Category:Marking]]
[[Category:Licensing]]
[[Category:Community]]
[[Category:Media]]
[[Category:HOWTO]]
[[Category:Guide]]
{{Best Practice}}

Recommended practices for attribution

2022-12-07T20:41:02Z

CCID-yuanxiaoxu: /* Attributing public domain materials */

You can use CC-licensed materials as long as you follow the license conditions. One condition of all CC licenses is attribution: crediting the author and noting the source and the license. Generally speaking, attribution must reasonably include all relevant information supplied by the licensor. Because each use case is different, you can decide what form of attribution is most suitable for your specific situation. The following examples are intended to illustrate what typical prudent practices look like. We expect community norms and expectations to evolve with time, and will adapt this guide accordingly.
In addition to attribution, there are also [https://wiki.creativecommons.org/wiki/Considerations_for_licensors_and_licensees#Considerations_for_licensees|other things to consider as a licensor or a licensee]. If you are a licensor and would like to learn how to license your own material, take a look at [https://wiki.creativecommons.org/wiki/Marking_your_work_with_a_CC_license our guide on how to mark your work with a CC license].

==Basic components of attribution==

[[File:19th_century_tassel_from_Smithsonian.jpeg|290px|left]]

Whenever you are reusing CC licensed works, we recommend that the attribution include the '''T'''itle, '''A'''uthor, '''S'''ource, and '''L'''icense. This is true whether you’re sharing the work as-is or if you have made an adaptation. To remember these attribution elements, it’s helpful to think of the acronym: '''TASL'''.

Let’s now go through '''TASL''' — we will explain each element in more detail:

'''Title''': What is the name of the work?

:If a title was provided for the work, include it as a part of the attribution. Sometimes a title is not provided; in that case, there’s no need to mention the title.

:The inclusion of title is a requirement of all CC licenses version 3.0 or earlier, and it is optional for the 4.0 suites. See [https://wiki.creativecommons.org/wiki/Recommended_practices_for_attribution#License_details License details].

'''Author''': Who allows you to use the work?

:We often use “author” as a shorthand when we are, legally speaking, referring to the “licensor” (a.k.a., the “copyright holder” or “rightsholder”). This is because, in most CC-licensed works, the licensor is the same person or entity as the author. When an author is licensing their work under a CC license, and has made their name available, include the author’s name as a component in your attribution. Sometimes, the licensor may want you to give credit to some other entity, like a company or institution, or the licensor may want to be credited by a pseudonym instead of their real name. In rare cases, the licensor may not want to be attributed at all. In all of these cases, do what the licensor requests.

:Sometimes, the author will also provide a copyright notice, which consists of the copyright symbol, year of publication, and the name of the author/licensor. Include the copyright notice as a part of your attribution if such information is provided.

'''Source''': Where can people find the work?

:Please make it possible for future users to find the source of the material by including a URL or hyperlink where the work resides. This often is where you found the work. If you found it somewhere other than the original site, try to include information about the original site where the work was first shared publicly. It is also better to use the original URL instead of a shortened link, whether you are hyperlinking or printing out the entire URL.

'''License''': How can you use the work?

:You must specify which CC license was applied to the work you are reusing. Each of the six different CC licenses come with distinct requirements for re-use. We recommend that you name and provide a link to the license, e.g., [http://creativecommons.org/licenses/by/4.0 CC BY 4.0] (http://creativecommons.org/licenses/by/4.0) for a work licensed under CC BY 4.0.

:Consider also including the “disclaimer of warranties,” which clarifies that the author makes no representations or warranties about the non-infringement or absence of other defects concerning the CC-licensed work. In plain English, this means that the users will use the work at their own risk.

:To sum up, if the licensor has provided any information related to TASL, consider including them in your attribution. We also recommend providing links to the Title, Author, Source, and License, where possible, so future users can easily access the information they need on a work and the license terms.
<hr>
===Reasonable attribution===

The CC licenses ask you to be reasonable:

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 90%;">You may satisfy the attribution requirement in any reasonable manner based on the medium, means and context in which the Licensed Material is used. For example, it may be reasonable to satisfy some or all of the conditions by retaining a copyright notice, or by providing a URI or hyperlink associated with the Licensed Material, if the copyright notice or webpage includes some or all of the required information.</div>

There is no single best or correct way of attribution, as long as your attribution is reasonable and suited to the medium you're working with.
<hr>

===License details===

If you have any doubts or questions, you can read the complete attribution requirements which are spelled out in detail in the legal code of every CC license, eg. http://creativecommons.org/licenses/by/4.0/legalcode This [[License_Versions#Detailed_attribution_comparison_chart|chart compares the detailed requirements across all versions of CC licenses.]]

==Examples of attribution==

We will now look at some examples in different media.

===Attributing an image===

Here is a photo. Below, we will go over some good and bad examples of how people might attribute it.

[[File:8256206923_c77e85319e_n.jpg]]
<hr>

====This is a great attribution====
<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">
"[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Creative Commons 10th Birthday Celebration San Francisco]" by [http://www.flickr.com/photos/sixteenmilesofstring/ Timothy Vollmer] is licensed under [http://creativecommons.org/licenses/by/4.0/ CC BY 4.0]</div>

''Let’s go through TASL:''
:'''T'''itle? "Creative Commons 10th Birthday Celebration San Francisco"
:'''A'''uthor? "[http://www.flickr.com/photos/sixteenmilesofstring/ Timothy Vollmer]" - linked to his profile page
:'''S'''ource? "[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Creative Commons 10th Birthday Celebration San Francisco]" - linked to original Flickr page
:'''L'''icense? "[http://creativecommons.org/licenses/by/4.0/ CC BY 4.0]" - linked to license deed

Most importantly, this attribution reasonably includes all the relevant information provided by the author.
<hr>

====This is a pretty good attribution====

<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Photo] by Timothy Vollmer/ [http://creativecommons.org/licenses/by/2.0/ CC BY]</div>

''Let’s go through TASL:''
:'''T'''itle? Title is not noted but at least the source is linked.
:'''A'''uthor? "Timothy Vollmer"
:'''S'''ource? "[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Photo]" - linked to original Flickr page
:'''L'''icense? "[http://creativecommons.org/licenses/by/4.0/ CC BY]" - linked to license deed

As you see, a good attribution includes all the essential '''TASL''' elements, even though they may not mirror the format of credit the author has requested.
<hr>

==== This is an incorrect attribution====
<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">Photo: Creative Commons</div>

''Let’s go through TASL'':
:'''T'''itle? Title of the image is not noted
:'''A'''uthor? Author is not noted (It is a common mistake to attribute CC-licensed photos to CC, but Creative Commons is not the author!)
:'''S'''ource? No link to the original source
:'''L'''icense? There is no mention of a license nor a link to the license. "Creative Commons" is the name of an organization; it does not equate to any of the licenses maintained by the Creative Commons.
<hr>

====This is a great attribution for an image you modified slightly====
:[[File:Cropped_tvol_cupcake.png|300px]]

<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">"[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Creative Commons 10th Birthday Celebration San Francisco]" by [http://www.flickr.com/photos/sixteenmilesofstring/ Timothy Vollmer], used under [http://creativecommons.org/licenses/by/4.0/ CC BY 4.0] / Cropped from original</div>

Here, information on '''T'''itle, '''A'''uthor, '''S'''ource, and '''L'''icense are all included as requested by the author. The slight modification is also noted and briefly described.

Note if the modification changes the work’s meaning in a way that would be considered creative — that is, not a purely mechanical change or a simple crop/excerpt that keeps the original message undistorted, it would be considered creating a new adaptation of the original work. You cannot rely on a CC license that does not allow adaptation (e.g., CC BY-ND or CC BY-NC-ND) when making such modifications.

<hr>

====This is a great attribution for when you have created an adaptation====

:[[File:8256206923_c77e85319e_n_90fied.jpg|300px]]

<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">This work, "90fied", is adapted from "[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Creative Commons 10th Birthday Celebration San Francisco]" by [http://www.flickr.com/photos/sixteenmilesofstring/ Timothy Vollmer], used under [http://creativecommons.org/licenses/by/4.0/ CC BY 4.0]. "90fied" is licensed under [http://creativecommons.org/licenses/by/4.0/ CC BY 4.0] by [Your name here].</div>

''Let’s go through TASL:''

Original '''T'''itle, '''A'''uthor, '''S'''ource, and '''L'''icense are all noted.

The original work is referenced and the fact that it is an adaptation is also noted, so viewers can see what has changed.

The author and other attribution information for the new adapted work is also noted.

Note: If you're at a point where you are licensing works that are adaptations, go to [[Marking your work with a CC license]].
<hr>

===Attributing music===

====When you incorporate music in an audio or video recording====
Music (both the underlying composition and the sound recordings) — such as a song, or a recording of natural sounds — can be attributed within the audio/video, and in the description text of the audio/video. How to attribute a CC licensed music in an audio or video recording will largely depend on what is reasonable for a chosen medium and platform.

Caution: Licenses with “ND” do not allow for adaptations. Your use of CC-licensed music is often an adaptation!

It is considered adaptation if you incorporate CC-licensed music into your work in a way that the CC-licensed music can no longer be seen as a stand-alone piece. For example, if you are using a song as background music in a podcast or in a video, it is considered an adaptation of the song.

Keep in mind that CC BY-ND and CC BY-NC-ND do not allow adaptations (although you may be authorized by law to do so, such as under a users’ right like fair use, or you may ask for the author’s permission independent of the CC license).
<hr>

[[File:Smithsonian_music_stand.jpeg|left|250px]]

=====This is a great attribution of background music in a podcast or a video=====
When reasonable to do so, we recommend that you include attribution both in the description box and in the podcast recording or the video recording itself.

If you are using the following song in a podcast: ‘Day Bird’ by Broke for Free ([https://brokeforfree.com brokeforfree.com]), this would be a great way to provide attribution (which you can see in [https://soundcloud.com/wearecc/open-minds-podcast-catherine-stihler-ceo-of-creative-commons the Creative Commons podcast]) —

:At the end of the podcast audio recording, the host says:
:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 90%;">Special thanks to the musician Broke for Free, whose track “Day Bird” you heard at the beginning of this episode and you are listening to right now. It's under the Creative Commons Attribution License, meaning it's free for anyone to use. You can find it at the Free Music Archive—freemusicarchive.org</div>

:In the description box, the information text reads:
:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 90%;">Theme music: “Day Bird” by Broke for Free ([https://brokeforfree.com brokeforfree.com]). Available for use under the CC BY 3.0 license ([https://creativecommons.org/licenses/by/3.0/ creativecommons.org/licenses/by/3.0/]), at [https://freemusicarchive.org/music/Broke_For_Free/Directionless_EP/Broke_For_Free_-_Directionless_EP_-_03_Day_Bird|the Free Music Archive].</div>

''Let’s go through TASL:''

:'''T'''itle? Both the recording and the description box include the title of the work, “Day Bird”

:'''A'''uthor? "Broke for Free," again, noted both in the recording and in the description box

:'''S'''ource? Both the author’s page and the archive’s page are included with links

:'''L'''icense? "CC BY 3.0" — linked to license deed

You cannot talk over, or remix, music licensed under CC BY-ND or CC BY-NC-ND.

<hr>

=====This is a bad attribution of background music in a podcast or a video=====

A bad attribution is one where you do not provide enough information for a user to find the music you are using. The following is a bad attribution for the same song:

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">No attribution is included in the podcast recording or the video itself.

In the description box, it says: “ Creative Commons music.”</div>

''Let’s go through TASL:''

:'''T'''itle? Title is not noted

:'''A'''uthor? Author is not noted

:'''S'''ource? Source is not noted; users cannot find the specific song used in the podcast

:'''L'''icense? No information on the CC license

The attribution information is not sufficient for people to find the song you have re-used.
<hr>

====When you are not adding new elements to the music====
When you re-use music without adding new elements to it, you are not making an adaptation. In that case, you can rely on any of the CC licenses, including CC BY-ND and CC BY-NC-ND. We recommend providing attribution information in writing.

[[File:Wiki_page_attributing_night_owl.png|400px]]

On [https://commons.wikimedia.org/wiki/File:Broke_For_Free_-_01_-_Night_Owl.ogg this Wikipedia page], you can see an example of great attribution for the sharing another soundtrack, “Night Owl” by Broke for Free, when it’s without adaptation.

''Let’s go through TASL:''

'''T'''itle? Title of the work, “Night Owl,” is noted

'''A'''uthor? "Broke for Free," noted and linked to the author’s webpage

'''S'''ource? A link is provided for the source

'''L'''icense? "CC BY 3.0" — linked to license deed
<hr>

===Attributing text===
Let’s take [https://github.com/getify/You-Dont-Know-JS ''You Don't Know JS Yet'' (2nd Edition)] as an example, and go over what your attribution may look like if you reuse the book series. The information under the “License & Copyright” section looks like this on the webpage where the book series was originally shared:
:[[File:attributing_You_Don't_Know_JS_Yet_(2nd_Edition).png|200px]]

We recommend that you retain all the information provided by the author of the book series when it is reasonable for you to do so. For example, if you are distributing digital copies or excerpts of the book series in a free seminar, or using parts of the book in a free online course or presentation, the attribution will likely look something like this:

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">This chapter is from “[https://github.com/getify/You-Dont-Know-JS You Don't Know JS Yet (2nd Edition)]” by [https://github.com/getify Kyle Simpson]. The book is licensed under the [https://creativecommons.org/licenses/by-nc-nd/4.0/ CC BY-NC-ND 4.0 license]. © 2019-2022 Kyle Simpson.</div>

On the other hand, if you are distributing hard copies of the book series or excerpts from the book series, instead of using hyperlinks, you may wish to include the links so it’s easier for users to locate the original source of the book, the author, and the CC license:

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">This chapter is from “You Don't Know JS Yet (2nd Edition)” (https://github.com/getify/You-Dont-Know-JS) by Kyle Simpson (https://github.com/getify). The book is licensed under the CC BY-NC-ND 4.0 license (https://creativecommons.org/licenses/by-nc-nd/4.0/). © 2019-2022 Kyle Simpson.</div>

Note that the CC BY-NC-ND license includes the NoDerivatives requirement, which indicates that no adaptations are allowed. You cannot make any adaptations relying on the CC BY-NC-CD license the author chose for the book. If you would like to make a translation of the book, for example, you will need to ask the author for permission first.

The CC BY-NC-ND license also includes the NonCommercial requirement. To learn more, take a look at [https://en.wikipedia.org/wiki/Creative_Commons_NonCommercial_license our guide about the NonCommercial licenses].
<hr>

=== Attributing materials from multiple sources ===

:[[File:Saylor_marking_example.jpg]]

''Let’s go through TASL:''

:'''T'''itle? Specific works are named, e.g., "Box-and-whisker Plots"

:'''A'''uthor? Different authors noted for the different works

:'''S'''ource? Original materials are linked for each work

:'''L'''icense? The different licenses (Creative Commons Attribution for Collaborative Statistics and Creative Commons Attribution-Noncommercial-ShareAlike for the Khan Academy video) are spelled out and linked for each work

:Lastly, it is clear which attribution belongs to which work.

You can visit the [http://www.saylor.org/courses/ma121/ Saylor.org Introduction to Statistics course page] to see how they marked it up directly.
<hr>

=== Publishing attribution on a separate web page ===
As stated above, recommended attribution depends on the medium you're working with. For media such as offline materials, video, audio, and images, consider publishing a web page with attribution information. For example, on a webpage featuring your audio recording, provide a credit list of material you used that adheres to best practices above. Doing so allows not only your material, but the materials you attribute, to be found by search engines and other web discovery tools. If possible within the medium, make the Author, Source, and License links the user can follow.

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">'''Example:'''<br>This video features the song [http://ccmixter.org/media/files/victor/6374 "Desaprendere (Treatment)"] by [http://fourstones.net/ fourstones], available under a Creative Commons [http://creativecommons.org/licenses/by-nc/2.5/ Attribution-Noncommercial 2.5 license].</div>

<hr>

==Attributing public domain materials==
Although attribution is not a legal obligation under [https://creativecommons.org/share-your-work/public-domain/cc0/ CC0 dedication]’s or [https://creativecommons.org/share-your-work/public-domain/pdm/ CC Public Domain Mark]’s licensing terms, we recommend that you consider including information about the hosting institution for public domain materials when it is reasonable to do so. Citing public domain works in this way not only encourages institutions to digitize and share more public domain materials in their physical collections, but also empowers users to easily locate the original source.

Here is an example of citing the source of a public domain image.

The following public domain image is digitized and hosted by the Rijksmuseum (the national museum of the Netherlands). The Rijksmuseum has applied a CC0 dedication to the image.

:[[File:Attributing_the_milkmaid.png|300px]]

You may provide credit in the following format:

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">“[http://hdl.handle.net/10934/RM0001.COLLECT.6417 The Milkmaid]” by Vermeer. The Rijksmuseum collection. The image is dedicated to the public domain under [https://creativecommons.org/share-your-work/public-domain/cc0/ CC0]. </div>

In most cases, people credit the source regardless of the work’s copyright status. Especially in an academic setting, providing source information about other people’s works has long been considered crucial to academic integrity. Copyright cannot be the only checkbox when deciding whether a source will be attributed. You can learn more about [https://creativecommons.org/faq/#what-is-the-difference-between-plagiarism-and-copyright-infringement-and-what-role-do-cc-licenses-play-to-address-plagiarism how our licenses interact with academic citation standards in our FAQ].

== Common pitfalls ==

Below are some practices that you may wish to avoid. These practices are not always contrary to the Creative Commons licensing terms, but they often make it more challenging for users to find the original source and/or author.

'''Attribute in alt text'''
:Alt text is intended to provide accessible information about visual materials for users with cognitive disabilities or visual impairment. Using this field for licensing information makes browsing difficult for those users.

'''Attribute in metadata fields only'''
:While it is great to include attribution in metadata fields (such as EXIF for images), in most cases this is not the only place to include attribution information. This is because many users are likely not aware of, and will never see, attribution information included in metadata.

'''Credit authors by names other than the ones they have selected'''
:Many people believe that attribution must be given to the real name of the author of a work, but this is not the case — always give attribution to the name the author has specified, even if it is a pseudonym. If the author does not give a name or explicitly requests to be anonymous, you must give the other attribution information (i.e., “T” and “SL” from “TASL”) without crediting the author.

'''Credit a site (or Creative Commons itself!) instead of the author'''
:Unless an author specifically requests users to only credit a site, crediting the site where you have found the material cannot substitute crediting the author. An author may have uploaded material to a site under a CC license, but in most cases, the copyright is still held by the author, and it is the copyright holder who needs to be credited. For example, many photos sourced from Wikimedia Commons are attributed to Wikimedia when they must be attributed to the authors.

== Other guides to attribution ==

* [http://creativecommons.org.au/materials/attribution.pdf Attributing Creative Commons Material] (pdf) - Creative Commons Australia's publication is full of examples with colorful imagery.
* [http://www.newmediarights.org/guide/how_to/creative_commons/best_practices_creative_commons_attributions How to attribute works you reuse under a Creative Commons license] by New Media Rights provides real world examples by different media type

[[Category:Marking]]
[[Category:Licensing]]
[[Category:Community]]
[[Category:Media]]
[[Category:HOWTO]]
[[Category:Guide]]
{{Best Practice}}

Recommended practices for attribution

2022-12-07T20:40:09Z

CCID-yuanxiaoxu: /* Attributing public domain materials */

You can use CC-licensed materials as long as you follow the license conditions. One condition of all CC licenses is attribution: crediting the author and noting the source and the license. Generally speaking, attribution must reasonably include all relevant information supplied by the licensor. Because each use case is different, you can decide what form of attribution is most suitable for your specific situation. The following examples are intended to illustrate what typical prudent practices look like. We expect community norms and expectations to evolve with time, and will adapt this guide accordingly.
In addition to attribution, there are also [https://wiki.creativecommons.org/wiki/Considerations_for_licensors_and_licensees#Considerations_for_licensees|other things to consider as a licensor or a licensee]. If you are a licensor and would like to learn how to license your own material, take a look at [https://wiki.creativecommons.org/wiki/Marking_your_work_with_a_CC_license our guide on how to mark your work with a CC license].

==Basic components of attribution==

[[File:19th_century_tassel_from_Smithsonian.jpeg|290px|left]]

Whenever you are reusing CC licensed works, we recommend that the attribution include the '''T'''itle, '''A'''uthor, '''S'''ource, and '''L'''icense. This is true whether you’re sharing the work as-is or if you have made an adaptation. To remember these attribution elements, it’s helpful to think of the acronym: '''TASL'''.

Let’s now go through '''TASL''' — we will explain each element in more detail:

'''Title''': What is the name of the work?

:If a title was provided for the work, include it as a part of the attribution. Sometimes a title is not provided; in that case, there’s no need to mention the title.

:The inclusion of title is a requirement of all CC licenses version 3.0 or earlier, and it is optional for the 4.0 suites. See [https://wiki.creativecommons.org/wiki/Recommended_practices_for_attribution#License_details License details].

'''Author''': Who allows you to use the work?

:We often use “author” as a shorthand when we are, legally speaking, referring to the “licensor” (a.k.a., the “copyright holder” or “rightsholder”). This is because, in most CC-licensed works, the licensor is the same person or entity as the author. When an author is licensing their work under a CC license, and has made their name available, include the author’s name as a component in your attribution. Sometimes, the licensor may want you to give credit to some other entity, like a company or institution, or the licensor may want to be credited by a pseudonym instead of their real name. In rare cases, the licensor may not want to be attributed at all. In all of these cases, do what the licensor requests.

:Sometimes, the author will also provide a copyright notice, which consists of the copyright symbol, year of publication, and the name of the author/licensor. Include the copyright notice as a part of your attribution if such information is provided.

'''Source''': Where can people find the work?

:Please make it possible for future users to find the source of the material by including a URL or hyperlink where the work resides. This often is where you found the work. If you found it somewhere other than the original site, try to include information about the original site where the work was first shared publicly. It is also better to use the original URL instead of a shortened link, whether you are hyperlinking or printing out the entire URL.

'''License''': How can you use the work?

:You must specify which CC license was applied to the work you are reusing. Each of the six different CC licenses come with distinct requirements for re-use. We recommend that you name and provide a link to the license, e.g., [http://creativecommons.org/licenses/by/4.0 CC BY 4.0] (http://creativecommons.org/licenses/by/4.0) for a work licensed under CC BY 4.0.

:Consider also including the “disclaimer of warranties,” which clarifies that the author makes no representations or warranties about the non-infringement or absence of other defects concerning the CC-licensed work. In plain English, this means that the users will use the work at their own risk.

:To sum up, if the licensor has provided any information related to TASL, consider including them in your attribution. We also recommend providing links to the Title, Author, Source, and License, where possible, so future users can easily access the information they need on a work and the license terms.
<hr>
===Reasonable attribution===

The CC licenses ask you to be reasonable:

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 90%;">You may satisfy the attribution requirement in any reasonable manner based on the medium, means and context in which the Licensed Material is used. For example, it may be reasonable to satisfy some or all of the conditions by retaining a copyright notice, or by providing a URI or hyperlink associated with the Licensed Material, if the copyright notice or webpage includes some or all of the required information.</div>

There is no single best or correct way of attribution, as long as your attribution is reasonable and suited to the medium you're working with.
<hr>

===License details===

If you have any doubts or questions, you can read the complete attribution requirements which are spelled out in detail in the legal code of every CC license, eg. http://creativecommons.org/licenses/by/4.0/legalcode This [[License_Versions#Detailed_attribution_comparison_chart|chart compares the detailed requirements across all versions of CC licenses.]]

==Examples of attribution==

We will now look at some examples in different media.

===Attributing an image===

Here is a photo. Below, we will go over some good and bad examples of how people might attribute it.

[[File:8256206923_c77e85319e_n.jpg]]
<hr>

====This is a great attribution====
<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">
"[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Creative Commons 10th Birthday Celebration San Francisco]" by [http://www.flickr.com/photos/sixteenmilesofstring/ Timothy Vollmer] is licensed under [http://creativecommons.org/licenses/by/4.0/ CC BY 4.0]</div>

''Let’s go through TASL:''
:'''T'''itle? "Creative Commons 10th Birthday Celebration San Francisco"
:'''A'''uthor? "[http://www.flickr.com/photos/sixteenmilesofstring/ Timothy Vollmer]" - linked to his profile page
:'''S'''ource? "[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Creative Commons 10th Birthday Celebration San Francisco]" - linked to original Flickr page
:'''L'''icense? "[http://creativecommons.org/licenses/by/4.0/ CC BY 4.0]" - linked to license deed

Most importantly, this attribution reasonably includes all the relevant information provided by the author.
<hr>

====This is a pretty good attribution====

<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Photo] by Timothy Vollmer/ [http://creativecommons.org/licenses/by/2.0/ CC BY]</div>

''Let’s go through TASL:''
:'''T'''itle? Title is not noted but at least the source is linked.
:'''A'''uthor? "Timothy Vollmer"
:'''S'''ource? "[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Photo]" - linked to original Flickr page
:'''L'''icense? "[http://creativecommons.org/licenses/by/4.0/ CC BY]" - linked to license deed

As you see, a good attribution includes all the essential '''TASL''' elements, even though they may not mirror the format of credit the author has requested.
<hr>

==== This is an incorrect attribution====
<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">Photo: Creative Commons</div>

''Let’s go through TASL'':
:'''T'''itle? Title of the image is not noted
:'''A'''uthor? Author is not noted (It is a common mistake to attribute CC-licensed photos to CC, but Creative Commons is not the author!)
:'''S'''ource? No link to the original source
:'''L'''icense? There is no mention of a license nor a link to the license. "Creative Commons" is the name of an organization; it does not equate to any of the licenses maintained by the Creative Commons.
<hr>

====This is a great attribution for an image you modified slightly====
:[[File:Cropped_tvol_cupcake.png|300px]]

<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">"[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Creative Commons 10th Birthday Celebration San Francisco]" by [http://www.flickr.com/photos/sixteenmilesofstring/ Timothy Vollmer], used under [http://creativecommons.org/licenses/by/4.0/ CC BY 4.0] / Cropped from original</div>

Here, information on '''T'''itle, '''A'''uthor, '''S'''ource, and '''L'''icense are all included as requested by the author. The slight modification is also noted and briefly described.

Note if the modification changes the work’s meaning in a way that would be considered creative — that is, not a purely mechanical change or a simple crop/excerpt that keeps the original message undistorted, it would be considered creating a new adaptation of the original work. You cannot rely on a CC license that does not allow adaptation (e.g., CC BY-ND or CC BY-NC-ND) when making such modifications.

<hr>

====This is a great attribution for when you have created an adaptation====

:[[File:8256206923_c77e85319e_n_90fied.jpg|300px]]

<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">This work, "90fied", is adapted from "[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Creative Commons 10th Birthday Celebration San Francisco]" by [http://www.flickr.com/photos/sixteenmilesofstring/ Timothy Vollmer], used under [http://creativecommons.org/licenses/by/4.0/ CC BY 4.0]. "90fied" is licensed under [http://creativecommons.org/licenses/by/4.0/ CC BY 4.0] by [Your name here].</div>

''Let’s go through TASL:''

Original '''T'''itle, '''A'''uthor, '''S'''ource, and '''L'''icense are all noted.

The original work is referenced and the fact that it is an adaptation is also noted, so viewers can see what has changed.

The author and other attribution information for the new adapted work is also noted.

Note: If you're at a point where you are licensing works that are adaptations, go to [[Marking your work with a CC license]].
<hr>

===Attributing music===

====When you incorporate music in an audio or video recording====
Music (both the underlying composition and the sound recordings) — such as a song, or a recording of natural sounds — can be attributed within the audio/video, and in the description text of the audio/video. How to attribute a CC licensed music in an audio or video recording will largely depend on what is reasonable for a chosen medium and platform.

Caution: Licenses with “ND” do not allow for adaptations. Your use of CC-licensed music is often an adaptation!

It is considered adaptation if you incorporate CC-licensed music into your work in a way that the CC-licensed music can no longer be seen as a stand-alone piece. For example, if you are using a song as background music in a podcast or in a video, it is considered an adaptation of the song.

Keep in mind that CC BY-ND and CC BY-NC-ND do not allow adaptations (although you may be authorized by law to do so, such as under a users’ right like fair use, or you may ask for the author’s permission independent of the CC license).
<hr>

[[File:Smithsonian_music_stand.jpeg|left|250px]]

=====This is a great attribution of background music in a podcast or a video=====
When reasonable to do so, we recommend that you include attribution both in the description box and in the podcast recording or the video recording itself.

If you are using the following song in a podcast: ‘Day Bird’ by Broke for Free ([https://brokeforfree.com brokeforfree.com]), this would be a great way to provide attribution (which you can see in [https://soundcloud.com/wearecc/open-minds-podcast-catherine-stihler-ceo-of-creative-commons the Creative Commons podcast]) —

:At the end of the podcast audio recording, the host says:
:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 90%;">Special thanks to the musician Broke for Free, whose track “Day Bird” you heard at the beginning of this episode and you are listening to right now. It's under the Creative Commons Attribution License, meaning it's free for anyone to use. You can find it at the Free Music Archive—freemusicarchive.org</div>

:In the description box, the information text reads:
:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 90%;">Theme music: “Day Bird” by Broke for Free ([https://brokeforfree.com brokeforfree.com]). Available for use under the CC BY 3.0 license ([https://creativecommons.org/licenses/by/3.0/ creativecommons.org/licenses/by/3.0/]), at [https://freemusicarchive.org/music/Broke_For_Free/Directionless_EP/Broke_For_Free_-_Directionless_EP_-_03_Day_Bird|the Free Music Archive].</div>

''Let’s go through TASL:''

:'''T'''itle? Both the recording and the description box include the title of the work, “Day Bird”

:'''A'''uthor? "Broke for Free," again, noted both in the recording and in the description box

:'''S'''ource? Both the author’s page and the archive’s page are included with links

:'''L'''icense? "CC BY 3.0" — linked to license deed

You cannot talk over, or remix, music licensed under CC BY-ND or CC BY-NC-ND.

<hr>

=====This is a bad attribution of background music in a podcast or a video=====

A bad attribution is one where you do not provide enough information for a user to find the music you are using. The following is a bad attribution for the same song:

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">No attribution is included in the podcast recording or the video itself.

In the description box, it says: “ Creative Commons music.”</div>

''Let’s go through TASL:''

:'''T'''itle? Title is not noted

:'''A'''uthor? Author is not noted

:'''S'''ource? Source is not noted; users cannot find the specific song used in the podcast

:'''L'''icense? No information on the CC license

The attribution information is not sufficient for people to find the song you have re-used.
<hr>

====When you are not adding new elements to the music====
When you re-use music without adding new elements to it, you are not making an adaptation. In that case, you can rely on any of the CC licenses, including CC BY-ND and CC BY-NC-ND. We recommend providing attribution information in writing.

[[File:Wiki_page_attributing_night_owl.png|400px]]

On [https://commons.wikimedia.org/wiki/File:Broke_For_Free_-_01_-_Night_Owl.ogg this Wikipedia page], you can see an example of great attribution for the sharing another soundtrack, “Night Owl” by Broke for Free, when it’s without adaptation.

''Let’s go through TASL:''

'''T'''itle? Title of the work, “Night Owl,” is noted

'''A'''uthor? "Broke for Free," noted and linked to the author’s webpage

'''S'''ource? A link is provided for the source

'''L'''icense? "CC BY 3.0" — linked to license deed
<hr>

===Attributing text===
Let’s take [https://github.com/getify/You-Dont-Know-JS ''You Don't Know JS Yet'' (2nd Edition)] as an example, and go over what your attribution may look like if you reuse the book series. The information under the “License & Copyright” section looks like this on the webpage where the book series was originally shared:
:[[File:attributing_You_Don't_Know_JS_Yet_(2nd_Edition).png|200px]]

We recommend that you retain all the information provided by the author of the book series when it is reasonable for you to do so. For example, if you are distributing digital copies or excerpts of the book series in a free seminar, or using parts of the book in a free online course or presentation, the attribution will likely look something like this:

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">This chapter is from “[https://github.com/getify/You-Dont-Know-JS You Don't Know JS Yet (2nd Edition)]” by [https://github.com/getify Kyle Simpson]. The book is licensed under the [https://creativecommons.org/licenses/by-nc-nd/4.0/ CC BY-NC-ND 4.0 license]. © 2019-2022 Kyle Simpson.</div>

On the other hand, if you are distributing hard copies of the book series or excerpts from the book series, instead of using hyperlinks, you may wish to include the links so it’s easier for users to locate the original source of the book, the author, and the CC license:

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">This chapter is from “You Don't Know JS Yet (2nd Edition)” (https://github.com/getify/You-Dont-Know-JS) by Kyle Simpson (https://github.com/getify). The book is licensed under the CC BY-NC-ND 4.0 license (https://creativecommons.org/licenses/by-nc-nd/4.0/). © 2019-2022 Kyle Simpson.</div>

Note that the CC BY-NC-ND license includes the NoDerivatives requirement, which indicates that no adaptations are allowed. You cannot make any adaptations relying on the CC BY-NC-CD license the author chose for the book. If you would like to make a translation of the book, for example, you will need to ask the author for permission first.

The CC BY-NC-ND license also includes the NonCommercial requirement. To learn more, take a look at [https://en.wikipedia.org/wiki/Creative_Commons_NonCommercial_license our guide about the NonCommercial licenses].
<hr>

=== Attributing materials from multiple sources ===

:[[File:Saylor_marking_example.jpg]]

''Let’s go through TASL:''

:'''T'''itle? Specific works are named, e.g., "Box-and-whisker Plots"

:'''A'''uthor? Different authors noted for the different works

:'''S'''ource? Original materials are linked for each work

:'''L'''icense? The different licenses (Creative Commons Attribution for Collaborative Statistics and Creative Commons Attribution-Noncommercial-ShareAlike for the Khan Academy video) are spelled out and linked for each work

:Lastly, it is clear which attribution belongs to which work.

You can visit the [http://www.saylor.org/courses/ma121/ Saylor.org Introduction to Statistics course page] to see how they marked it up directly.
<hr>

=== Publishing attribution on a separate web page ===
As stated above, recommended attribution depends on the medium you're working with. For media such as offline materials, video, audio, and images, consider publishing a web page with attribution information. For example, on a webpage featuring your audio recording, provide a credit list of material you used that adheres to best practices above. Doing so allows not only your material, but the materials you attribute, to be found by search engines and other web discovery tools. If possible within the medium, make the Author, Source, and License links the user can follow.

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">'''Example:'''<br>This video features the song [http://ccmixter.org/media/files/victor/6374 "Desaprendere (Treatment)"] by [http://fourstones.net/ fourstones], available under a Creative Commons [http://creativecommons.org/licenses/by-nc/2.5/ Attribution-Noncommercial 2.5 license].</div>

<hr>

==Attributing public domain materials==
Although attribution is not a legal obligation under [https://creativecommons.org/share-your-work/public-domain/cc0/ CC0 dedication]’s or [https://creativecommons.org/share-your-work/public-domain/pdm/ CC Public Domain Mark]’s licensing terms, we recommend that you consider including information about the hosting institution for public domain materials when it is reasonable to do so. Citing public domain works in this way not only encourages institutions to digitize and share more public domain materials in their physical collections, but also empowers users to easily locate the original source.

The following public domain image is digitized and hosted by the Rijksmuseum (the national museum of the Netherlands). The Rijksmuseum has applied a CC0 dedication to the image.

:[[File:Attributing_the_milkmaid.png|300px]]

You may provide credit in the following format:

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">“[http://hdl.handle.net/10934/RM0001.COLLECT.6417 The Milkmaid]” by Vermeer. The Rijksmuseum collection. The image is dedicated to the public domain under [https://creativecommons.org/share-your-work/public-domain/cc0/ CC0]. </div>

In most cases, people credit the source regardless of the work’s copyright status. Especially in an academic setting, providing source information about other people’s works has long been considered crucial to academic integrity. Copyright cannot be the only checkbox when deciding whether a source will be attributed. You can learn more about [https://creativecommons.org/faq/#what-is-the-difference-between-plagiarism-and-copyright-infringement-and-what-role-do-cc-licenses-play-to-address-plagiarism how our licenses interact with academic citation standards in our FAQ].

== Common pitfalls ==

Below are some practices that you may wish to avoid. These practices are not always contrary to the Creative Commons licensing terms, but they often make it more challenging for users to find the original source and/or author.

'''Attribute in alt text'''
:Alt text is intended to provide accessible information about visual materials for users with cognitive disabilities or visual impairment. Using this field for licensing information makes browsing difficult for those users.

'''Attribute in metadata fields only'''
:While it is great to include attribution in metadata fields (such as EXIF for images), in most cases this is not the only place to include attribution information. This is because many users are likely not aware of, and will never see, attribution information included in metadata.

'''Credit authors by names other than the ones they have selected'''
:Many people believe that attribution must be given to the real name of the author of a work, but this is not the case — always give attribution to the name the author has specified, even if it is a pseudonym. If the author does not give a name or explicitly requests to be anonymous, you must give the other attribution information (i.e., “T” and “SL” from “TASL”) without crediting the author.

'''Credit a site (or Creative Commons itself!) instead of the author'''
:Unless an author specifically requests users to only credit a site, crediting the site where you have found the material cannot substitute crediting the author. An author may have uploaded material to a site under a CC license, but in most cases, the copyright is still held by the author, and it is the copyright holder who needs to be credited. For example, many photos sourced from Wikimedia Commons are attributed to Wikimedia when they must be attributed to the authors.

== Other guides to attribution ==

* [http://creativecommons.org.au/materials/attribution.pdf Attributing Creative Commons Material] (pdf) - Creative Commons Australia's publication is full of examples with colorful imagery.
* [http://www.newmediarights.org/guide/how_to/creative_commons/best_practices_creative_commons_attributions How to attribute works you reuse under a Creative Commons license] by New Media Rights provides real world examples by different media type

[[Category:Marking]]
[[Category:Licensing]]
[[Category:Community]]
[[Category:Media]]
[[Category:HOWTO]]
[[Category:Guide]]
{{Best Practice}}

Recommended practices for attribution

2022-12-07T20:30:21Z

CCID-yuanxiaoxu: /* Publishing attribution on a separate web page */

You can use CC-licensed materials as long as you follow the license conditions. One condition of all CC licenses is attribution: crediting the author and noting the source and the license. Generally speaking, attribution must reasonably include all relevant information supplied by the licensor. Because each use case is different, you can decide what form of attribution is most suitable for your specific situation. The following examples are intended to illustrate what typical prudent practices look like. We expect community norms and expectations to evolve with time, and will adapt this guide accordingly.
In addition to attribution, there are also [https://wiki.creativecommons.org/wiki/Considerations_for_licensors_and_licensees#Considerations_for_licensees|other things to consider as a licensor or a licensee]. If you are a licensor and would like to learn how to license your own material, take a look at [https://wiki.creativecommons.org/wiki/Marking_your_work_with_a_CC_license our guide on how to mark your work with a CC license].

==Basic components of attribution==

[[File:19th_century_tassel_from_Smithsonian.jpeg|290px|left]]

Whenever you are reusing CC licensed works, we recommend that the attribution include the '''T'''itle, '''A'''uthor, '''S'''ource, and '''L'''icense. This is true whether you’re sharing the work as-is or if you have made an adaptation. To remember these attribution elements, it’s helpful to think of the acronym: '''TASL'''.

Let’s now go through '''TASL''' — we will explain each element in more detail:

'''Title''': What is the name of the work?

:If a title was provided for the work, include it as a part of the attribution. Sometimes a title is not provided; in that case, there’s no need to mention the title.

:The inclusion of title is a requirement of all CC licenses version 3.0 or earlier, and it is optional for the 4.0 suites. See [https://wiki.creativecommons.org/wiki/Recommended_practices_for_attribution#License_details License details].

'''Author''': Who allows you to use the work?

:We often use “author” as a shorthand when we are, legally speaking, referring to the “licensor” (a.k.a., the “copyright holder” or “rightsholder”). This is because, in most CC-licensed works, the licensor is the same person or entity as the author. When an author is licensing their work under a CC license, and has made their name available, include the author’s name as a component in your attribution. Sometimes, the licensor may want you to give credit to some other entity, like a company or institution, or the licensor may want to be credited by a pseudonym instead of their real name. In rare cases, the licensor may not want to be attributed at all. In all of these cases, do what the licensor requests.

:Sometimes, the author will also provide a copyright notice, which consists of the copyright symbol, year of publication, and the name of the author/licensor. Include the copyright notice as a part of your attribution if such information is provided.

'''Source''': Where can people find the work?

:Please make it possible for future users to find the source of the material by including a URL or hyperlink where the work resides. This often is where you found the work. If you found it somewhere other than the original site, try to include information about the original site where the work was first shared publicly. It is also better to use the original URL instead of a shortened link, whether you are hyperlinking or printing out the entire URL.

'''License''': How can you use the work?

:You must specify which CC license was applied to the work you are reusing. Each of the six different CC licenses come with distinct requirements for re-use. We recommend that you name and provide a link to the license, e.g., [http://creativecommons.org/licenses/by/4.0 CC BY 4.0] (http://creativecommons.org/licenses/by/4.0) for a work licensed under CC BY 4.0.

:Consider also including the “disclaimer of warranties,” which clarifies that the author makes no representations or warranties about the non-infringement or absence of other defects concerning the CC-licensed work. In plain English, this means that the users will use the work at their own risk.

:To sum up, if the licensor has provided any information related to TASL, consider including them in your attribution. We also recommend providing links to the Title, Author, Source, and License, where possible, so future users can easily access the information they need on a work and the license terms.
<hr>
===Reasonable attribution===

The CC licenses ask you to be reasonable:

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 90%;">You may satisfy the attribution requirement in any reasonable manner based on the medium, means and context in which the Licensed Material is used. For example, it may be reasonable to satisfy some or all of the conditions by retaining a copyright notice, or by providing a URI or hyperlink associated with the Licensed Material, if the copyright notice or webpage includes some or all of the required information.</div>

There is no single best or correct way of attribution, as long as your attribution is reasonable and suited to the medium you're working with.
<hr>

===License details===

If you have any doubts or questions, you can read the complete attribution requirements which are spelled out in detail in the legal code of every CC license, eg. http://creativecommons.org/licenses/by/4.0/legalcode This [[License_Versions#Detailed_attribution_comparison_chart|chart compares the detailed requirements across all versions of CC licenses.]]

==Examples of attribution==

We will now look at some examples in different media.

===Attributing an image===

Here is a photo. Below, we will go over some good and bad examples of how people might attribute it.

[[File:8256206923_c77e85319e_n.jpg]]
<hr>

====This is a great attribution====
<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">
"[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Creative Commons 10th Birthday Celebration San Francisco]" by [http://www.flickr.com/photos/sixteenmilesofstring/ Timothy Vollmer] is licensed under [http://creativecommons.org/licenses/by/4.0/ CC BY 4.0]</div>

''Let’s go through TASL:''
:'''T'''itle? "Creative Commons 10th Birthday Celebration San Francisco"
:'''A'''uthor? "[http://www.flickr.com/photos/sixteenmilesofstring/ Timothy Vollmer]" - linked to his profile page
:'''S'''ource? "[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Creative Commons 10th Birthday Celebration San Francisco]" - linked to original Flickr page
:'''L'''icense? "[http://creativecommons.org/licenses/by/4.0/ CC BY 4.0]" - linked to license deed

Most importantly, this attribution reasonably includes all the relevant information provided by the author.
<hr>

====This is a pretty good attribution====

<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Photo] by Timothy Vollmer/ [http://creativecommons.org/licenses/by/2.0/ CC BY]</div>

''Let’s go through TASL:''
:'''T'''itle? Title is not noted but at least the source is linked.
:'''A'''uthor? "Timothy Vollmer"
:'''S'''ource? "[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Photo]" - linked to original Flickr page
:'''L'''icense? "[http://creativecommons.org/licenses/by/4.0/ CC BY]" - linked to license deed

As you see, a good attribution includes all the essential '''TASL''' elements, even though they may not mirror the format of credit the author has requested.
<hr>

==== This is an incorrect attribution====
<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">Photo: Creative Commons</div>

''Let’s go through TASL'':
:'''T'''itle? Title of the image is not noted
:'''A'''uthor? Author is not noted (It is a common mistake to attribute CC-licensed photos to CC, but Creative Commons is not the author!)
:'''S'''ource? No link to the original source
:'''L'''icense? There is no mention of a license nor a link to the license. "Creative Commons" is the name of an organization; it does not equate to any of the licenses maintained by the Creative Commons.
<hr>

====This is a great attribution for an image you modified slightly====
:[[File:Cropped_tvol_cupcake.png|300px]]

<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">"[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Creative Commons 10th Birthday Celebration San Francisco]" by [http://www.flickr.com/photos/sixteenmilesofstring/ Timothy Vollmer], used under [http://creativecommons.org/licenses/by/4.0/ CC BY 4.0] / Cropped from original</div>

Here, information on '''T'''itle, '''A'''uthor, '''S'''ource, and '''L'''icense are all included as requested by the author. The slight modification is also noted and briefly described.

Note if the modification changes the work’s meaning in a way that would be considered creative — that is, not a purely mechanical change or a simple crop/excerpt that keeps the original message undistorted, it would be considered creating a new adaptation of the original work. You cannot rely on a CC license that does not allow adaptation (e.g., CC BY-ND or CC BY-NC-ND) when making such modifications.

<hr>

====This is a great attribution for when you have created an adaptation====

:[[File:8256206923_c77e85319e_n_90fied.jpg|300px]]

<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">This work, "90fied", is adapted from "[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Creative Commons 10th Birthday Celebration San Francisco]" by [http://www.flickr.com/photos/sixteenmilesofstring/ Timothy Vollmer], used under [http://creativecommons.org/licenses/by/4.0/ CC BY 4.0]. "90fied" is licensed under [http://creativecommons.org/licenses/by/4.0/ CC BY 4.0] by [Your name here].</div>

''Let’s go through TASL:''

Original '''T'''itle, '''A'''uthor, '''S'''ource, and '''L'''icense are all noted.

The original work is referenced and the fact that it is an adaptation is also noted, so viewers can see what has changed.

The author and other attribution information for the new adapted work is also noted.

Note: If you're at a point where you are licensing works that are adaptations, go to [[Marking your work with a CC license]].
<hr>

===Attributing music===

====When you incorporate music in an audio or video recording====
Music (both the underlying composition and the sound recordings) — such as a song, or a recording of natural sounds — can be attributed within the audio/video, and in the description text of the audio/video. How to attribute a CC licensed music in an audio or video recording will largely depend on what is reasonable for a chosen medium and platform.

Caution: Licenses with “ND” do not allow for adaptations. Your use of CC-licensed music is often an adaptation!

It is considered adaptation if you incorporate CC-licensed music into your work in a way that the CC-licensed music can no longer be seen as a stand-alone piece. For example, if you are using a song as background music in a podcast or in a video, it is considered an adaptation of the song.

Keep in mind that CC BY-ND and CC BY-NC-ND do not allow adaptations (although you may be authorized by law to do so, such as under a users’ right like fair use, or you may ask for the author’s permission independent of the CC license).
<hr>

[[File:Smithsonian_music_stand.jpeg|left|250px]]

=====This is a great attribution of background music in a podcast or a video=====
When reasonable to do so, we recommend that you include attribution both in the description box and in the podcast recording or the video recording itself.

If you are using the following song in a podcast: ‘Day Bird’ by Broke for Free ([https://brokeforfree.com brokeforfree.com]), this would be a great way to provide attribution (which you can see in [https://soundcloud.com/wearecc/open-minds-podcast-catherine-stihler-ceo-of-creative-commons the Creative Commons podcast]) —

:At the end of the podcast audio recording, the host says:
:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 90%;">Special thanks to the musician Broke for Free, whose track “Day Bird” you heard at the beginning of this episode and you are listening to right now. It's under the Creative Commons Attribution License, meaning it's free for anyone to use. You can find it at the Free Music Archive—freemusicarchive.org</div>

:In the description box, the information text reads:
:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 90%;">Theme music: “Day Bird” by Broke for Free ([https://brokeforfree.com brokeforfree.com]). Available for use under the CC BY 3.0 license ([https://creativecommons.org/licenses/by/3.0/ creativecommons.org/licenses/by/3.0/]), at [https://freemusicarchive.org/music/Broke_For_Free/Directionless_EP/Broke_For_Free_-_Directionless_EP_-_03_Day_Bird|the Free Music Archive].</div>

''Let’s go through TASL:''

:'''T'''itle? Both the recording and the description box include the title of the work, “Day Bird”

:'''A'''uthor? "Broke for Free," again, noted both in the recording and in the description box

:'''S'''ource? Both the author’s page and the archive’s page are included with links

:'''L'''icense? "CC BY 3.0" — linked to license deed

You cannot talk over, or remix, music licensed under CC BY-ND or CC BY-NC-ND.

<hr>

=====This is a bad attribution of background music in a podcast or a video=====

A bad attribution is one where you do not provide enough information for a user to find the music you are using. The following is a bad attribution for the same song:

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">No attribution is included in the podcast recording or the video itself.

In the description box, it says: “ Creative Commons music.”</div>

''Let’s go through TASL:''

:'''T'''itle? Title is not noted

:'''A'''uthor? Author is not noted

:'''S'''ource? Source is not noted; users cannot find the specific song used in the podcast

:'''L'''icense? No information on the CC license

The attribution information is not sufficient for people to find the song you have re-used.
<hr>

====When you are not adding new elements to the music====
When you re-use music without adding new elements to it, you are not making an adaptation. In that case, you can rely on any of the CC licenses, including CC BY-ND and CC BY-NC-ND. We recommend providing attribution information in writing.

[[File:Wiki_page_attributing_night_owl.png|400px]]

On [https://commons.wikimedia.org/wiki/File:Broke_For_Free_-_01_-_Night_Owl.ogg this Wikipedia page], you can see an example of great attribution for the sharing another soundtrack, “Night Owl” by Broke for Free, when it’s without adaptation.

''Let’s go through TASL:''

'''T'''itle? Title of the work, “Night Owl,” is noted

'''A'''uthor? "Broke for Free," noted and linked to the author’s webpage

'''S'''ource? A link is provided for the source

'''L'''icense? "CC BY 3.0" — linked to license deed
<hr>

===Attributing text===
Let’s take [https://github.com/getify/You-Dont-Know-JS ''You Don't Know JS Yet'' (2nd Edition)] as an example, and go over what your attribution may look like if you reuse the book series. The information under the “License & Copyright” section looks like this on the webpage where the book series was originally shared:
:[[File:attributing_You_Don't_Know_JS_Yet_(2nd_Edition).png|200px]]

We recommend that you retain all the information provided by the author of the book series when it is reasonable for you to do so. For example, if you are distributing digital copies or excerpts of the book series in a free seminar, or using parts of the book in a free online course or presentation, the attribution will likely look something like this:

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">This chapter is from “[https://github.com/getify/You-Dont-Know-JS You Don't Know JS Yet (2nd Edition)]” by [https://github.com/getify Kyle Simpson]. The book is licensed under the [https://creativecommons.org/licenses/by-nc-nd/4.0/ CC BY-NC-ND 4.0 license]. © 2019-2022 Kyle Simpson.</div>

On the other hand, if you are distributing hard copies of the book series or excerpts from the book series, instead of using hyperlinks, you may wish to include the links so it’s easier for users to locate the original source of the book, the author, and the CC license:

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">This chapter is from “You Don't Know JS Yet (2nd Edition)” (https://github.com/getify/You-Dont-Know-JS) by Kyle Simpson (https://github.com/getify). The book is licensed under the CC BY-NC-ND 4.0 license (https://creativecommons.org/licenses/by-nc-nd/4.0/). © 2019-2022 Kyle Simpson.</div>

Note that the CC BY-NC-ND license includes the NoDerivatives requirement, which indicates that no adaptations are allowed. You cannot make any adaptations relying on the CC BY-NC-CD license the author chose for the book. If you would like to make a translation of the book, for example, you will need to ask the author for permission first.

The CC BY-NC-ND license also includes the NonCommercial requirement. To learn more, take a look at [https://en.wikipedia.org/wiki/Creative_Commons_NonCommercial_license our guide about the NonCommercial licenses].
<hr>

=== Attributing materials from multiple sources ===

:[[File:Saylor_marking_example.jpg]]

''Let’s go through TASL:''

:'''T'''itle? Specific works are named, e.g., "Box-and-whisker Plots"

:'''A'''uthor? Different authors noted for the different works

:'''S'''ource? Original materials are linked for each work

:'''L'''icense? The different licenses (Creative Commons Attribution for Collaborative Statistics and Creative Commons Attribution-Noncommercial-ShareAlike for the Khan Academy video) are spelled out and linked for each work

:Lastly, it is clear which attribution belongs to which work.

You can visit the [http://www.saylor.org/courses/ma121/ Saylor.org Introduction to Statistics course page] to see how they marked it up directly.
<hr>

=== Publishing attribution on a separate web page ===
As stated above, recommended attribution depends on the medium you're working with. For media such as offline materials, video, audio, and images, consider publishing a web page with attribution information. For example, on a webpage featuring your audio recording, provide a credit list of material you used that adheres to best practices above. Doing so allows not only your material, but the materials you attribute, to be found by search engines and other web discovery tools. If possible within the medium, make the Author, Source, and License links the user can follow.

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">'''Example:'''<br>This video features the song [http://ccmixter.org/media/files/victor/6374 "Desaprendere (Treatment)"] by [http://fourstones.net/ fourstones], available under a Creative Commons [http://creativecommons.org/licenses/by-nc/2.5/ Attribution-Noncommercial 2.5 license].</div>

<hr>

==Attributing public domain materials==
Although attribution is not a legal obligation under [https://creativecommons.org/share-your-work/public-domain/cc0/ CC0 dedication]’s or [https://creativecommons.org/share-your-work/public-domain/pdm/ CC Public Domain Mark]’s licensing terms, we recommend that you consider providing attribution to the source for public domain materials when it is reasonable to do so. Attribution of public domain works not only encourages institutions to digitize and share more public domain materials in their physical collections, but also empowers users to easily locate the original source.

The following public domain image is digitized and hosted by the Rijksmuseum (the national museum of the Netherlands). The Rijksmuseum has applied a CC0 dedication to the image.

:[[File:Attributing_the_milkmaid.png|300px]]

You may provide credit in the following format:

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">“[http://hdl.handle.net/10934/RM0001.COLLECT.6417 The Milkmaid]” by Vermeer. The Rijksmuseum collection. The image is dedicated to the public domain under [https://creativecommons.org/share-your-work/public-domain/cc0/ CC0]. </div>

In most cases, people credit the source regardless of the work’s copyright status. Especially in an academic setting, providing source information about other people’s works has long been considered crucial to academic integrity. Copyright cannot be the only checkbox when deciding whether a source will be attributed.

== Common pitfalls ==

Below are some practices that you may wish to avoid. These practices are not always contrary to the Creative Commons licensing terms, but they often make it more challenging for users to find the original source and/or author.

'''Attribute in alt text'''
:Alt text is intended to provide accessible information about visual materials for users with cognitive disabilities or visual impairment. Using this field for licensing information makes browsing difficult for those users.

'''Attribute in metadata fields only'''
:While it is great to include attribution in metadata fields (such as EXIF for images), in most cases this is not the only place to include attribution information. This is because many users are likely not aware of, and will never see, attribution information included in metadata.

'''Credit authors by names other than the ones they have selected'''
:Many people believe that attribution must be given to the real name of the author of a work, but this is not the case — always give attribution to the name the author has specified, even if it is a pseudonym. If the author does not give a name or explicitly requests to be anonymous, you must give the other attribution information (i.e., “T” and “SL” from “TASL”) without crediting the author.

'''Credit a site (or Creative Commons itself!) instead of the author'''
:Unless an author specifically requests users to only credit a site, crediting the site where you have found the material cannot substitute crediting the author. An author may have uploaded material to a site under a CC license, but in most cases, the copyright is still held by the author, and it is the copyright holder who needs to be credited. For example, many photos sourced from Wikimedia Commons are attributed to Wikimedia when they must be attributed to the authors.

== Other guides to attribution ==

* [http://creativecommons.org.au/materials/attribution.pdf Attributing Creative Commons Material] (pdf) - Creative Commons Australia's publication is full of examples with colorful imagery.
* [http://www.newmediarights.org/guide/how_to/creative_commons/best_practices_creative_commons_attributions How to attribute works you reuse under a Creative Commons license] by New Media Rights provides real world examples by different media type

[[Category:Marking]]
[[Category:Licensing]]
[[Category:Community]]
[[Category:Media]]
[[Category:HOWTO]]
[[Category:Guide]]
{{Best Practice}}

Recommended practices for attribution

2022-12-07T20:28:32Z

CCID-yuanxiaoxu: /* Publishing a web page for attribution */

You can use CC-licensed materials as long as you follow the license conditions. One condition of all CC licenses is attribution: crediting the author and noting the source and the license. Generally speaking, attribution must reasonably include all relevant information supplied by the licensor. Because each use case is different, you can decide what form of attribution is most suitable for your specific situation. The following examples are intended to illustrate what typical prudent practices look like. We expect community norms and expectations to evolve with time, and will adapt this guide accordingly.
In addition to attribution, there are also [https://wiki.creativecommons.org/wiki/Considerations_for_licensors_and_licensees#Considerations_for_licensees|other things to consider as a licensor or a licensee]. If you are a licensor and would like to learn how to license your own material, take a look at [https://wiki.creativecommons.org/wiki/Marking_your_work_with_a_CC_license our guide on how to mark your work with a CC license].

==Basic components of attribution==

[[File:19th_century_tassel_from_Smithsonian.jpeg|290px|left]]

Whenever you are reusing CC licensed works, we recommend that the attribution include the '''T'''itle, '''A'''uthor, '''S'''ource, and '''L'''icense. This is true whether you’re sharing the work as-is or if you have made an adaptation. To remember these attribution elements, it’s helpful to think of the acronym: '''TASL'''.

Let’s now go through '''TASL''' — we will explain each element in more detail:

'''Title''': What is the name of the work?

:If a title was provided for the work, include it as a part of the attribution. Sometimes a title is not provided; in that case, there’s no need to mention the title.

:The inclusion of title is a requirement of all CC licenses version 3.0 or earlier, and it is optional for the 4.0 suites. See [https://wiki.creativecommons.org/wiki/Recommended_practices_for_attribution#License_details License details].

'''Author''': Who allows you to use the work?

:We often use “author” as a shorthand when we are, legally speaking, referring to the “licensor” (a.k.a., the “copyright holder” or “rightsholder”). This is because, in most CC-licensed works, the licensor is the same person or entity as the author. When an author is licensing their work under a CC license, and has made their name available, include the author’s name as a component in your attribution. Sometimes, the licensor may want you to give credit to some other entity, like a company or institution, or the licensor may want to be credited by a pseudonym instead of their real name. In rare cases, the licensor may not want to be attributed at all. In all of these cases, do what the licensor requests.

:Sometimes, the author will also provide a copyright notice, which consists of the copyright symbol, year of publication, and the name of the author/licensor. Include the copyright notice as a part of your attribution if such information is provided.

'''Source''': Where can people find the work?

:Please make it possible for future users to find the source of the material by including a URL or hyperlink where the work resides. This often is where you found the work. If you found it somewhere other than the original site, try to include information about the original site where the work was first shared publicly. It is also better to use the original URL instead of a shortened link, whether you are hyperlinking or printing out the entire URL.

'''License''': How can you use the work?

:You must specify which CC license was applied to the work you are reusing. Each of the six different CC licenses come with distinct requirements for re-use. We recommend that you name and provide a link to the license, e.g., [http://creativecommons.org/licenses/by/4.0 CC BY 4.0] (http://creativecommons.org/licenses/by/4.0) for a work licensed under CC BY 4.0.

:Consider also including the “disclaimer of warranties,” which clarifies that the author makes no representations or warranties about the non-infringement or absence of other defects concerning the CC-licensed work. In plain English, this means that the users will use the work at their own risk.

:To sum up, if the licensor has provided any information related to TASL, consider including them in your attribution. We also recommend providing links to the Title, Author, Source, and License, where possible, so future users can easily access the information they need on a work and the license terms.
<hr>
===Reasonable attribution===

The CC licenses ask you to be reasonable:

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 90%;">You may satisfy the attribution requirement in any reasonable manner based on the medium, means and context in which the Licensed Material is used. For example, it may be reasonable to satisfy some or all of the conditions by retaining a copyright notice, or by providing a URI or hyperlink associated with the Licensed Material, if the copyright notice or webpage includes some or all of the required information.</div>

There is no single best or correct way of attribution, as long as your attribution is reasonable and suited to the medium you're working with.
<hr>

===License details===

If you have any doubts or questions, you can read the complete attribution requirements which are spelled out in detail in the legal code of every CC license, eg. http://creativecommons.org/licenses/by/4.0/legalcode This [[License_Versions#Detailed_attribution_comparison_chart|chart compares the detailed requirements across all versions of CC licenses.]]

==Examples of attribution==

We will now look at some examples in different media.

===Attributing an image===

Here is a photo. Below, we will go over some good and bad examples of how people might attribute it.

[[File:8256206923_c77e85319e_n.jpg]]
<hr>

====This is a great attribution====
<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">
"[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Creative Commons 10th Birthday Celebration San Francisco]" by [http://www.flickr.com/photos/sixteenmilesofstring/ Timothy Vollmer] is licensed under [http://creativecommons.org/licenses/by/4.0/ CC BY 4.0]</div>

''Let’s go through TASL:''
:'''T'''itle? "Creative Commons 10th Birthday Celebration San Francisco"
:'''A'''uthor? "[http://www.flickr.com/photos/sixteenmilesofstring/ Timothy Vollmer]" - linked to his profile page
:'''S'''ource? "[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Creative Commons 10th Birthday Celebration San Francisco]" - linked to original Flickr page
:'''L'''icense? "[http://creativecommons.org/licenses/by/4.0/ CC BY 4.0]" - linked to license deed

Most importantly, this attribution reasonably includes all the relevant information provided by the author.
<hr>

====This is a pretty good attribution====

<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Photo] by Timothy Vollmer/ [http://creativecommons.org/licenses/by/2.0/ CC BY]</div>

''Let’s go through TASL:''
:'''T'''itle? Title is not noted but at least the source is linked.
:'''A'''uthor? "Timothy Vollmer"
:'''S'''ource? "[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Photo]" - linked to original Flickr page
:'''L'''icense? "[http://creativecommons.org/licenses/by/4.0/ CC BY]" - linked to license deed

As you see, a good attribution includes all the essential '''TASL''' elements, even though they may not mirror the format of credit the author has requested.
<hr>

==== This is an incorrect attribution====
<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">Photo: Creative Commons</div>

''Let’s go through TASL'':
:'''T'''itle? Title of the image is not noted
:'''A'''uthor? Author is not noted (It is a common mistake to attribute CC-licensed photos to CC, but Creative Commons is not the author!)
:'''S'''ource? No link to the original source
:'''L'''icense? There is no mention of a license nor a link to the license. "Creative Commons" is the name of an organization; it does not equate to any of the licenses maintained by the Creative Commons.
<hr>

====This is a great attribution for an image you modified slightly====
:[[File:Cropped_tvol_cupcake.png|300px]]

<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">"[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Creative Commons 10th Birthday Celebration San Francisco]" by [http://www.flickr.com/photos/sixteenmilesofstring/ Timothy Vollmer], used under [http://creativecommons.org/licenses/by/4.0/ CC BY 4.0] / Cropped from original</div>

Here, information on '''T'''itle, '''A'''uthor, '''S'''ource, and '''L'''icense are all included as requested by the author. The slight modification is also noted and briefly described.

Note if the modification changes the work’s meaning in a way that would be considered creative — that is, not a purely mechanical change or a simple crop/excerpt that keeps the original message undistorted, it would be considered creating a new adaptation of the original work. You cannot rely on a CC license that does not allow adaptation (e.g., CC BY-ND or CC BY-NC-ND) when making such modifications.

<hr>

====This is a great attribution for when you have created an adaptation====

:[[File:8256206923_c77e85319e_n_90fied.jpg|300px]]

<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">This work, "90fied", is adapted from "[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Creative Commons 10th Birthday Celebration San Francisco]" by [http://www.flickr.com/photos/sixteenmilesofstring/ Timothy Vollmer], used under [http://creativecommons.org/licenses/by/4.0/ CC BY 4.0]. "90fied" is licensed under [http://creativecommons.org/licenses/by/4.0/ CC BY 4.0] by [Your name here].</div>

''Let’s go through TASL:''

Original '''T'''itle, '''A'''uthor, '''S'''ource, and '''L'''icense are all noted.

The original work is referenced and the fact that it is an adaptation is also noted, so viewers can see what has changed.

The author and other attribution information for the new adapted work is also noted.

Note: If you're at a point where you are licensing works that are adaptations, go to [[Marking your work with a CC license]].
<hr>

===Attributing music===

====When you incorporate music in an audio or video recording====
Music (both the underlying composition and the sound recordings) — such as a song, or a recording of natural sounds — can be attributed within the audio/video, and in the description text of the audio/video. How to attribute a CC licensed music in an audio or video recording will largely depend on what is reasonable for a chosen medium and platform.

Caution: Licenses with “ND” do not allow for adaptations. Your use of CC-licensed music is often an adaptation!

It is considered adaptation if you incorporate CC-licensed music into your work in a way that the CC-licensed music can no longer be seen as a stand-alone piece. For example, if you are using a song as background music in a podcast or in a video, it is considered an adaptation of the song.

Keep in mind that CC BY-ND and CC BY-NC-ND do not allow adaptations (although you may be authorized by law to do so, such as under a users’ right like fair use, or you may ask for the author’s permission independent of the CC license).
<hr>

[[File:Smithsonian_music_stand.jpeg|left|250px]]

=====This is a great attribution of background music in a podcast or a video=====
When reasonable to do so, we recommend that you include attribution both in the description box and in the podcast recording or the video recording itself.

If you are using the following song in a podcast: ‘Day Bird’ by Broke for Free ([https://brokeforfree.com brokeforfree.com]), this would be a great way to provide attribution (which you can see in [https://soundcloud.com/wearecc/open-minds-podcast-catherine-stihler-ceo-of-creative-commons the Creative Commons podcast]) —

:At the end of the podcast audio recording, the host says:
:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 90%;">Special thanks to the musician Broke for Free, whose track “Day Bird” you heard at the beginning of this episode and you are listening to right now. It's under the Creative Commons Attribution License, meaning it's free for anyone to use. You can find it at the Free Music Archive—freemusicarchive.org</div>

:In the description box, the information text reads:
:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 90%;">Theme music: “Day Bird” by Broke for Free ([https://brokeforfree.com brokeforfree.com]). Available for use under the CC BY 3.0 license ([https://creativecommons.org/licenses/by/3.0/ creativecommons.org/licenses/by/3.0/]), at [https://freemusicarchive.org/music/Broke_For_Free/Directionless_EP/Broke_For_Free_-_Directionless_EP_-_03_Day_Bird|the Free Music Archive].</div>

''Let’s go through TASL:''

:'''T'''itle? Both the recording and the description box include the title of the work, “Day Bird”

:'''A'''uthor? "Broke for Free," again, noted both in the recording and in the description box

:'''S'''ource? Both the author’s page and the archive’s page are included with links

:'''L'''icense? "CC BY 3.0" — linked to license deed

You cannot talk over, or remix, music licensed under CC BY-ND or CC BY-NC-ND.

<hr>

=====This is a bad attribution of background music in a podcast or a video=====

A bad attribution is one where you do not provide enough information for a user to find the music you are using. The following is a bad attribution for the same song:

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">No attribution is included in the podcast recording or the video itself.

In the description box, it says: “ Creative Commons music.”</div>

''Let’s go through TASL:''

:'''T'''itle? Title is not noted

:'''A'''uthor? Author is not noted

:'''S'''ource? Source is not noted; users cannot find the specific song used in the podcast

:'''L'''icense? No information on the CC license

The attribution information is not sufficient for people to find the song you have re-used.
<hr>

====When you are not adding new elements to the music====
When you re-use music without adding new elements to it, you are not making an adaptation. In that case, you can rely on any of the CC licenses, including CC BY-ND and CC BY-NC-ND. We recommend providing attribution information in writing.

[[File:Wiki_page_attributing_night_owl.png|400px]]

On [https://commons.wikimedia.org/wiki/File:Broke_For_Free_-_01_-_Night_Owl.ogg this Wikipedia page], you can see an example of great attribution for the sharing another soundtrack, “Night Owl” by Broke for Free, when it’s without adaptation.

''Let’s go through TASL:''

'''T'''itle? Title of the work, “Night Owl,” is noted

'''A'''uthor? "Broke for Free," noted and linked to the author’s webpage

'''S'''ource? A link is provided for the source

'''L'''icense? "CC BY 3.0" — linked to license deed
<hr>

===Attributing text===
Let’s take [https://github.com/getify/You-Dont-Know-JS ''You Don't Know JS Yet'' (2nd Edition)] as an example, and go over what your attribution may look like if you reuse the book series. The information under the “License & Copyright” section looks like this on the webpage where the book series was originally shared:
:[[File:attributing_You_Don't_Know_JS_Yet_(2nd_Edition).png|200px]]

We recommend that you retain all the information provided by the author of the book series when it is reasonable for you to do so. For example, if you are distributing digital copies or excerpts of the book series in a free seminar, or using parts of the book in a free online course or presentation, the attribution will likely look something like this:

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">This chapter is from “[https://github.com/getify/You-Dont-Know-JS You Don't Know JS Yet (2nd Edition)]” by [https://github.com/getify Kyle Simpson]. The book is licensed under the [https://creativecommons.org/licenses/by-nc-nd/4.0/ CC BY-NC-ND 4.0 license]. © 2019-2022 Kyle Simpson.</div>

On the other hand, if you are distributing hard copies of the book series or excerpts from the book series, instead of using hyperlinks, you may wish to include the links so it’s easier for users to locate the original source of the book, the author, and the CC license:

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">This chapter is from “You Don't Know JS Yet (2nd Edition)” (https://github.com/getify/You-Dont-Know-JS) by Kyle Simpson (https://github.com/getify). The book is licensed under the CC BY-NC-ND 4.0 license (https://creativecommons.org/licenses/by-nc-nd/4.0/). © 2019-2022 Kyle Simpson.</div>

Note that the CC BY-NC-ND license includes the NoDerivatives requirement, which indicates that no adaptations are allowed. You cannot make any adaptations relying on the CC BY-NC-CD license the author chose for the book. If you would like to make a translation of the book, for example, you will need to ask the author for permission first.

The CC BY-NC-ND license also includes the NonCommercial requirement. To learn more, take a look at [https://en.wikipedia.org/wiki/Creative_Commons_NonCommercial_license our guide about the NonCommercial licenses].
<hr>

=== Attributing materials from multiple sources ===

:[[File:Saylor_marking_example.jpg]]

''Let’s go through TASL:''

:'''T'''itle? Specific works are named, e.g., "Box-and-whisker Plots"

:'''A'''uthor? Different authors noted for the different works

:'''S'''ource? Original materials are linked for each work

:'''L'''icense? The different licenses (Creative Commons Attribution for Collaborative Statistics and Creative Commons Attribution-Noncommercial-ShareAlike for the Khan Academy video) are spelled out and linked for each work

:Lastly, it is clear which attribution belongs to which work.

You can visit the [http://www.saylor.org/courses/ma121/ Saylor.org Introduction to Statistics course page] to see how they marked it up directly.
<hr>

=== Publishing attribution on a separate web page ===
As stated above, recommended attribution depends on the medium you're working with. For media such as offline materials, video, audio, and images, consider publishing a web page with attribution information. For example, on a webpage featuring your audio recording, provide a credit list of material you used that adheres to best practices above. Doing so allows not only your material, but the materials you attribute, to be found by search engines and other web discovery tools. If possible within the medium, make the Author, Source, and License links the user can follow.

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">'''Example:'''<br>This video features the song [http://ccmixter.org/media/files/victor/6374 "Desaprendere (Treatment)"] by [http://fourstones.net/ fourstones], available under a Creative Commons [http://creativecommons.org/licenses/by-nc/2.5/ Attribution-Noncommercial] license.</div>

<hr>

==Attributing public domain materials==
Although attribution is not a legal obligation under [https://creativecommons.org/share-your-work/public-domain/cc0/ CC0 dedication]’s or [https://creativecommons.org/share-your-work/public-domain/pdm/ CC Public Domain Mark]’s licensing terms, we recommend that you consider providing attribution to the source for public domain materials when it is reasonable to do so. Attribution of public domain works not only encourages institutions to digitize and share more public domain materials in their physical collections, but also empowers users to easily locate the original source.

The following public domain image is digitized and hosted by the Rijksmuseum (the national museum of the Netherlands). The Rijksmuseum has applied a CC0 dedication to the image.

:[[File:Attributing_the_milkmaid.png|300px]]

You may provide credit in the following format:

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">“[http://hdl.handle.net/10934/RM0001.COLLECT.6417 The Milkmaid]” by Vermeer. The Rijksmuseum collection. The image is dedicated to the public domain under [https://creativecommons.org/share-your-work/public-domain/cc0/ CC0]. </div>

In most cases, people credit the source regardless of the work’s copyright status. Especially in an academic setting, providing source information about other people’s works has long been considered crucial to academic integrity. Copyright cannot be the only checkbox when deciding whether a source will be attributed.

== Common pitfalls ==

Below are some practices that you may wish to avoid. These practices are not always contrary to the Creative Commons licensing terms, but they often make it more challenging for users to find the original source and/or author.

'''Attribute in alt text'''
:Alt text is intended to provide accessible information about visual materials for users with cognitive disabilities or visual impairment. Using this field for licensing information makes browsing difficult for those users.

'''Attribute in metadata fields only'''
:While it is great to include attribution in metadata fields (such as EXIF for images), in most cases this is not the only place to include attribution information. This is because many users are likely not aware of, and will never see, attribution information included in metadata.

'''Credit authors by names other than the ones they have selected'''
:Many people believe that attribution must be given to the real name of the author of a work, but this is not the case — always give attribution to the name the author has specified, even if it is a pseudonym. If the author does not give a name or explicitly requests to be anonymous, you must give the other attribution information (i.e., “T” and “SL” from “TASL”) without crediting the author.

'''Credit a site (or Creative Commons itself!) instead of the author'''
:Unless an author specifically requests users to only credit a site, crediting the site where you have found the material cannot substitute crediting the author. An author may have uploaded material to a site under a CC license, but in most cases, the copyright is still held by the author, and it is the copyright holder who needs to be credited. For example, many photos sourced from Wikimedia Commons are attributed to Wikimedia when they must be attributed to the authors.

== Other guides to attribution ==

* [http://creativecommons.org.au/materials/attribution.pdf Attributing Creative Commons Material] (pdf) - Creative Commons Australia's publication is full of examples with colorful imagery.
* [http://www.newmediarights.org/guide/how_to/creative_commons/best_practices_creative_commons_attributions How to attribute works you reuse under a Creative Commons license] by New Media Rights provides real world examples by different media type

[[Category:Marking]]
[[Category:Licensing]]
[[Category:Community]]
[[Category:Media]]
[[Category:HOWTO]]
[[Category:Guide]]
{{Best Practice}}

Recommended practices for attribution

2022-12-07T20:27:45Z

CCID-yuanxiaoxu: /* Reasonable attribution */

You can use CC-licensed materials as long as you follow the license conditions. One condition of all CC licenses is attribution: crediting the author and noting the source and the license. Generally speaking, attribution must reasonably include all relevant information supplied by the licensor. Because each use case is different, you can decide what form of attribution is most suitable for your specific situation. The following examples are intended to illustrate what typical prudent practices look like. We expect community norms and expectations to evolve with time, and will adapt this guide accordingly.
In addition to attribution, there are also [https://wiki.creativecommons.org/wiki/Considerations_for_licensors_and_licensees#Considerations_for_licensees|other things to consider as a licensor or a licensee]. If you are a licensor and would like to learn how to license your own material, take a look at [https://wiki.creativecommons.org/wiki/Marking_your_work_with_a_CC_license our guide on how to mark your work with a CC license].

==Basic components of attribution==

[[File:19th_century_tassel_from_Smithsonian.jpeg|290px|left]]

Whenever you are reusing CC licensed works, we recommend that the attribution include the '''T'''itle, '''A'''uthor, '''S'''ource, and '''L'''icense. This is true whether you’re sharing the work as-is or if you have made an adaptation. To remember these attribution elements, it’s helpful to think of the acronym: '''TASL'''.

Let’s now go through '''TASL''' — we will explain each element in more detail:

'''Title''': What is the name of the work?

:If a title was provided for the work, include it as a part of the attribution. Sometimes a title is not provided; in that case, there’s no need to mention the title.

:The inclusion of title is a requirement of all CC licenses version 3.0 or earlier, and it is optional for the 4.0 suites. See [https://wiki.creativecommons.org/wiki/Recommended_practices_for_attribution#License_details License details].

'''Author''': Who allows you to use the work?

:We often use “author” as a shorthand when we are, legally speaking, referring to the “licensor” (a.k.a., the “copyright holder” or “rightsholder”). This is because, in most CC-licensed works, the licensor is the same person or entity as the author. When an author is licensing their work under a CC license, and has made their name available, include the author’s name as a component in your attribution. Sometimes, the licensor may want you to give credit to some other entity, like a company or institution, or the licensor may want to be credited by a pseudonym instead of their real name. In rare cases, the licensor may not want to be attributed at all. In all of these cases, do what the licensor requests.

:Sometimes, the author will also provide a copyright notice, which consists of the copyright symbol, year of publication, and the name of the author/licensor. Include the copyright notice as a part of your attribution if such information is provided.

'''Source''': Where can people find the work?

:Please make it possible for future users to find the source of the material by including a URL or hyperlink where the work resides. This often is where you found the work. If you found it somewhere other than the original site, try to include information about the original site where the work was first shared publicly. It is also better to use the original URL instead of a shortened link, whether you are hyperlinking or printing out the entire URL.

'''License''': How can you use the work?

:You must specify which CC license was applied to the work you are reusing. Each of the six different CC licenses come with distinct requirements for re-use. We recommend that you name and provide a link to the license, e.g., [http://creativecommons.org/licenses/by/4.0 CC BY 4.0] (http://creativecommons.org/licenses/by/4.0) for a work licensed under CC BY 4.0.

:Consider also including the “disclaimer of warranties,” which clarifies that the author makes no representations or warranties about the non-infringement or absence of other defects concerning the CC-licensed work. In plain English, this means that the users will use the work at their own risk.

:To sum up, if the licensor has provided any information related to TASL, consider including them in your attribution. We also recommend providing links to the Title, Author, Source, and License, where possible, so future users can easily access the information they need on a work and the license terms.
<hr>
===Reasonable attribution===

The CC licenses ask you to be reasonable:

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 90%;">You may satisfy the attribution requirement in any reasonable manner based on the medium, means and context in which the Licensed Material is used. For example, it may be reasonable to satisfy some or all of the conditions by retaining a copyright notice, or by providing a URI or hyperlink associated with the Licensed Material, if the copyright notice or webpage includes some or all of the required information.</div>

There is no single best or correct way of attribution, as long as your attribution is reasonable and suited to the medium you're working with.
<hr>

===License details===

If you have any doubts or questions, you can read the complete attribution requirements which are spelled out in detail in the legal code of every CC license, eg. http://creativecommons.org/licenses/by/4.0/legalcode This [[License_Versions#Detailed_attribution_comparison_chart|chart compares the detailed requirements across all versions of CC licenses.]]

==Examples of attribution==

We will now look at some examples in different media.

===Attributing an image===

Here is a photo. Below, we will go over some good and bad examples of how people might attribute it.

[[File:8256206923_c77e85319e_n.jpg]]
<hr>

====This is a great attribution====
<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">
"[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Creative Commons 10th Birthday Celebration San Francisco]" by [http://www.flickr.com/photos/sixteenmilesofstring/ Timothy Vollmer] is licensed under [http://creativecommons.org/licenses/by/4.0/ CC BY 4.0]</div>

''Let’s go through TASL:''
:'''T'''itle? "Creative Commons 10th Birthday Celebration San Francisco"
:'''A'''uthor? "[http://www.flickr.com/photos/sixteenmilesofstring/ Timothy Vollmer]" - linked to his profile page
:'''S'''ource? "[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Creative Commons 10th Birthday Celebration San Francisco]" - linked to original Flickr page
:'''L'''icense? "[http://creativecommons.org/licenses/by/4.0/ CC BY 4.0]" - linked to license deed

Most importantly, this attribution reasonably includes all the relevant information provided by the author.
<hr>

====This is a pretty good attribution====

<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Photo] by Timothy Vollmer/ [http://creativecommons.org/licenses/by/2.0/ CC BY]</div>

''Let’s go through TASL:''
:'''T'''itle? Title is not noted but at least the source is linked.
:'''A'''uthor? "Timothy Vollmer"
:'''S'''ource? "[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Photo]" - linked to original Flickr page
:'''L'''icense? "[http://creativecommons.org/licenses/by/4.0/ CC BY]" - linked to license deed

As you see, a good attribution includes all the essential '''TASL''' elements, even though they may not mirror the format of credit the author has requested.
<hr>

==== This is an incorrect attribution====
<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">Photo: Creative Commons</div>

''Let’s go through TASL'':
:'''T'''itle? Title of the image is not noted
:'''A'''uthor? Author is not noted (It is a common mistake to attribute CC-licensed photos to CC, but Creative Commons is not the author!)
:'''S'''ource? No link to the original source
:'''L'''icense? There is no mention of a license nor a link to the license. "Creative Commons" is the name of an organization; it does not equate to any of the licenses maintained by the Creative Commons.
<hr>

====This is a great attribution for an image you modified slightly====
:[[File:Cropped_tvol_cupcake.png|300px]]

<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">"[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Creative Commons 10th Birthday Celebration San Francisco]" by [http://www.flickr.com/photos/sixteenmilesofstring/ Timothy Vollmer], used under [http://creativecommons.org/licenses/by/4.0/ CC BY 4.0] / Cropped from original</div>

Here, information on '''T'''itle, '''A'''uthor, '''S'''ource, and '''L'''icense are all included as requested by the author. The slight modification is also noted and briefly described.

Note if the modification changes the work’s meaning in a way that would be considered creative — that is, not a purely mechanical change or a simple crop/excerpt that keeps the original message undistorted, it would be considered creating a new adaptation of the original work. You cannot rely on a CC license that does not allow adaptation (e.g., CC BY-ND or CC BY-NC-ND) when making such modifications.

<hr>

====This is a great attribution for when you have created an adaptation====

:[[File:8256206923_c77e85319e_n_90fied.jpg|300px]]

<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">This work, "90fied", is adapted from "[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Creative Commons 10th Birthday Celebration San Francisco]" by [http://www.flickr.com/photos/sixteenmilesofstring/ Timothy Vollmer], used under [http://creativecommons.org/licenses/by/4.0/ CC BY 4.0]. "90fied" is licensed under [http://creativecommons.org/licenses/by/4.0/ CC BY 4.0] by [Your name here].</div>

''Let’s go through TASL:''

Original '''T'''itle, '''A'''uthor, '''S'''ource, and '''L'''icense are all noted.

The original work is referenced and the fact that it is an adaptation is also noted, so viewers can see what has changed.

The author and other attribution information for the new adapted work is also noted.

Note: If you're at a point where you are licensing works that are adaptations, go to [[Marking your work with a CC license]].
<hr>

===Attributing music===

====When you incorporate music in an audio or video recording====
Music (both the underlying composition and the sound recordings) — such as a song, or a recording of natural sounds — can be attributed within the audio/video, and in the description text of the audio/video. How to attribute a CC licensed music in an audio or video recording will largely depend on what is reasonable for a chosen medium and platform.

Caution: Licenses with “ND” do not allow for adaptations. Your use of CC-licensed music is often an adaptation!

It is considered adaptation if you incorporate CC-licensed music into your work in a way that the CC-licensed music can no longer be seen as a stand-alone piece. For example, if you are using a song as background music in a podcast or in a video, it is considered an adaptation of the song.

Keep in mind that CC BY-ND and CC BY-NC-ND do not allow adaptations (although you may be authorized by law to do so, such as under a users’ right like fair use, or you may ask for the author’s permission independent of the CC license).
<hr>

[[File:Smithsonian_music_stand.jpeg|left|250px]]

=====This is a great attribution of background music in a podcast or a video=====
When reasonable to do so, we recommend that you include attribution both in the description box and in the podcast recording or the video recording itself.

If you are using the following song in a podcast: ‘Day Bird’ by Broke for Free ([https://brokeforfree.com brokeforfree.com]), this would be a great way to provide attribution (which you can see in [https://soundcloud.com/wearecc/open-minds-podcast-catherine-stihler-ceo-of-creative-commons the Creative Commons podcast]) —

:At the end of the podcast audio recording, the host says:
:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 90%;">Special thanks to the musician Broke for Free, whose track “Day Bird” you heard at the beginning of this episode and you are listening to right now. It's under the Creative Commons Attribution License, meaning it's free for anyone to use. You can find it at the Free Music Archive—freemusicarchive.org</div>

:In the description box, the information text reads:
:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 90%;">Theme music: “Day Bird” by Broke for Free ([https://brokeforfree.com brokeforfree.com]). Available for use under the CC BY 3.0 license ([https://creativecommons.org/licenses/by/3.0/ creativecommons.org/licenses/by/3.0/]), at [https://freemusicarchive.org/music/Broke_For_Free/Directionless_EP/Broke_For_Free_-_Directionless_EP_-_03_Day_Bird|the Free Music Archive].</div>

''Let’s go through TASL:''

:'''T'''itle? Both the recording and the description box include the title of the work, “Day Bird”

:'''A'''uthor? "Broke for Free," again, noted both in the recording and in the description box

:'''S'''ource? Both the author’s page and the archive’s page are included with links

:'''L'''icense? "CC BY 3.0" — linked to license deed

You cannot talk over, or remix, music licensed under CC BY-ND or CC BY-NC-ND.

<hr>

=====This is a bad attribution of background music in a podcast or a video=====

A bad attribution is one where you do not provide enough information for a user to find the music you are using. The following is a bad attribution for the same song:

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">No attribution is included in the podcast recording or the video itself.

In the description box, it says: “ Creative Commons music.”</div>

''Let’s go through TASL:''

:'''T'''itle? Title is not noted

:'''A'''uthor? Author is not noted

:'''S'''ource? Source is not noted; users cannot find the specific song used in the podcast

:'''L'''icense? No information on the CC license

The attribution information is not sufficient for people to find the song you have re-used.
<hr>

====When you are not adding new elements to the music====
When you re-use music without adding new elements to it, you are not making an adaptation. In that case, you can rely on any of the CC licenses, including CC BY-ND and CC BY-NC-ND. We recommend providing attribution information in writing.

[[File:Wiki_page_attributing_night_owl.png|400px]]

On [https://commons.wikimedia.org/wiki/File:Broke_For_Free_-_01_-_Night_Owl.ogg this Wikipedia page], you can see an example of great attribution for the sharing another soundtrack, “Night Owl” by Broke for Free, when it’s without adaptation.

''Let’s go through TASL:''

'''T'''itle? Title of the work, “Night Owl,” is noted

'''A'''uthor? "Broke for Free," noted and linked to the author’s webpage

'''S'''ource? A link is provided for the source

'''L'''icense? "CC BY 3.0" — linked to license deed
<hr>

===Attributing text===
Let’s take [https://github.com/getify/You-Dont-Know-JS ''You Don't Know JS Yet'' (2nd Edition)] as an example, and go over what your attribution may look like if you reuse the book series. The information under the “License & Copyright” section looks like this on the webpage where the book series was originally shared:
:[[File:attributing_You_Don't_Know_JS_Yet_(2nd_Edition).png|200px]]

We recommend that you retain all the information provided by the author of the book series when it is reasonable for you to do so. For example, if you are distributing digital copies or excerpts of the book series in a free seminar, or using parts of the book in a free online course or presentation, the attribution will likely look something like this:

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">This chapter is from “[https://github.com/getify/You-Dont-Know-JS You Don't Know JS Yet (2nd Edition)]” by [https://github.com/getify Kyle Simpson]. The book is licensed under the [https://creativecommons.org/licenses/by-nc-nd/4.0/ CC BY-NC-ND 4.0 license]. © 2019-2022 Kyle Simpson.</div>

On the other hand, if you are distributing hard copies of the book series or excerpts from the book series, instead of using hyperlinks, you may wish to include the links so it’s easier for users to locate the original source of the book, the author, and the CC license:

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">This chapter is from “You Don't Know JS Yet (2nd Edition)” (https://github.com/getify/You-Dont-Know-JS) by Kyle Simpson (https://github.com/getify). The book is licensed under the CC BY-NC-ND 4.0 license (https://creativecommons.org/licenses/by-nc-nd/4.0/). © 2019-2022 Kyle Simpson.</div>

Note that the CC BY-NC-ND license includes the NoDerivatives requirement, which indicates that no adaptations are allowed. You cannot make any adaptations relying on the CC BY-NC-CD license the author chose for the book. If you would like to make a translation of the book, for example, you will need to ask the author for permission first.

The CC BY-NC-ND license also includes the NonCommercial requirement. To learn more, take a look at [https://en.wikipedia.org/wiki/Creative_Commons_NonCommercial_license our guide about the NonCommercial licenses].
<hr>

=== Attributing materials from multiple sources ===

:[[File:Saylor_marking_example.jpg]]

''Let’s go through TASL:''

:'''T'''itle? Specific works are named, e.g., "Box-and-whisker Plots"

:'''A'''uthor? Different authors noted for the different works

:'''S'''ource? Original materials are linked for each work

:'''L'''icense? The different licenses (Creative Commons Attribution for Collaborative Statistics and Creative Commons Attribution-Noncommercial-ShareAlike for the Khan Academy video) are spelled out and linked for each work

:Lastly, it is clear which attribution belongs to which work.

You can visit the [http://www.saylor.org/courses/ma121/ Saylor.org Introduction to Statistics course page] to see how they marked it up directly.
<hr>

=== Publishing a web page for attribution ===
As stated above, recommended attribution depends on the medium you're working with. For media such as offline materials, video, audio, and images, consider publishing a web page with attribution information. For example, on a webpage featuring your audio recording, provide a credit list of material you used that adheres to best practices above. Doing so allows not only your material, but the materials you attribute, to be found by search engines and other web discovery tools. If possible within the medium, make the Author, Source, and License links the user can follow.

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">'''Example:'''<br>This video features the song [http://ccmixter.org/media/files/victor/6374 "Desaprendere (Treatment)"] by [http://fourstones.net/ fourstones], available under a Creative Commons [http://creativecommons.org/licenses/by-nc/2.5/ Attribution-Noncommercial] license.</div>

<hr>

==Attributing public domain materials==
Although attribution is not a legal obligation under [https://creativecommons.org/share-your-work/public-domain/cc0/ CC0 dedication]’s or [https://creativecommons.org/share-your-work/public-domain/pdm/ CC Public Domain Mark]’s licensing terms, we recommend that you consider providing attribution to the source for public domain materials when it is reasonable to do so. Attribution of public domain works not only encourages institutions to digitize and share more public domain materials in their physical collections, but also empowers users to easily locate the original source.

The following public domain image is digitized and hosted by the Rijksmuseum (the national museum of the Netherlands). The Rijksmuseum has applied a CC0 dedication to the image.

:[[File:Attributing_the_milkmaid.png|300px]]

You may provide credit in the following format:

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">“[http://hdl.handle.net/10934/RM0001.COLLECT.6417 The Milkmaid]” by Vermeer. The Rijksmuseum collection. The image is dedicated to the public domain under [https://creativecommons.org/share-your-work/public-domain/cc0/ CC0]. </div>

In most cases, people credit the source regardless of the work’s copyright status. Especially in an academic setting, providing source information about other people’s works has long been considered crucial to academic integrity. Copyright cannot be the only checkbox when deciding whether a source will be attributed.

== Common pitfalls ==

Below are some practices that you may wish to avoid. These practices are not always contrary to the Creative Commons licensing terms, but they often make it more challenging for users to find the original source and/or author.

'''Attribute in alt text'''
:Alt text is intended to provide accessible information about visual materials for users with cognitive disabilities or visual impairment. Using this field for licensing information makes browsing difficult for those users.

'''Attribute in metadata fields only'''
:While it is great to include attribution in metadata fields (such as EXIF for images), in most cases this is not the only place to include attribution information. This is because many users are likely not aware of, and will never see, attribution information included in metadata.

'''Credit authors by names other than the ones they have selected'''
:Many people believe that attribution must be given to the real name of the author of a work, but this is not the case — always give attribution to the name the author has specified, even if it is a pseudonym. If the author does not give a name or explicitly requests to be anonymous, you must give the other attribution information (i.e., “T” and “SL” from “TASL”) without crediting the author.

'''Credit a site (or Creative Commons itself!) instead of the author'''
:Unless an author specifically requests users to only credit a site, crediting the site where you have found the material cannot substitute crediting the author. An author may have uploaded material to a site under a CC license, but in most cases, the copyright is still held by the author, and it is the copyright holder who needs to be credited. For example, many photos sourced from Wikimedia Commons are attributed to Wikimedia when they must be attributed to the authors.

== Other guides to attribution ==

* [http://creativecommons.org.au/materials/attribution.pdf Attributing Creative Commons Material] (pdf) - Creative Commons Australia's publication is full of examples with colorful imagery.
* [http://www.newmediarights.org/guide/how_to/creative_commons/best_practices_creative_commons_attributions How to attribute works you reuse under a Creative Commons license] by New Media Rights provides real world examples by different media type

[[Category:Marking]]
[[Category:Licensing]]
[[Category:Community]]
[[Category:Media]]
[[Category:HOWTO]]
[[Category:Guide]]
{{Best Practice}}

Recommended practices for attribution

2022-12-07T20:23:43Z

CCID-yuanxiaoxu: /* Basic components of attribution */

You can use CC-licensed materials as long as you follow the license conditions. One condition of all CC licenses is attribution: crediting the author and noting the source and the license. Generally speaking, attribution must reasonably include all relevant information supplied by the licensor. Because each use case is different, you can decide what form of attribution is most suitable for your specific situation. The following examples are intended to illustrate what typical prudent practices look like. We expect community norms and expectations to evolve with time, and will adapt this guide accordingly.
In addition to attribution, there are also [https://wiki.creativecommons.org/wiki/Considerations_for_licensors_and_licensees#Considerations_for_licensees|other things to consider as a licensor or a licensee]. If you are a licensor and would like to learn how to license your own material, take a look at [https://wiki.creativecommons.org/wiki/Marking_your_work_with_a_CC_license our guide on how to mark your work with a CC license].

==Basic components of attribution==

[[File:19th_century_tassel_from_Smithsonian.jpeg|290px|left]]

Whenever you are reusing CC licensed works, we recommend that the attribution include the '''T'''itle, '''A'''uthor, '''S'''ource, and '''L'''icense. This is true whether you’re sharing the work as-is or if you have made an adaptation. To remember these attribution elements, it’s helpful to think of the acronym: '''TASL'''.

Let’s now go through '''TASL''' — we will explain each element in more detail:

'''Title''': What is the name of the work?

:If a title was provided for the work, include it as a part of the attribution. Sometimes a title is not provided; in that case, there’s no need to mention the title.

:The inclusion of title is a requirement of all CC licenses version 3.0 or earlier, and it is optional for the 4.0 suites. See [https://wiki.creativecommons.org/wiki/Recommended_practices_for_attribution#License_details License details].

'''Author''': Who allows you to use the work?

:We often use “author” as a shorthand when we are, legally speaking, referring to the “licensor” (a.k.a., the “copyright holder” or “rightsholder”). This is because, in most CC-licensed works, the licensor is the same person or entity as the author. When an author is licensing their work under a CC license, and has made their name available, include the author’s name as a component in your attribution. Sometimes, the licensor may want you to give credit to some other entity, like a company or institution, or the licensor may want to be credited by a pseudonym instead of their real name. In rare cases, the licensor may not want to be attributed at all. In all of these cases, do what the licensor requests.

:Sometimes, the author will also provide a copyright notice, which consists of the copyright symbol, year of publication, and the name of the author/licensor. Include the copyright notice as a part of your attribution if such information is provided.

'''Source''': Where can people find the work?

:Please make it possible for future users to find the source of the material by including a URL or hyperlink where the work resides. This often is where you found the work. If you found it somewhere other than the original site, try to include information about the original site where the work was first shared publicly. It is also better to use the original URL instead of a shortened link, whether you are hyperlinking or printing out the entire URL.

'''License''': How can you use the work?

:You must specify which CC license was applied to the work you are reusing. Each of the six different CC licenses come with distinct requirements for re-use. We recommend that you name and provide a link to the license, e.g., [http://creativecommons.org/licenses/by/4.0 CC BY 4.0] (http://creativecommons.org/licenses/by/4.0) for a work licensed under CC BY 4.0.

:Consider also including the “disclaimer of warranties,” which clarifies that the author makes no representations or warranties about the non-infringement or absence of other defects concerning the CC-licensed work. In plain English, this means that the users will use the work at their own risk.

:To sum up, if the licensor has provided any information related to TASL, consider including them in your attribution. We also recommend providing links to the Title, Author, Source, and License, where possible, so future users can easily access the information they need on a work and the license terms.
<hr>
===Reasonable attribution===

The CC licenses ask you to be reasonable:

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 90%;">You may satisfy the attribution requirement in any reasonable manner based on the medium, means and context in which the Licensed Material is used. For example, it may be reasonable to satisfy some or all of the conditions by retaining a copyright notice, or by providing a URI or hyperlink associated with the Licensed Material, if the copyright notice or webpage includes some or all of the required information.</div>

There is no single best or correct way of attribution, as long as your attribution is reasonable and suited to the medium you're working with. That being said, please include attribution somehow, even if it's a link to an About page that has the relevant info. (More on different media below.)
<hr>

===License details===

If you have any doubts or questions, you can read the complete attribution requirements which are spelled out in detail in the legal code of every CC license, eg. http://creativecommons.org/licenses/by/4.0/legalcode This [[License_Versions#Detailed_attribution_comparison_chart|chart compares the detailed requirements across all versions of CC licenses.]]

==Examples of attribution==

We will now look at some examples in different media.

===Attributing an image===

Here is a photo. Below, we will go over some good and bad examples of how people might attribute it.

[[File:8256206923_c77e85319e_n.jpg]]
<hr>

====This is a great attribution====
<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">
"[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Creative Commons 10th Birthday Celebration San Francisco]" by [http://www.flickr.com/photos/sixteenmilesofstring/ Timothy Vollmer] is licensed under [http://creativecommons.org/licenses/by/4.0/ CC BY 4.0]</div>

''Let’s go through TASL:''
:'''T'''itle? "Creative Commons 10th Birthday Celebration San Francisco"
:'''A'''uthor? "[http://www.flickr.com/photos/sixteenmilesofstring/ Timothy Vollmer]" - linked to his profile page
:'''S'''ource? "[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Creative Commons 10th Birthday Celebration San Francisco]" - linked to original Flickr page
:'''L'''icense? "[http://creativecommons.org/licenses/by/4.0/ CC BY 4.0]" - linked to license deed

Most importantly, this attribution reasonably includes all the relevant information provided by the author.
<hr>

====This is a pretty good attribution====

<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Photo] by Timothy Vollmer/ [http://creativecommons.org/licenses/by/2.0/ CC BY]</div>

''Let’s go through TASL:''
:'''T'''itle? Title is not noted but at least the source is linked.
:'''A'''uthor? "Timothy Vollmer"
:'''S'''ource? "[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Photo]" - linked to original Flickr page
:'''L'''icense? "[http://creativecommons.org/licenses/by/4.0/ CC BY]" - linked to license deed

As you see, a good attribution includes all the essential '''TASL''' elements, even though they may not mirror the format of credit the author has requested.
<hr>

==== This is an incorrect attribution====
<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">Photo: Creative Commons</div>

''Let’s go through TASL'':
:'''T'''itle? Title of the image is not noted
:'''A'''uthor? Author is not noted (It is a common mistake to attribute CC-licensed photos to CC, but Creative Commons is not the author!)
:'''S'''ource? No link to the original source
:'''L'''icense? There is no mention of a license nor a link to the license. "Creative Commons" is the name of an organization; it does not equate to any of the licenses maintained by the Creative Commons.
<hr>

====This is a great attribution for an image you modified slightly====
:[[File:Cropped_tvol_cupcake.png|300px]]

<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">"[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Creative Commons 10th Birthday Celebration San Francisco]" by [http://www.flickr.com/photos/sixteenmilesofstring/ Timothy Vollmer], used under [http://creativecommons.org/licenses/by/4.0/ CC BY 4.0] / Cropped from original</div>

Here, information on '''T'''itle, '''A'''uthor, '''S'''ource, and '''L'''icense are all included as requested by the author. The slight modification is also noted and briefly described.

Note if the modification changes the work’s meaning in a way that would be considered creative — that is, not a purely mechanical change or a simple crop/excerpt that keeps the original message undistorted, it would be considered creating a new adaptation of the original work. You cannot rely on a CC license that does not allow adaptation (e.g., CC BY-ND or CC BY-NC-ND) when making such modifications.

<hr>

====This is a great attribution for when you have created an adaptation====

:[[File:8256206923_c77e85319e_n_90fied.jpg|300px]]

<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">This work, "90fied", is adapted from "[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Creative Commons 10th Birthday Celebration San Francisco]" by [http://www.flickr.com/photos/sixteenmilesofstring/ Timothy Vollmer], used under [http://creativecommons.org/licenses/by/4.0/ CC BY 4.0]. "90fied" is licensed under [http://creativecommons.org/licenses/by/4.0/ CC BY 4.0] by [Your name here].</div>

''Let’s go through TASL:''

Original '''T'''itle, '''A'''uthor, '''S'''ource, and '''L'''icense are all noted.

The original work is referenced and the fact that it is an adaptation is also noted, so viewers can see what has changed.

The author and other attribution information for the new adapted work is also noted.

Note: If you're at a point where you are licensing works that are adaptations, go to [[Marking your work with a CC license]].
<hr>

===Attributing music===

====When you incorporate music in an audio or video recording====
Music (both the underlying composition and the sound recordings) — such as a song, or a recording of natural sounds — can be attributed within the audio/video, and in the description text of the audio/video. How to attribute a CC licensed music in an audio or video recording will largely depend on what is reasonable for a chosen medium and platform.

Caution: Licenses with “ND” do not allow for adaptations. Your use of CC-licensed music is often an adaptation!

It is considered adaptation if you incorporate CC-licensed music into your work in a way that the CC-licensed music can no longer be seen as a stand-alone piece. For example, if you are using a song as background music in a podcast or in a video, it is considered an adaptation of the song.

Keep in mind that CC BY-ND and CC BY-NC-ND do not allow adaptations (although you may be authorized by law to do so, such as under a users’ right like fair use, or you may ask for the author’s permission independent of the CC license).
<hr>

[[File:Smithsonian_music_stand.jpeg|left|250px]]

=====This is a great attribution of background music in a podcast or a video=====
When reasonable to do so, we recommend that you include attribution both in the description box and in the podcast recording or the video recording itself.

If you are using the following song in a podcast: ‘Day Bird’ by Broke for Free ([https://brokeforfree.com brokeforfree.com]), this would be a great way to provide attribution (which you can see in [https://soundcloud.com/wearecc/open-minds-podcast-catherine-stihler-ceo-of-creative-commons the Creative Commons podcast]) —

:At the end of the podcast audio recording, the host says:
:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 90%;">Special thanks to the musician Broke for Free, whose track “Day Bird” you heard at the beginning of this episode and you are listening to right now. It's under the Creative Commons Attribution License, meaning it's free for anyone to use. You can find it at the Free Music Archive—freemusicarchive.org</div>

:In the description box, the information text reads:
:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 90%;">Theme music: “Day Bird” by Broke for Free ([https://brokeforfree.com brokeforfree.com]). Available for use under the CC BY 3.0 license ([https://creativecommons.org/licenses/by/3.0/ creativecommons.org/licenses/by/3.0/]), at [https://freemusicarchive.org/music/Broke_For_Free/Directionless_EP/Broke_For_Free_-_Directionless_EP_-_03_Day_Bird|the Free Music Archive].</div>

''Let’s go through TASL:''

:'''T'''itle? Both the recording and the description box include the title of the work, “Day Bird”

:'''A'''uthor? "Broke for Free," again, noted both in the recording and in the description box

:'''S'''ource? Both the author’s page and the archive’s page are included with links

:'''L'''icense? "CC BY 3.0" — linked to license deed

You cannot talk over, or remix, music licensed under CC BY-ND or CC BY-NC-ND.

<hr>

=====This is a bad attribution of background music in a podcast or a video=====

A bad attribution is one where you do not provide enough information for a user to find the music you are using. The following is a bad attribution for the same song:

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">No attribution is included in the podcast recording or the video itself.

In the description box, it says: “ Creative Commons music.”</div>

''Let’s go through TASL:''

:'''T'''itle? Title is not noted

:'''A'''uthor? Author is not noted

:'''S'''ource? Source is not noted; users cannot find the specific song used in the podcast

:'''L'''icense? No information on the CC license

The attribution information is not sufficient for people to find the song you have re-used.
<hr>

====When you are not adding new elements to the music====
When you re-use music without adding new elements to it, you are not making an adaptation. In that case, you can rely on any of the CC licenses, including CC BY-ND and CC BY-NC-ND. We recommend providing attribution information in writing.

[[File:Wiki_page_attributing_night_owl.png|400px]]

On [https://commons.wikimedia.org/wiki/File:Broke_For_Free_-_01_-_Night_Owl.ogg this Wikipedia page], you can see an example of great attribution for the sharing another soundtrack, “Night Owl” by Broke for Free, when it’s without adaptation.

''Let’s go through TASL:''

'''T'''itle? Title of the work, “Night Owl,” is noted

'''A'''uthor? "Broke for Free," noted and linked to the author’s webpage

'''S'''ource? A link is provided for the source

'''L'''icense? "CC BY 3.0" — linked to license deed
<hr>

===Attributing text===
Let’s take [https://github.com/getify/You-Dont-Know-JS ''You Don't Know JS Yet'' (2nd Edition)] as an example, and go over what your attribution may look like if you reuse the book series. The information under the “License & Copyright” section looks like this on the webpage where the book series was originally shared:
:[[File:attributing_You_Don't_Know_JS_Yet_(2nd_Edition).png|200px]]

We recommend that you retain all the information provided by the author of the book series when it is reasonable for you to do so. For example, if you are distributing digital copies or excerpts of the book series in a free seminar, or using parts of the book in a free online course or presentation, the attribution will likely look something like this:

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">This chapter is from “[https://github.com/getify/You-Dont-Know-JS You Don't Know JS Yet (2nd Edition)]” by [https://github.com/getify Kyle Simpson]. The book is licensed under the [https://creativecommons.org/licenses/by-nc-nd/4.0/ CC BY-NC-ND 4.0 license]. © 2019-2022 Kyle Simpson.</div>

On the other hand, if you are distributing hard copies of the book series or excerpts from the book series, instead of using hyperlinks, you may wish to include the links so it’s easier for users to locate the original source of the book, the author, and the CC license:

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">This chapter is from “You Don't Know JS Yet (2nd Edition)” (https://github.com/getify/You-Dont-Know-JS) by Kyle Simpson (https://github.com/getify). The book is licensed under the CC BY-NC-ND 4.0 license (https://creativecommons.org/licenses/by-nc-nd/4.0/). © 2019-2022 Kyle Simpson.</div>

Note that the CC BY-NC-ND license includes the NoDerivatives requirement, which indicates that no adaptations are allowed. You cannot make any adaptations relying on the CC BY-NC-CD license the author chose for the book. If you would like to make a translation of the book, for example, you will need to ask the author for permission first.

The CC BY-NC-ND license also includes the NonCommercial requirement. To learn more, take a look at [https://en.wikipedia.org/wiki/Creative_Commons_NonCommercial_license our guide about the NonCommercial licenses].
<hr>

=== Attributing materials from multiple sources ===

:[[File:Saylor_marking_example.jpg]]

''Let’s go through TASL:''

:'''T'''itle? Specific works are named, e.g., "Box-and-whisker Plots"

:'''A'''uthor? Different authors noted for the different works

:'''S'''ource? Original materials are linked for each work

:'''L'''icense? The different licenses (Creative Commons Attribution for Collaborative Statistics and Creative Commons Attribution-Noncommercial-ShareAlike for the Khan Academy video) are spelled out and linked for each work

:Lastly, it is clear which attribution belongs to which work.

You can visit the [http://www.saylor.org/courses/ma121/ Saylor.org Introduction to Statistics course page] to see how they marked it up directly.
<hr>

=== Publishing a web page for attribution ===
As stated above, recommended attribution depends on the medium you're working with. For media such as offline materials, video, audio, and images, consider publishing a web page with attribution information. For example, on a webpage featuring your audio recording, provide a credit list of material you used that adheres to best practices above. Doing so allows not only your material, but the materials you attribute, to be found by search engines and other web discovery tools. If possible within the medium, make the Author, Source, and License links the user can follow.

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">'''Example:'''<br>This video features the song [http://ccmixter.org/media/files/victor/6374 "Desaprendere (Treatment)"] by [http://fourstones.net/ fourstones], available under a Creative Commons [http://creativecommons.org/licenses/by-nc/2.5/ Attribution-Noncommercial] license.</div>

<hr>

==Attributing public domain materials==
Although attribution is not a legal obligation under [https://creativecommons.org/share-your-work/public-domain/cc0/ CC0 dedication]’s or [https://creativecommons.org/share-your-work/public-domain/pdm/ CC Public Domain Mark]’s licensing terms, we recommend that you consider providing attribution to the source for public domain materials when it is reasonable to do so. Attribution of public domain works not only encourages institutions to digitize and share more public domain materials in their physical collections, but also empowers users to easily locate the original source.

The following public domain image is digitized and hosted by the Rijksmuseum (the national museum of the Netherlands). The Rijksmuseum has applied a CC0 dedication to the image.

:[[File:Attributing_the_milkmaid.png|300px]]

You may provide credit in the following format:

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">“[http://hdl.handle.net/10934/RM0001.COLLECT.6417 The Milkmaid]” by Vermeer. The Rijksmuseum collection. The image is dedicated to the public domain under [https://creativecommons.org/share-your-work/public-domain/cc0/ CC0]. </div>

In most cases, people credit the source regardless of the work’s copyright status. Especially in an academic setting, providing source information about other people’s works has long been considered crucial to academic integrity. Copyright cannot be the only checkbox when deciding whether a source will be attributed.

== Common pitfalls ==

Below are some practices that you may wish to avoid. These practices are not always contrary to the Creative Commons licensing terms, but they often make it more challenging for users to find the original source and/or author.

'''Attribute in alt text'''
:Alt text is intended to provide accessible information about visual materials for users with cognitive disabilities or visual impairment. Using this field for licensing information makes browsing difficult for those users.

'''Attribute in metadata fields only'''
:While it is great to include attribution in metadata fields (such as EXIF for images), in most cases this is not the only place to include attribution information. This is because many users are likely not aware of, and will never see, attribution information included in metadata.

'''Credit authors by names other than the ones they have selected'''
:Many people believe that attribution must be given to the real name of the author of a work, but this is not the case — always give attribution to the name the author has specified, even if it is a pseudonym. If the author does not give a name or explicitly requests to be anonymous, you must give the other attribution information (i.e., “T” and “SL” from “TASL”) without crediting the author.

'''Credit a site (or Creative Commons itself!) instead of the author'''
:Unless an author specifically requests users to only credit a site, crediting the site where you have found the material cannot substitute crediting the author. An author may have uploaded material to a site under a CC license, but in most cases, the copyright is still held by the author, and it is the copyright holder who needs to be credited. For example, many photos sourced from Wikimedia Commons are attributed to Wikimedia when they must be attributed to the authors.

== Other guides to attribution ==

* [http://creativecommons.org.au/materials/attribution.pdf Attributing Creative Commons Material] (pdf) - Creative Commons Australia's publication is full of examples with colorful imagery.
* [http://www.newmediarights.org/guide/how_to/creative_commons/best_practices_creative_commons_attributions How to attribute works you reuse under a Creative Commons license] by New Media Rights provides real world examples by different media type

[[Category:Marking]]
[[Category:Licensing]]
[[Category:Community]]
[[Category:Media]]
[[Category:HOWTO]]
[[Category:Guide]]
{{Best Practice}}

Recommended practices for attribution

2022-12-07T20:23:25Z

CCID-yuanxiaoxu: /* Basic components of attribution */

You can use CC-licensed materials as long as you follow the license conditions. One condition of all CC licenses is attribution: crediting the author and noting the source and the license. Generally speaking, attribution must reasonably include all relevant information supplied by the licensor. Because each use case is different, you can decide what form of attribution is most suitable for your specific situation. The following examples are intended to illustrate what typical prudent practices look like. We expect community norms and expectations to evolve with time, and will adapt this guide accordingly.
In addition to attribution, there are also [https://wiki.creativecommons.org/wiki/Considerations_for_licensors_and_licensees#Considerations_for_licensees|other things to consider as a licensor or a licensee]. If you are a licensor and would like to learn how to license your own material, take a look at [https://wiki.creativecommons.org/wiki/Marking_your_work_with_a_CC_license our guide on how to mark your work with a CC license].

==Basic components of attribution==

[[File:19th_century_tassel_from_Smithsonian.jpeg|290px|left]]

Whenever you are reusing CC licensed works, we recommend that the attribution include the '''T'''itle, '''A'''uthor, '''S'''ource, and '''L'''icense. This is true whether you’re sharing the work as-is or if you have made an adaptation. To remember these attribution elements, it’s helpful to think of the acronym: '''TASL'''.

Let’s now go through '''TASL''' — we will explain each element in more detail:

'''Title''': What is the name of the work?

:If a title was provided for the work, include it as a part of the attribution. Sometimes a title is not provided; in that case, there’s no need to mention the title.

:The inclusion of title is a requirement of all CC licenses version 3.0 or earlier, and it is optional for the 4.0 suites. See [[https://wiki.creativecommons.org/wiki/Recommended_practices_for_attribution#License_details License details]].

'''Author''': Who allows you to use the work?

:We often use “author” as a shorthand when we are, legally speaking, referring to the “licensor” (a.k.a., the “copyright holder” or “rightsholder”). This is because, in most CC-licensed works, the licensor is the same person or entity as the author. When an author is licensing their work under a CC license, and has made their name available, include the author’s name as a component in your attribution. Sometimes, the licensor may want you to give credit to some other entity, like a company or institution, or the licensor may want to be credited by a pseudonym instead of their real name. In rare cases, the licensor may not want to be attributed at all. In all of these cases, do what the licensor requests.

:Sometimes, the author will also provide a copyright notice, which consists of the copyright symbol, year of publication, and the name of the author/licensor. Include the copyright notice as a part of your attribution if such information is provided.

'''Source''': Where can people find the work?

:Please make it possible for future users to find the source of the material by including a URL or hyperlink where the work resides. This often is where you found the work. If you found it somewhere other than the original site, try to include information about the original site where the work was first shared publicly. It is also better to use the original URL instead of a shortened link, whether you are hyperlinking or printing out the entire URL.

'''License''': How can you use the work?

:You must specify which CC license was applied to the work you are reusing. Each of the six different CC licenses come with distinct requirements for re-use. We recommend that you name and provide a link to the license, e.g., [http://creativecommons.org/licenses/by/4.0 CC BY 4.0] (http://creativecommons.org/licenses/by/4.0) for a work licensed under CC BY 4.0.

:Consider also including the “disclaimer of warranties,” which clarifies that the author makes no representations or warranties about the non-infringement or absence of other defects concerning the CC-licensed work. In plain English, this means that the users will use the work at their own risk.

:To sum up, if the licensor has provided any information related to TASL, consider including them in your attribution. We also recommend providing links to the Title, Author, Source, and License, where possible, so future users can easily access the information they need on a work and the license terms.
<hr>
===Reasonable attribution===

The CC licenses ask you to be reasonable:

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 90%;">You may satisfy the attribution requirement in any reasonable manner based on the medium, means and context in which the Licensed Material is used. For example, it may be reasonable to satisfy some or all of the conditions by retaining a copyright notice, or by providing a URI or hyperlink associated with the Licensed Material, if the copyright notice or webpage includes some or all of the required information.</div>

There is no single best or correct way of attribution, as long as your attribution is reasonable and suited to the medium you're working with. That being said, please include attribution somehow, even if it's a link to an About page that has the relevant info. (More on different media below.)
<hr>

===License details===

If you have any doubts or questions, you can read the complete attribution requirements which are spelled out in detail in the legal code of every CC license, eg. http://creativecommons.org/licenses/by/4.0/legalcode This [[License_Versions#Detailed_attribution_comparison_chart|chart compares the detailed requirements across all versions of CC licenses.]]

==Examples of attribution==

We will now look at some examples in different media.

===Attributing an image===

Here is a photo. Below, we will go over some good and bad examples of how people might attribute it.

[[File:8256206923_c77e85319e_n.jpg]]
<hr>

====This is a great attribution====
<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">
"[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Creative Commons 10th Birthday Celebration San Francisco]" by [http://www.flickr.com/photos/sixteenmilesofstring/ Timothy Vollmer] is licensed under [http://creativecommons.org/licenses/by/4.0/ CC BY 4.0]</div>

''Let’s go through TASL:''
:'''T'''itle? "Creative Commons 10th Birthday Celebration San Francisco"
:'''A'''uthor? "[http://www.flickr.com/photos/sixteenmilesofstring/ Timothy Vollmer]" - linked to his profile page
:'''S'''ource? "[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Creative Commons 10th Birthday Celebration San Francisco]" - linked to original Flickr page
:'''L'''icense? "[http://creativecommons.org/licenses/by/4.0/ CC BY 4.0]" - linked to license deed

Most importantly, this attribution reasonably includes all the relevant information provided by the author.
<hr>

====This is a pretty good attribution====

<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Photo] by Timothy Vollmer/ [http://creativecommons.org/licenses/by/2.0/ CC BY]</div>

''Let’s go through TASL:''
:'''T'''itle? Title is not noted but at least the source is linked.
:'''A'''uthor? "Timothy Vollmer"
:'''S'''ource? "[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Photo]" - linked to original Flickr page
:'''L'''icense? "[http://creativecommons.org/licenses/by/4.0/ CC BY]" - linked to license deed

As you see, a good attribution includes all the essential '''TASL''' elements, even though they may not mirror the format of credit the author has requested.
<hr>

==== This is an incorrect attribution====
<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">Photo: Creative Commons</div>

''Let’s go through TASL'':
:'''T'''itle? Title of the image is not noted
:'''A'''uthor? Author is not noted (It is a common mistake to attribute CC-licensed photos to CC, but Creative Commons is not the author!)
:'''S'''ource? No link to the original source
:'''L'''icense? There is no mention of a license nor a link to the license. "Creative Commons" is the name of an organization; it does not equate to any of the licenses maintained by the Creative Commons.
<hr>

====This is a great attribution for an image you modified slightly====
:[[File:Cropped_tvol_cupcake.png|300px]]

<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">"[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Creative Commons 10th Birthday Celebration San Francisco]" by [http://www.flickr.com/photos/sixteenmilesofstring/ Timothy Vollmer], used under [http://creativecommons.org/licenses/by/4.0/ CC BY 4.0] / Cropped from original</div>

Here, information on '''T'''itle, '''A'''uthor, '''S'''ource, and '''L'''icense are all included as requested by the author. The slight modification is also noted and briefly described.

Note if the modification changes the work’s meaning in a way that would be considered creative — that is, not a purely mechanical change or a simple crop/excerpt that keeps the original message undistorted, it would be considered creating a new adaptation of the original work. You cannot rely on a CC license that does not allow adaptation (e.g., CC BY-ND or CC BY-NC-ND) when making such modifications.

<hr>

====This is a great attribution for when you have created an adaptation====

:[[File:8256206923_c77e85319e_n_90fied.jpg|300px]]

<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">This work, "90fied", is adapted from "[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Creative Commons 10th Birthday Celebration San Francisco]" by [http://www.flickr.com/photos/sixteenmilesofstring/ Timothy Vollmer], used under [http://creativecommons.org/licenses/by/4.0/ CC BY 4.0]. "90fied" is licensed under [http://creativecommons.org/licenses/by/4.0/ CC BY 4.0] by [Your name here].</div>

''Let’s go through TASL:''

Original '''T'''itle, '''A'''uthor, '''S'''ource, and '''L'''icense are all noted.

The original work is referenced and the fact that it is an adaptation is also noted, so viewers can see what has changed.

The author and other attribution information for the new adapted work is also noted.

Note: If you're at a point where you are licensing works that are adaptations, go to [[Marking your work with a CC license]].
<hr>

===Attributing music===

====When you incorporate music in an audio or video recording====
Music (both the underlying composition and the sound recordings) — such as a song, or a recording of natural sounds — can be attributed within the audio/video, and in the description text of the audio/video. How to attribute a CC licensed music in an audio or video recording will largely depend on what is reasonable for a chosen medium and platform.

Caution: Licenses with “ND” do not allow for adaptations. Your use of CC-licensed music is often an adaptation!

It is considered adaptation if you incorporate CC-licensed music into your work in a way that the CC-licensed music can no longer be seen as a stand-alone piece. For example, if you are using a song as background music in a podcast or in a video, it is considered an adaptation of the song.

Keep in mind that CC BY-ND and CC BY-NC-ND do not allow adaptations (although you may be authorized by law to do so, such as under a users’ right like fair use, or you may ask for the author’s permission independent of the CC license).
<hr>

[[File:Smithsonian_music_stand.jpeg|left|250px]]

=====This is a great attribution of background music in a podcast or a video=====
When reasonable to do so, we recommend that you include attribution both in the description box and in the podcast recording or the video recording itself.

If you are using the following song in a podcast: ‘Day Bird’ by Broke for Free ([https://brokeforfree.com brokeforfree.com]), this would be a great way to provide attribution (which you can see in [https://soundcloud.com/wearecc/open-minds-podcast-catherine-stihler-ceo-of-creative-commons the Creative Commons podcast]) —

:At the end of the podcast audio recording, the host says:
:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 90%;">Special thanks to the musician Broke for Free, whose track “Day Bird” you heard at the beginning of this episode and you are listening to right now. It's under the Creative Commons Attribution License, meaning it's free for anyone to use. You can find it at the Free Music Archive—freemusicarchive.org</div>

:In the description box, the information text reads:
:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 90%;">Theme music: “Day Bird” by Broke for Free ([https://brokeforfree.com brokeforfree.com]). Available for use under the CC BY 3.0 license ([https://creativecommons.org/licenses/by/3.0/ creativecommons.org/licenses/by/3.0/]), at [https://freemusicarchive.org/music/Broke_For_Free/Directionless_EP/Broke_For_Free_-_Directionless_EP_-_03_Day_Bird|the Free Music Archive].</div>

''Let’s go through TASL:''

:'''T'''itle? Both the recording and the description box include the title of the work, “Day Bird”

:'''A'''uthor? "Broke for Free," again, noted both in the recording and in the description box

:'''S'''ource? Both the author’s page and the archive’s page are included with links

:'''L'''icense? "CC BY 3.0" — linked to license deed

You cannot talk over, or remix, music licensed under CC BY-ND or CC BY-NC-ND.

<hr>

=====This is a bad attribution of background music in a podcast or a video=====

A bad attribution is one where you do not provide enough information for a user to find the music you are using. The following is a bad attribution for the same song:

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">No attribution is included in the podcast recording or the video itself.

In the description box, it says: “ Creative Commons music.”</div>

''Let’s go through TASL:''

:'''T'''itle? Title is not noted

:'''A'''uthor? Author is not noted

:'''S'''ource? Source is not noted; users cannot find the specific song used in the podcast

:'''L'''icense? No information on the CC license

The attribution information is not sufficient for people to find the song you have re-used.
<hr>

====When you are not adding new elements to the music====
When you re-use music without adding new elements to it, you are not making an adaptation. In that case, you can rely on any of the CC licenses, including CC BY-ND and CC BY-NC-ND. We recommend providing attribution information in writing.

[[File:Wiki_page_attributing_night_owl.png|400px]]

On [https://commons.wikimedia.org/wiki/File:Broke_For_Free_-_01_-_Night_Owl.ogg this Wikipedia page], you can see an example of great attribution for the sharing another soundtrack, “Night Owl” by Broke for Free, when it’s without adaptation.

''Let’s go through TASL:''

'''T'''itle? Title of the work, “Night Owl,” is noted

'''A'''uthor? "Broke for Free," noted and linked to the author’s webpage

'''S'''ource? A link is provided for the source

'''L'''icense? "CC BY 3.0" — linked to license deed
<hr>

===Attributing text===
Let’s take [https://github.com/getify/You-Dont-Know-JS ''You Don't Know JS Yet'' (2nd Edition)] as an example, and go over what your attribution may look like if you reuse the book series. The information under the “License & Copyright” section looks like this on the webpage where the book series was originally shared:
:[[File:attributing_You_Don't_Know_JS_Yet_(2nd_Edition).png|200px]]

We recommend that you retain all the information provided by the author of the book series when it is reasonable for you to do so. For example, if you are distributing digital copies or excerpts of the book series in a free seminar, or using parts of the book in a free online course or presentation, the attribution will likely look something like this:

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">This chapter is from “[https://github.com/getify/You-Dont-Know-JS You Don't Know JS Yet (2nd Edition)]” by [https://github.com/getify Kyle Simpson]. The book is licensed under the [https://creativecommons.org/licenses/by-nc-nd/4.0/ CC BY-NC-ND 4.0 license]. © 2019-2022 Kyle Simpson.</div>

On the other hand, if you are distributing hard copies of the book series or excerpts from the book series, instead of using hyperlinks, you may wish to include the links so it’s easier for users to locate the original source of the book, the author, and the CC license:

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">This chapter is from “You Don't Know JS Yet (2nd Edition)” (https://github.com/getify/You-Dont-Know-JS) by Kyle Simpson (https://github.com/getify). The book is licensed under the CC BY-NC-ND 4.0 license (https://creativecommons.org/licenses/by-nc-nd/4.0/). © 2019-2022 Kyle Simpson.</div>

Note that the CC BY-NC-ND license includes the NoDerivatives requirement, which indicates that no adaptations are allowed. You cannot make any adaptations relying on the CC BY-NC-CD license the author chose for the book. If you would like to make a translation of the book, for example, you will need to ask the author for permission first.

The CC BY-NC-ND license also includes the NonCommercial requirement. To learn more, take a look at [https://en.wikipedia.org/wiki/Creative_Commons_NonCommercial_license our guide about the NonCommercial licenses].
<hr>

=== Attributing materials from multiple sources ===

:[[File:Saylor_marking_example.jpg]]

''Let’s go through TASL:''

:'''T'''itle? Specific works are named, e.g., "Box-and-whisker Plots"

:'''A'''uthor? Different authors noted for the different works

:'''S'''ource? Original materials are linked for each work

:'''L'''icense? The different licenses (Creative Commons Attribution for Collaborative Statistics and Creative Commons Attribution-Noncommercial-ShareAlike for the Khan Academy video) are spelled out and linked for each work

:Lastly, it is clear which attribution belongs to which work.

You can visit the [http://www.saylor.org/courses/ma121/ Saylor.org Introduction to Statistics course page] to see how they marked it up directly.
<hr>

=== Publishing a web page for attribution ===
As stated above, recommended attribution depends on the medium you're working with. For media such as offline materials, video, audio, and images, consider publishing a web page with attribution information. For example, on a webpage featuring your audio recording, provide a credit list of material you used that adheres to best practices above. Doing so allows not only your material, but the materials you attribute, to be found by search engines and other web discovery tools. If possible within the medium, make the Author, Source, and License links the user can follow.

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">'''Example:'''<br>This video features the song [http://ccmixter.org/media/files/victor/6374 "Desaprendere (Treatment)"] by [http://fourstones.net/ fourstones], available under a Creative Commons [http://creativecommons.org/licenses/by-nc/2.5/ Attribution-Noncommercial] license.</div>

<hr>

==Attributing public domain materials==
Although attribution is not a legal obligation under [https://creativecommons.org/share-your-work/public-domain/cc0/ CC0 dedication]’s or [https://creativecommons.org/share-your-work/public-domain/pdm/ CC Public Domain Mark]’s licensing terms, we recommend that you consider providing attribution to the source for public domain materials when it is reasonable to do so. Attribution of public domain works not only encourages institutions to digitize and share more public domain materials in their physical collections, but also empowers users to easily locate the original source.

The following public domain image is digitized and hosted by the Rijksmuseum (the national museum of the Netherlands). The Rijksmuseum has applied a CC0 dedication to the image.

:[[File:Attributing_the_milkmaid.png|300px]]

You may provide credit in the following format:

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">“[http://hdl.handle.net/10934/RM0001.COLLECT.6417 The Milkmaid]” by Vermeer. The Rijksmuseum collection. The image is dedicated to the public domain under [https://creativecommons.org/share-your-work/public-domain/cc0/ CC0]. </div>

In most cases, people credit the source regardless of the work’s copyright status. Especially in an academic setting, providing source information about other people’s works has long been considered crucial to academic integrity. Copyright cannot be the only checkbox when deciding whether a source will be attributed.

== Common pitfalls ==

Below are some practices that you may wish to avoid. These practices are not always contrary to the Creative Commons licensing terms, but they often make it more challenging for users to find the original source and/or author.

'''Attribute in alt text'''
:Alt text is intended to provide accessible information about visual materials for users with cognitive disabilities or visual impairment. Using this field for licensing information makes browsing difficult for those users.

'''Attribute in metadata fields only'''
:While it is great to include attribution in metadata fields (such as EXIF for images), in most cases this is not the only place to include attribution information. This is because many users are likely not aware of, and will never see, attribution information included in metadata.

'''Credit authors by names other than the ones they have selected'''
:Many people believe that attribution must be given to the real name of the author of a work, but this is not the case — always give attribution to the name the author has specified, even if it is a pseudonym. If the author does not give a name or explicitly requests to be anonymous, you must give the other attribution information (i.e., “T” and “SL” from “TASL”) without crediting the author.

'''Credit a site (or Creative Commons itself!) instead of the author'''
:Unless an author specifically requests users to only credit a site, crediting the site where you have found the material cannot substitute crediting the author. An author may have uploaded material to a site under a CC license, but in most cases, the copyright is still held by the author, and it is the copyright holder who needs to be credited. For example, many photos sourced from Wikimedia Commons are attributed to Wikimedia when they must be attributed to the authors.

== Other guides to attribution ==

* [http://creativecommons.org.au/materials/attribution.pdf Attributing Creative Commons Material] (pdf) - Creative Commons Australia's publication is full of examples with colorful imagery.
* [http://www.newmediarights.org/guide/how_to/creative_commons/best_practices_creative_commons_attributions How to attribute works you reuse under a Creative Commons license] by New Media Rights provides real world examples by different media type

[[Category:Marking]]
[[Category:Licensing]]
[[Category:Community]]
[[Category:Media]]
[[Category:HOWTO]]
[[Category:Guide]]
{{Best Practice}}

Recommended practices for attribution

2022-12-07T20:22:38Z

CCID-yuanxiaoxu: /* Devil in the details */

You can use CC-licensed materials as long as you follow the license conditions. One condition of all CC licenses is attribution: crediting the author and noting the source and the license. Generally speaking, attribution must reasonably include all relevant information supplied by the licensor. Because each use case is different, you can decide what form of attribution is most suitable for your specific situation. The following examples are intended to illustrate what typical prudent practices look like. We expect community norms and expectations to evolve with time, and will adapt this guide accordingly.
In addition to attribution, there are also [https://wiki.creativecommons.org/wiki/Considerations_for_licensors_and_licensees#Considerations_for_licensees|other things to consider as a licensor or a licensee]. If you are a licensor and would like to learn how to license your own material, take a look at [https://wiki.creativecommons.org/wiki/Marking_your_work_with_a_CC_license our guide on how to mark your work with a CC license].

==Basic components of attribution==

[[File:19th_century_tassel_from_Smithsonian.jpeg|290px|left]]

Whenever you are reusing CC licensed works, we recommend that the attribution include the '''T'''itle, '''A'''uthor, '''S'''ource, and '''L'''icense. This is true whether you’re sharing the work as-is or if you have made an adaptation. To remember these attribution elements, it’s helpful to think of the acronym: '''TASL'''.

Let’s now go through '''TASL''' — we will explain each element in more detail:

'''Title''': What is the name of the work?

:If a title was provided for the work, include it as a part of the attribution. Sometimes a title is not provided; in that case, there’s no need to mention the title.

:The inclusion of title is a requirement of all CC licenses version 3.0 or earlier, and it is optional for the 4.0 suites. See Devil in the details.

'''Author''': Who allows you to use the work?

:We often use “author” as a shorthand when we are, legally speaking, referring to the “licensor” (a.k.a., the “copyright holder” or “rightsholder”). This is because, in most CC-licensed works, the licensor is the same person or entity as the author. When an author is licensing their work under a CC license, and has made their name available, include the author’s name as a component in your attribution. Sometimes, the licensor may want you to give credit to some other entity, like a company or institution, or the licensor may want to be credited by a pseudonym instead of their real name. In rare cases, the licensor may not want to be attributed at all. In all of these cases, do what the licensor requests.

:Sometimes, the author will also provide a copyright notice, which consists of the copyright symbol, year of publication, and the name of the author/licensor. Include the copyright notice as a part of your attribution if such information is provided.

'''Source''': Where can people find the work?

:Please make it possible for future users to find the source of the material by including a URL or hyperlink where the work resides. This often is where you found the work. If you found it somewhere other than the original site, try to include information about the original site where the work was first shared publicly. It is also better to use the original URL instead of a shortened link, whether you are hyperlinking or printing out the entire URL.

'''License''': How can you use the work?

:You must specify which CC license was applied to the work you are reusing. Each of the six different CC licenses come with distinct requirements for re-use. We recommend that you name and provide a link to the license, e.g., [http://creativecommons.org/licenses/by/4.0 CC BY 4.0] (http://creativecommons.org/licenses/by/4.0) for a work licensed under CC BY 4.0.

:Consider also including the “disclaimer of warranties,” which clarifies that the author makes no representations or warranties about the non-infringement or absence of other defects concerning the CC-licensed work. In plain English, this means that the users will use the work at their own risk.

:To sum up, if the licensor has provided any information related to TASL, consider including them in your attribution. We also recommend providing links to the Title, Author, Source, and License, where possible, so future users can easily access the information they need on a work and the license terms.
<hr>
===Reasonable attribution===

The CC licenses ask you to be reasonable:

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 90%;">You may satisfy the attribution requirement in any reasonable manner based on the medium, means and context in which the Licensed Material is used. For example, it may be reasonable to satisfy some or all of the conditions by retaining a copyright notice, or by providing a URI or hyperlink associated with the Licensed Material, if the copyright notice or webpage includes some or all of the required information.</div>

There is no single best or correct way of attribution, as long as your attribution is reasonable and suited to the medium you're working with. That being said, please include attribution somehow, even if it's a link to an About page that has the relevant info. (More on different media below.)
<hr>

===License details===

If you have any doubts or questions, you can read the complete attribution requirements which are spelled out in detail in the legal code of every CC license, eg. http://creativecommons.org/licenses/by/4.0/legalcode This [[License_Versions#Detailed_attribution_comparison_chart|chart compares the detailed requirements across all versions of CC licenses.]]

==Examples of attribution==

We will now look at some examples in different media.

===Attributing an image===

Here is a photo. Below, we will go over some good and bad examples of how people might attribute it.

[[File:8256206923_c77e85319e_n.jpg]]
<hr>

====This is a great attribution====
<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">
"[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Creative Commons 10th Birthday Celebration San Francisco]" by [http://www.flickr.com/photos/sixteenmilesofstring/ Timothy Vollmer] is licensed under [http://creativecommons.org/licenses/by/4.0/ CC BY 4.0]</div>

''Let’s go through TASL:''
:'''T'''itle? "Creative Commons 10th Birthday Celebration San Francisco"
:'''A'''uthor? "[http://www.flickr.com/photos/sixteenmilesofstring/ Timothy Vollmer]" - linked to his profile page
:'''S'''ource? "[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Creative Commons 10th Birthday Celebration San Francisco]" - linked to original Flickr page
:'''L'''icense? "[http://creativecommons.org/licenses/by/4.0/ CC BY 4.0]" - linked to license deed

Most importantly, this attribution reasonably includes all the relevant information provided by the author.
<hr>

====This is a pretty good attribution====

<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Photo] by Timothy Vollmer/ [http://creativecommons.org/licenses/by/2.0/ CC BY]</div>

''Let’s go through TASL:''
:'''T'''itle? Title is not noted but at least the source is linked.
:'''A'''uthor? "Timothy Vollmer"
:'''S'''ource? "[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Photo]" - linked to original Flickr page
:'''L'''icense? "[http://creativecommons.org/licenses/by/4.0/ CC BY]" - linked to license deed

As you see, a good attribution includes all the essential '''TASL''' elements, even though they may not mirror the format of credit the author has requested.
<hr>

==== This is an incorrect attribution====
<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">Photo: Creative Commons</div>

''Let’s go through TASL'':
:'''T'''itle? Title of the image is not noted
:'''A'''uthor? Author is not noted (It is a common mistake to attribute CC-licensed photos to CC, but Creative Commons is not the author!)
:'''S'''ource? No link to the original source
:'''L'''icense? There is no mention of a license nor a link to the license. "Creative Commons" is the name of an organization; it does not equate to any of the licenses maintained by the Creative Commons.
<hr>

====This is a great attribution for an image you modified slightly====
:[[File:Cropped_tvol_cupcake.png|300px]]

<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">"[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Creative Commons 10th Birthday Celebration San Francisco]" by [http://www.flickr.com/photos/sixteenmilesofstring/ Timothy Vollmer], used under [http://creativecommons.org/licenses/by/4.0/ CC BY 4.0] / Cropped from original</div>

Here, information on '''T'''itle, '''A'''uthor, '''S'''ource, and '''L'''icense are all included as requested by the author. The slight modification is also noted and briefly described.

Note if the modification changes the work’s meaning in a way that would be considered creative — that is, not a purely mechanical change or a simple crop/excerpt that keeps the original message undistorted, it would be considered creating a new adaptation of the original work. You cannot rely on a CC license that does not allow adaptation (e.g., CC BY-ND or CC BY-NC-ND) when making such modifications.

<hr>

====This is a great attribution for when you have created an adaptation====

:[[File:8256206923_c77e85319e_n_90fied.jpg|300px]]

<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">This work, "90fied", is adapted from "[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Creative Commons 10th Birthday Celebration San Francisco]" by [http://www.flickr.com/photos/sixteenmilesofstring/ Timothy Vollmer], used under [http://creativecommons.org/licenses/by/4.0/ CC BY 4.0]. "90fied" is licensed under [http://creativecommons.org/licenses/by/4.0/ CC BY 4.0] by [Your name here].</div>

''Let’s go through TASL:''

Original '''T'''itle, '''A'''uthor, '''S'''ource, and '''L'''icense are all noted.

The original work is referenced and the fact that it is an adaptation is also noted, so viewers can see what has changed.

The author and other attribution information for the new adapted work is also noted.

Note: If you're at a point where you are licensing works that are adaptations, go to [[Marking your work with a CC license]].
<hr>

===Attributing music===

====When you incorporate music in an audio or video recording====
Music (both the underlying composition and the sound recordings) — such as a song, or a recording of natural sounds — can be attributed within the audio/video, and in the description text of the audio/video. How to attribute a CC licensed music in an audio or video recording will largely depend on what is reasonable for a chosen medium and platform.

Caution: Licenses with “ND” do not allow for adaptations. Your use of CC-licensed music is often an adaptation!

It is considered adaptation if you incorporate CC-licensed music into your work in a way that the CC-licensed music can no longer be seen as a stand-alone piece. For example, if you are using a song as background music in a podcast or in a video, it is considered an adaptation of the song.

Keep in mind that CC BY-ND and CC BY-NC-ND do not allow adaptations (although you may be authorized by law to do so, such as under a users’ right like fair use, or you may ask for the author’s permission independent of the CC license).
<hr>

[[File:Smithsonian_music_stand.jpeg|left|250px]]

=====This is a great attribution of background music in a podcast or a video=====
When reasonable to do so, we recommend that you include attribution both in the description box and in the podcast recording or the video recording itself.

If you are using the following song in a podcast: ‘Day Bird’ by Broke for Free ([https://brokeforfree.com brokeforfree.com]), this would be a great way to provide attribution (which you can see in [https://soundcloud.com/wearecc/open-minds-podcast-catherine-stihler-ceo-of-creative-commons the Creative Commons podcast]) —

:At the end of the podcast audio recording, the host says:
:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 90%;">Special thanks to the musician Broke for Free, whose track “Day Bird” you heard at the beginning of this episode and you are listening to right now. It's under the Creative Commons Attribution License, meaning it's free for anyone to use. You can find it at the Free Music Archive—freemusicarchive.org</div>

:In the description box, the information text reads:
:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 90%;">Theme music: “Day Bird” by Broke for Free ([https://brokeforfree.com brokeforfree.com]). Available for use under the CC BY 3.0 license ([https://creativecommons.org/licenses/by/3.0/ creativecommons.org/licenses/by/3.0/]), at [https://freemusicarchive.org/music/Broke_For_Free/Directionless_EP/Broke_For_Free_-_Directionless_EP_-_03_Day_Bird|the Free Music Archive].</div>

''Let’s go through TASL:''

:'''T'''itle? Both the recording and the description box include the title of the work, “Day Bird”

:'''A'''uthor? "Broke for Free," again, noted both in the recording and in the description box

:'''S'''ource? Both the author’s page and the archive’s page are included with links

:'''L'''icense? "CC BY 3.0" — linked to license deed

You cannot talk over, or remix, music licensed under CC BY-ND or CC BY-NC-ND.

<hr>

=====This is a bad attribution of background music in a podcast or a video=====

A bad attribution is one where you do not provide enough information for a user to find the music you are using. The following is a bad attribution for the same song:

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">No attribution is included in the podcast recording or the video itself.

In the description box, it says: “ Creative Commons music.”</div>

''Let’s go through TASL:''

:'''T'''itle? Title is not noted

:'''A'''uthor? Author is not noted

:'''S'''ource? Source is not noted; users cannot find the specific song used in the podcast

:'''L'''icense? No information on the CC license

The attribution information is not sufficient for people to find the song you have re-used.
<hr>

====When you are not adding new elements to the music====
When you re-use music without adding new elements to it, you are not making an adaptation. In that case, you can rely on any of the CC licenses, including CC BY-ND and CC BY-NC-ND. We recommend providing attribution information in writing.

[[File:Wiki_page_attributing_night_owl.png|400px]]

On [https://commons.wikimedia.org/wiki/File:Broke_For_Free_-_01_-_Night_Owl.ogg this Wikipedia page], you can see an example of great attribution for the sharing another soundtrack, “Night Owl” by Broke for Free, when it’s without adaptation.

''Let’s go through TASL:''

'''T'''itle? Title of the work, “Night Owl,” is noted

'''A'''uthor? "Broke for Free," noted and linked to the author’s webpage

'''S'''ource? A link is provided for the source

'''L'''icense? "CC BY 3.0" — linked to license deed
<hr>

===Attributing text===
Let’s take [https://github.com/getify/You-Dont-Know-JS ''You Don't Know JS Yet'' (2nd Edition)] as an example, and go over what your attribution may look like if you reuse the book series. The information under the “License & Copyright” section looks like this on the webpage where the book series was originally shared:
:[[File:attributing_You_Don't_Know_JS_Yet_(2nd_Edition).png|200px]]

We recommend that you retain all the information provided by the author of the book series when it is reasonable for you to do so. For example, if you are distributing digital copies or excerpts of the book series in a free seminar, or using parts of the book in a free online course or presentation, the attribution will likely look something like this:

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">This chapter is from “[https://github.com/getify/You-Dont-Know-JS You Don't Know JS Yet (2nd Edition)]” by [https://github.com/getify Kyle Simpson]. The book is licensed under the [https://creativecommons.org/licenses/by-nc-nd/4.0/ CC BY-NC-ND 4.0 license]. © 2019-2022 Kyle Simpson.</div>

On the other hand, if you are distributing hard copies of the book series or excerpts from the book series, instead of using hyperlinks, you may wish to include the links so it’s easier for users to locate the original source of the book, the author, and the CC license:

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">This chapter is from “You Don't Know JS Yet (2nd Edition)” (https://github.com/getify/You-Dont-Know-JS) by Kyle Simpson (https://github.com/getify). The book is licensed under the CC BY-NC-ND 4.0 license (https://creativecommons.org/licenses/by-nc-nd/4.0/). © 2019-2022 Kyle Simpson.</div>

Note that the CC BY-NC-ND license includes the NoDerivatives requirement, which indicates that no adaptations are allowed. You cannot make any adaptations relying on the CC BY-NC-CD license the author chose for the book. If you would like to make a translation of the book, for example, you will need to ask the author for permission first.

The CC BY-NC-ND license also includes the NonCommercial requirement. To learn more, take a look at [https://en.wikipedia.org/wiki/Creative_Commons_NonCommercial_license our guide about the NonCommercial licenses].
<hr>

=== Attributing materials from multiple sources ===

:[[File:Saylor_marking_example.jpg]]

''Let’s go through TASL:''

:'''T'''itle? Specific works are named, e.g., "Box-and-whisker Plots"

:'''A'''uthor? Different authors noted for the different works

:'''S'''ource? Original materials are linked for each work

:'''L'''icense? The different licenses (Creative Commons Attribution for Collaborative Statistics and Creative Commons Attribution-Noncommercial-ShareAlike for the Khan Academy video) are spelled out and linked for each work

:Lastly, it is clear which attribution belongs to which work.

You can visit the [http://www.saylor.org/courses/ma121/ Saylor.org Introduction to Statistics course page] to see how they marked it up directly.
<hr>

=== Publishing a web page for attribution ===
As stated above, recommended attribution depends on the medium you're working with. For media such as offline materials, video, audio, and images, consider publishing a web page with attribution information. For example, on a webpage featuring your audio recording, provide a credit list of material you used that adheres to best practices above. Doing so allows not only your material, but the materials you attribute, to be found by search engines and other web discovery tools. If possible within the medium, make the Author, Source, and License links the user can follow.

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">'''Example:'''<br>This video features the song [http://ccmixter.org/media/files/victor/6374 "Desaprendere (Treatment)"] by [http://fourstones.net/ fourstones], available under a Creative Commons [http://creativecommons.org/licenses/by-nc/2.5/ Attribution-Noncommercial] license.</div>

<hr>

==Attributing public domain materials==
Although attribution is not a legal obligation under [https://creativecommons.org/share-your-work/public-domain/cc0/ CC0 dedication]’s or [https://creativecommons.org/share-your-work/public-domain/pdm/ CC Public Domain Mark]’s licensing terms, we recommend that you consider providing attribution to the source for public domain materials when it is reasonable to do so. Attribution of public domain works not only encourages institutions to digitize and share more public domain materials in their physical collections, but also empowers users to easily locate the original source.

The following public domain image is digitized and hosted by the Rijksmuseum (the national museum of the Netherlands). The Rijksmuseum has applied a CC0 dedication to the image.

:[[File:Attributing_the_milkmaid.png|300px]]

You may provide credit in the following format:

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">“[http://hdl.handle.net/10934/RM0001.COLLECT.6417 The Milkmaid]” by Vermeer. The Rijksmuseum collection. The image is dedicated to the public domain under [https://creativecommons.org/share-your-work/public-domain/cc0/ CC0]. </div>

In most cases, people credit the source regardless of the work’s copyright status. Especially in an academic setting, providing source information about other people’s works has long been considered crucial to academic integrity. Copyright cannot be the only checkbox when deciding whether a source will be attributed.

== Common pitfalls ==

Below are some practices that you may wish to avoid. These practices are not always contrary to the Creative Commons licensing terms, but they often make it more challenging for users to find the original source and/or author.

'''Attribute in alt text'''
:Alt text is intended to provide accessible information about visual materials for users with cognitive disabilities or visual impairment. Using this field for licensing information makes browsing difficult for those users.

'''Attribute in metadata fields only'''
:While it is great to include attribution in metadata fields (such as EXIF for images), in most cases this is not the only place to include attribution information. This is because many users are likely not aware of, and will never see, attribution information included in metadata.

'''Credit authors by names other than the ones they have selected'''
:Many people believe that attribution must be given to the real name of the author of a work, but this is not the case — always give attribution to the name the author has specified, even if it is a pseudonym. If the author does not give a name or explicitly requests to be anonymous, you must give the other attribution information (i.e., “T” and “SL” from “TASL”) without crediting the author.

'''Credit a site (or Creative Commons itself!) instead of the author'''
:Unless an author specifically requests users to only credit a site, crediting the site where you have found the material cannot substitute crediting the author. An author may have uploaded material to a site under a CC license, but in most cases, the copyright is still held by the author, and it is the copyright holder who needs to be credited. For example, many photos sourced from Wikimedia Commons are attributed to Wikimedia when they must be attributed to the authors.

== Other guides to attribution ==

* [http://creativecommons.org.au/materials/attribution.pdf Attributing Creative Commons Material] (pdf) - Creative Commons Australia's publication is full of examples with colorful imagery.
* [http://www.newmediarights.org/guide/how_to/creative_commons/best_practices_creative_commons_attributions How to attribute works you reuse under a Creative Commons license] by New Media Rights provides real world examples by different media type

[[Category:Marking]]
[[Category:Licensing]]
[[Category:Community]]
[[Category:Media]]
[[Category:HOWTO]]
[[Category:Guide]]
{{Best Practice}}

Recommended practices for attribution

2022-12-07T20:21:54Z

CCID-yuanxiaoxu:

You can use CC-licensed materials as long as you follow the license conditions. One condition of all CC licenses is attribution: crediting the author and noting the source and the license. Generally speaking, attribution must reasonably include all relevant information supplied by the licensor. Because each use case is different, you can decide what form of attribution is most suitable for your specific situation. The following examples are intended to illustrate what typical prudent practices look like. We expect community norms and expectations to evolve with time, and will adapt this guide accordingly.
In addition to attribution, there are also [https://wiki.creativecommons.org/wiki/Considerations_for_licensors_and_licensees#Considerations_for_licensees|other things to consider as a licensor or a licensee]. If you are a licensor and would like to learn how to license your own material, take a look at [https://wiki.creativecommons.org/wiki/Marking_your_work_with_a_CC_license our guide on how to mark your work with a CC license].

==Basic components of attribution==

[[File:19th_century_tassel_from_Smithsonian.jpeg|290px|left]]

Whenever you are reusing CC licensed works, we recommend that the attribution include the '''T'''itle, '''A'''uthor, '''S'''ource, and '''L'''icense. This is true whether you’re sharing the work as-is or if you have made an adaptation. To remember these attribution elements, it’s helpful to think of the acronym: '''TASL'''.

Let’s now go through '''TASL''' — we will explain each element in more detail:

'''Title''': What is the name of the work?

:If a title was provided for the work, include it as a part of the attribution. Sometimes a title is not provided; in that case, there’s no need to mention the title.

:The inclusion of title is a requirement of all CC licenses version 3.0 or earlier, and it is optional for the 4.0 suites. See Devil in the details.

'''Author''': Who allows you to use the work?

:We often use “author” as a shorthand when we are, legally speaking, referring to the “licensor” (a.k.a., the “copyright holder” or “rightsholder”). This is because, in most CC-licensed works, the licensor is the same person or entity as the author. When an author is licensing their work under a CC license, and has made their name available, include the author’s name as a component in your attribution. Sometimes, the licensor may want you to give credit to some other entity, like a company or institution, or the licensor may want to be credited by a pseudonym instead of their real name. In rare cases, the licensor may not want to be attributed at all. In all of these cases, do what the licensor requests.

:Sometimes, the author will also provide a copyright notice, which consists of the copyright symbol, year of publication, and the name of the author/licensor. Include the copyright notice as a part of your attribution if such information is provided.

'''Source''': Where can people find the work?

:Please make it possible for future users to find the source of the material by including a URL or hyperlink where the work resides. This often is where you found the work. If you found it somewhere other than the original site, try to include information about the original site where the work was first shared publicly. It is also better to use the original URL instead of a shortened link, whether you are hyperlinking or printing out the entire URL.

'''License''': How can you use the work?

:You must specify which CC license was applied to the work you are reusing. Each of the six different CC licenses come with distinct requirements for re-use. We recommend that you name and provide a link to the license, e.g., [http://creativecommons.org/licenses/by/4.0 CC BY 4.0] (http://creativecommons.org/licenses/by/4.0) for a work licensed under CC BY 4.0.

:Consider also including the “disclaimer of warranties,” which clarifies that the author makes no representations or warranties about the non-infringement or absence of other defects concerning the CC-licensed work. In plain English, this means that the users will use the work at their own risk.

:To sum up, if the licensor has provided any information related to TASL, consider including them in your attribution. We also recommend providing links to the Title, Author, Source, and License, where possible, so future users can easily access the information they need on a work and the license terms.
<hr>
===Reasonable attribution===

The CC licenses ask you to be reasonable:

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 90%;">You may satisfy the attribution requirement in any reasonable manner based on the medium, means and context in which the Licensed Material is used. For example, it may be reasonable to satisfy some or all of the conditions by retaining a copyright notice, or by providing a URI or hyperlink associated with the Licensed Material, if the copyright notice or webpage includes some or all of the required information.</div>

There is no single best or correct way of attribution, as long as your attribution is reasonable and suited to the medium you're working with. That being said, please include attribution somehow, even if it's a link to an About page that has the relevant info. (More on different media below.)
<hr>

===Devil in the details===

If you have any doubts or questions, you can read the complete attribution requirements which are spelled out in detail in the legal code of every CC license, eg. http://creativecommons.org/licenses/by/4.0/legalcode This [[License_Versions#Detailed_attribution_comparison_chart|chart compares the detailed requirements across all versions of CC licenses.]]

==Examples of attribution==

We will now look at some examples in different media.

===Attributing an image===

Here is a photo. Below, we will go over some good and bad examples of how people might attribute it.

[[File:8256206923_c77e85319e_n.jpg]]
<hr>

====This is a great attribution====
<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">
"[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Creative Commons 10th Birthday Celebration San Francisco]" by [http://www.flickr.com/photos/sixteenmilesofstring/ Timothy Vollmer] is licensed under [http://creativecommons.org/licenses/by/4.0/ CC BY 4.0]</div>

''Let’s go through TASL:''
:'''T'''itle? "Creative Commons 10th Birthday Celebration San Francisco"
:'''A'''uthor? "[http://www.flickr.com/photos/sixteenmilesofstring/ Timothy Vollmer]" - linked to his profile page
:'''S'''ource? "[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Creative Commons 10th Birthday Celebration San Francisco]" - linked to original Flickr page
:'''L'''icense? "[http://creativecommons.org/licenses/by/4.0/ CC BY 4.0]" - linked to license deed

Most importantly, this attribution reasonably includes all the relevant information provided by the author.
<hr>

====This is a pretty good attribution====

<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Photo] by Timothy Vollmer/ [http://creativecommons.org/licenses/by/2.0/ CC BY]</div>

''Let’s go through TASL:''
:'''T'''itle? Title is not noted but at least the source is linked.
:'''A'''uthor? "Timothy Vollmer"
:'''S'''ource? "[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Photo]" - linked to original Flickr page
:'''L'''icense? "[http://creativecommons.org/licenses/by/4.0/ CC BY]" - linked to license deed

As you see, a good attribution includes all the essential '''TASL''' elements, even though they may not mirror the format of credit the author has requested.
<hr>

==== This is an incorrect attribution====
<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">Photo: Creative Commons</div>

''Let’s go through TASL'':
:'''T'''itle? Title of the image is not noted
:'''A'''uthor? Author is not noted (It is a common mistake to attribute CC-licensed photos to CC, but Creative Commons is not the author!)
:'''S'''ource? No link to the original source
:'''L'''icense? There is no mention of a license nor a link to the license. "Creative Commons" is the name of an organization; it does not equate to any of the licenses maintained by the Creative Commons.
<hr>

====This is a great attribution for an image you modified slightly====
:[[File:Cropped_tvol_cupcake.png|300px]]

<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">"[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Creative Commons 10th Birthday Celebration San Francisco]" by [http://www.flickr.com/photos/sixteenmilesofstring/ Timothy Vollmer], used under [http://creativecommons.org/licenses/by/4.0/ CC BY 4.0] / Cropped from original</div>

Here, information on '''T'''itle, '''A'''uthor, '''S'''ource, and '''L'''icense are all included as requested by the author. The slight modification is also noted and briefly described.

Note if the modification changes the work’s meaning in a way that would be considered creative — that is, not a purely mechanical change or a simple crop/excerpt that keeps the original message undistorted, it would be considered creating a new adaptation of the original work. You cannot rely on a CC license that does not allow adaptation (e.g., CC BY-ND or CC BY-NC-ND) when making such modifications.

<hr>

====This is a great attribution for when you have created an adaptation====

:[[File:8256206923_c77e85319e_n_90fied.jpg|300px]]

<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">This work, "90fied", is adapted from "[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Creative Commons 10th Birthday Celebration San Francisco]" by [http://www.flickr.com/photos/sixteenmilesofstring/ Timothy Vollmer], used under [http://creativecommons.org/licenses/by/4.0/ CC BY 4.0]. "90fied" is licensed under [http://creativecommons.org/licenses/by/4.0/ CC BY 4.0] by [Your name here].</div>

''Let’s go through TASL:''

Original '''T'''itle, '''A'''uthor, '''S'''ource, and '''L'''icense are all noted.

The original work is referenced and the fact that it is an adaptation is also noted, so viewers can see what has changed.

The author and other attribution information for the new adapted work is also noted.

Note: If you're at a point where you are licensing works that are adaptations, go to [[Marking your work with a CC license]].
<hr>

===Attributing music===

====When you incorporate music in an audio or video recording====
Music (both the underlying composition and the sound recordings) — such as a song, or a recording of natural sounds — can be attributed within the audio/video, and in the description text of the audio/video. How to attribute a CC licensed music in an audio or video recording will largely depend on what is reasonable for a chosen medium and platform.

Caution: Licenses with “ND” do not allow for adaptations. Your use of CC-licensed music is often an adaptation!

It is considered adaptation if you incorporate CC-licensed music into your work in a way that the CC-licensed music can no longer be seen as a stand-alone piece. For example, if you are using a song as background music in a podcast or in a video, it is considered an adaptation of the song.

Keep in mind that CC BY-ND and CC BY-NC-ND do not allow adaptations (although you may be authorized by law to do so, such as under a users’ right like fair use, or you may ask for the author’s permission independent of the CC license).
<hr>

[[File:Smithsonian_music_stand.jpeg|left|250px]]

=====This is a great attribution of background music in a podcast or a video=====
When reasonable to do so, we recommend that you include attribution both in the description box and in the podcast recording or the video recording itself.

If you are using the following song in a podcast: ‘Day Bird’ by Broke for Free ([https://brokeforfree.com brokeforfree.com]), this would be a great way to provide attribution (which you can see in [https://soundcloud.com/wearecc/open-minds-podcast-catherine-stihler-ceo-of-creative-commons the Creative Commons podcast]) —

:At the end of the podcast audio recording, the host says:
:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 90%;">Special thanks to the musician Broke for Free, whose track “Day Bird” you heard at the beginning of this episode and you are listening to right now. It's under the Creative Commons Attribution License, meaning it's free for anyone to use. You can find it at the Free Music Archive—freemusicarchive.org</div>

:In the description box, the information text reads:
:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 90%;">Theme music: “Day Bird” by Broke for Free ([https://brokeforfree.com brokeforfree.com]). Available for use under the CC BY 3.0 license ([https://creativecommons.org/licenses/by/3.0/ creativecommons.org/licenses/by/3.0/]), at [https://freemusicarchive.org/music/Broke_For_Free/Directionless_EP/Broke_For_Free_-_Directionless_EP_-_03_Day_Bird|the Free Music Archive].</div>

''Let’s go through TASL:''

:'''T'''itle? Both the recording and the description box include the title of the work, “Day Bird”

:'''A'''uthor? "Broke for Free," again, noted both in the recording and in the description box

:'''S'''ource? Both the author’s page and the archive’s page are included with links

:'''L'''icense? "CC BY 3.0" — linked to license deed

You cannot talk over, or remix, music licensed under CC BY-ND or CC BY-NC-ND.

<hr>

=====This is a bad attribution of background music in a podcast or a video=====

A bad attribution is one where you do not provide enough information for a user to find the music you are using. The following is a bad attribution for the same song:

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">No attribution is included in the podcast recording or the video itself.

In the description box, it says: “ Creative Commons music.”</div>

''Let’s go through TASL:''

:'''T'''itle? Title is not noted

:'''A'''uthor? Author is not noted

:'''S'''ource? Source is not noted; users cannot find the specific song used in the podcast

:'''L'''icense? No information on the CC license

The attribution information is not sufficient for people to find the song you have re-used.
<hr>

====When you are not adding new elements to the music====
When you re-use music without adding new elements to it, you are not making an adaptation. In that case, you can rely on any of the CC licenses, including CC BY-ND and CC BY-NC-ND. We recommend providing attribution information in writing.

[[File:Wiki_page_attributing_night_owl.png|400px]]

On [https://commons.wikimedia.org/wiki/File:Broke_For_Free_-_01_-_Night_Owl.ogg this Wikipedia page], you can see an example of great attribution for the sharing another soundtrack, “Night Owl” by Broke for Free, when it’s without adaptation.

''Let’s go through TASL:''

'''T'''itle? Title of the work, “Night Owl,” is noted

'''A'''uthor? "Broke for Free," noted and linked to the author’s webpage

'''S'''ource? A link is provided for the source

'''L'''icense? "CC BY 3.0" — linked to license deed
<hr>

===Attributing text===
Let’s take [https://github.com/getify/You-Dont-Know-JS ''You Don't Know JS Yet'' (2nd Edition)] as an example, and go over what your attribution may look like if you reuse the book series. The information under the “License & Copyright” section looks like this on the webpage where the book series was originally shared:
:[[File:attributing_You_Don't_Know_JS_Yet_(2nd_Edition).png|200px]]

We recommend that you retain all the information provided by the author of the book series when it is reasonable for you to do so. For example, if you are distributing digital copies or excerpts of the book series in a free seminar, or using parts of the book in a free online course or presentation, the attribution will likely look something like this:

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">This chapter is from “[https://github.com/getify/You-Dont-Know-JS You Don't Know JS Yet (2nd Edition)]” by [https://github.com/getify Kyle Simpson]. The book is licensed under the [https://creativecommons.org/licenses/by-nc-nd/4.0/ CC BY-NC-ND 4.0 license]. © 2019-2022 Kyle Simpson.</div>

On the other hand, if you are distributing hard copies of the book series or excerpts from the book series, instead of using hyperlinks, you may wish to include the links so it’s easier for users to locate the original source of the book, the author, and the CC license:

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">This chapter is from “You Don't Know JS Yet (2nd Edition)” (https://github.com/getify/You-Dont-Know-JS) by Kyle Simpson (https://github.com/getify). The book is licensed under the CC BY-NC-ND 4.0 license (https://creativecommons.org/licenses/by-nc-nd/4.0/). © 2019-2022 Kyle Simpson.</div>

Note that the CC BY-NC-ND license includes the NoDerivatives requirement, which indicates that no adaptations are allowed. You cannot make any adaptations relying on the CC BY-NC-CD license the author chose for the book. If you would like to make a translation of the book, for example, you will need to ask the author for permission first.

The CC BY-NC-ND license also includes the NonCommercial requirement. To learn more, take a look at [https://en.wikipedia.org/wiki/Creative_Commons_NonCommercial_license our guide about the NonCommercial licenses].
<hr>

=== Attributing materials from multiple sources ===

:[[File:Saylor_marking_example.jpg]]

''Let’s go through TASL:''

:'''T'''itle? Specific works are named, e.g., "Box-and-whisker Plots"

:'''A'''uthor? Different authors noted for the different works

:'''S'''ource? Original materials are linked for each work

:'''L'''icense? The different licenses (Creative Commons Attribution for Collaborative Statistics and Creative Commons Attribution-Noncommercial-ShareAlike for the Khan Academy video) are spelled out and linked for each work

:Lastly, it is clear which attribution belongs to which work.

You can visit the [http://www.saylor.org/courses/ma121/ Saylor.org Introduction to Statistics course page] to see how they marked it up directly.
<hr>

=== Publishing a web page for attribution ===
As stated above, recommended attribution depends on the medium you're working with. For media such as offline materials, video, audio, and images, consider publishing a web page with attribution information. For example, on a webpage featuring your audio recording, provide a credit list of material you used that adheres to best practices above. Doing so allows not only your material, but the materials you attribute, to be found by search engines and other web discovery tools. If possible within the medium, make the Author, Source, and License links the user can follow.

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">'''Example:'''<br>This video features the song [http://ccmixter.org/media/files/victor/6374 "Desaprendere (Treatment)"] by [http://fourstones.net/ fourstones], available under a Creative Commons [http://creativecommons.org/licenses/by-nc/2.5/ Attribution-Noncommercial] license.</div>

<hr>

==Attributing public domain materials==
Although attribution is not a legal obligation under [https://creativecommons.org/share-your-work/public-domain/cc0/ CC0 dedication]’s or [https://creativecommons.org/share-your-work/public-domain/pdm/ CC Public Domain Mark]’s licensing terms, we recommend that you consider providing attribution to the source for public domain materials when it is reasonable to do so. Attribution of public domain works not only encourages institutions to digitize and share more public domain materials in their physical collections, but also empowers users to easily locate the original source.

The following public domain image is digitized and hosted by the Rijksmuseum (the national museum of the Netherlands). The Rijksmuseum has applied a CC0 dedication to the image.

:[[File:Attributing_the_milkmaid.png|300px]]

You may provide credit in the following format:

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">“[http://hdl.handle.net/10934/RM0001.COLLECT.6417 The Milkmaid]” by Vermeer. The Rijksmuseum collection. The image is dedicated to the public domain under [https://creativecommons.org/share-your-work/public-domain/cc0/ CC0]. </div>

In most cases, people credit the source regardless of the work’s copyright status. Especially in an academic setting, providing source information about other people’s works has long been considered crucial to academic integrity. Copyright cannot be the only checkbox when deciding whether a source will be attributed.

== Common pitfalls ==

Below are some practices that you may wish to avoid. These practices are not always contrary to the Creative Commons licensing terms, but they often make it more challenging for users to find the original source and/or author.

'''Attribute in alt text'''
:Alt text is intended to provide accessible information about visual materials for users with cognitive disabilities or visual impairment. Using this field for licensing information makes browsing difficult for those users.

'''Attribute in metadata fields only'''
:While it is great to include attribution in metadata fields (such as EXIF for images), in most cases this is not the only place to include attribution information. This is because many users are likely not aware of, and will never see, attribution information included in metadata.

'''Credit authors by names other than the ones they have selected'''
:Many people believe that attribution must be given to the real name of the author of a work, but this is not the case — always give attribution to the name the author has specified, even if it is a pseudonym. If the author does not give a name or explicitly requests to be anonymous, you must give the other attribution information (i.e., “T” and “SL” from “TASL”) without crediting the author.

'''Credit a site (or Creative Commons itself!) instead of the author'''
:Unless an author specifically requests users to only credit a site, crediting the site where you have found the material cannot substitute crediting the author. An author may have uploaded material to a site under a CC license, but in most cases, the copyright is still held by the author, and it is the copyright holder who needs to be credited. For example, many photos sourced from Wikimedia Commons are attributed to Wikimedia when they must be attributed to the authors.

== Other guides to attribution ==

* [http://creativecommons.org.au/materials/attribution.pdf Attributing Creative Commons Material] (pdf) - Creative Commons Australia's publication is full of examples with colorful imagery.
* [http://www.newmediarights.org/guide/how_to/creative_commons/best_practices_creative_commons_attributions How to attribute works you reuse under a Creative Commons license] by New Media Rights provides real world examples by different media type

[[Category:Marking]]
[[Category:Licensing]]
[[Category:Community]]
[[Category:Media]]
[[Category:HOWTO]]
[[Category:Guide]]
{{Best Practice}}

Recommended practices for attribution

2022-12-07T20:20:44Z

CCID-yuanxiaoxu: /* Attributing text */

You can use CC-licensed materials as long as you follow the license conditions. One condition of all CC licenses is attribution: crediting the author and giving the source information. Generally speaking, attribution must reasonably include all relevant information supplied by the licensor. Because each use case is different, you can decide what form of attribution is most suitable for your specific situation. The following examples are intended to illustrate what typical prudent practices look like. We expect community norms and expectations to evolve with time, and will adapt this guide accordingly.
In addition to attribution, there are also [https://wiki.creativecommons.org/wiki/Considerations_for_licensors_and_licensees#Considerations_for_licensees|other things to consider as a licensor or a licensee]. If you are a licensor and would like to learn how to license your own material, take a look at [https://wiki.creativecommons.org/wiki/Marking_your_work_with_a_CC_license our guide on how to mark your work with a CC license].

==Basic components of attribution==

[[File:19th_century_tassel_from_Smithsonian.jpeg|290px|left]]

Whenever you are reusing CC licensed works, we recommend that the attribution include the '''T'''itle, '''A'''uthor, '''S'''ource, and '''L'''icense. This is true whether you’re sharing the work as-is or if you have made an adaptation. To remember these attribution elements, it’s helpful to think of the acronym: '''TASL'''.

Let’s now go through '''TASL''' — we will explain each element in more detail:

'''Title''': What is the name of the work?

:If a title was provided for the work, include it as a part of the attribution. Sometimes a title is not provided; in that case, there’s no need to mention the title.

:The inclusion of title is a requirement of all CC licenses version 3.0 or earlier, and it is optional for the 4.0 suites. See Devil in the details.

'''Author''': Who allows you to use the work?

:We often use “author” as a shorthand when we are, legally speaking, referring to the “licensor” (a.k.a., the “copyright holder” or “rightsholder”). This is because, in most CC-licensed works, the licensor is the same person or entity as the author. When an author is licensing their work under a CC license, and has made their name available, include the author’s name as a component in your attribution. Sometimes, the licensor may want you to give credit to some other entity, like a company or institution, or the licensor may want to be credited by a pseudonym instead of their real name. In rare cases, the licensor may not want to be attributed at all. In all of these cases, do what the licensor requests.

:Sometimes, the author will also provide a copyright notice, which consists of the copyright symbol, year of publication, and the name of the author/licensor. Include the copyright notice as a part of your attribution if such information is provided.

'''Source''': Where can people find the work?

:Please make it possible for future users to find the source of the material by including a URL or hyperlink where the work resides. This often is where you found the work. If you found it somewhere other than the original site, try to include information about the original site where the work was first shared publicly. It is also better to use the original URL instead of a shortened link, whether you are hyperlinking or printing out the entire URL.

'''License''': How can you use the work?

:You must specify which CC license was applied to the work you are reusing. Each of the six different CC licenses come with distinct requirements for re-use. We recommend that you name and provide a link to the license, e.g., [http://creativecommons.org/licenses/by/4.0 CC BY 4.0] (http://creativecommons.org/licenses/by/4.0) for a work licensed under CC BY 4.0.

:Consider also including the “disclaimer of warranties,” which clarifies that the author makes no representations or warranties about the non-infringement or absence of other defects concerning the CC-licensed work. In plain English, this means that the users will use the work at their own risk.

:To sum up, if the licensor has provided any information related to TASL, consider including them in your attribution. We also recommend providing links to the Title, Author, Source, and License, where possible, so future users can easily access the information they need on a work and the license terms.
<hr>
===Reasonable attribution===

The CC licenses ask you to be reasonable:

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 90%;">You may satisfy the attribution requirement in any reasonable manner based on the medium, means and context in which the Licensed Material is used. For example, it may be reasonable to satisfy some or all of the conditions by retaining a copyright notice, or by providing a URI or hyperlink associated with the Licensed Material, if the copyright notice or webpage includes some or all of the required information.</div>

There is no single best or correct way of attribution, as long as your attribution is reasonable and suited to the medium you're working with. That being said, please include attribution somehow, even if it's a link to an About page that has the relevant info. (More on different media below.)
<hr>

===Devil in the details===

If you have any doubts or questions, you can read the complete attribution requirements which are spelled out in detail in the legal code of every CC license, eg. http://creativecommons.org/licenses/by/4.0/legalcode This [[License_Versions#Detailed_attribution_comparison_chart|chart compares the detailed requirements across all versions of CC licenses.]]

==Examples of attribution==

We will now look at some examples in different media.

===Attributing an image===

Here is a photo. Below, we will go over some good and bad examples of how people might attribute it.

[[File:8256206923_c77e85319e_n.jpg]]
<hr>

====This is a great attribution====
<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">
"[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Creative Commons 10th Birthday Celebration San Francisco]" by [http://www.flickr.com/photos/sixteenmilesofstring/ Timothy Vollmer] is licensed under [http://creativecommons.org/licenses/by/4.0/ CC BY 4.0]</div>

''Let’s go through TASL:''
:'''T'''itle? "Creative Commons 10th Birthday Celebration San Francisco"
:'''A'''uthor? "[http://www.flickr.com/photos/sixteenmilesofstring/ Timothy Vollmer]" - linked to his profile page
:'''S'''ource? "[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Creative Commons 10th Birthday Celebration San Francisco]" - linked to original Flickr page
:'''L'''icense? "[http://creativecommons.org/licenses/by/4.0/ CC BY 4.0]" - linked to license deed

Most importantly, this attribution reasonably includes all the relevant information provided by the author.
<hr>

====This is a pretty good attribution====

<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Photo] by Timothy Vollmer/ [http://creativecommons.org/licenses/by/2.0/ CC BY]</div>

''Let’s go through TASL:''
:'''T'''itle? Title is not noted but at least the source is linked.
:'''A'''uthor? "Timothy Vollmer"
:'''S'''ource? "[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Photo]" - linked to original Flickr page
:'''L'''icense? "[http://creativecommons.org/licenses/by/4.0/ CC BY]" - linked to license deed

As you see, a good attribution includes all the essential '''TASL''' elements, even though they may not mirror the format of credit the author has requested.
<hr>

==== This is an incorrect attribution====
<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">Photo: Creative Commons</div>

''Let’s go through TASL'':
:'''T'''itle? Title of the image is not noted
:'''A'''uthor? Author is not noted (It is a common mistake to attribute CC-licensed photos to CC, but Creative Commons is not the author!)
:'''S'''ource? No link to the original source
:'''L'''icense? There is no mention of a license nor a link to the license. "Creative Commons" is the name of an organization; it does not equate to any of the licenses maintained by the Creative Commons.
<hr>

====This is a great attribution for an image you modified slightly====
:[[File:Cropped_tvol_cupcake.png|300px]]

<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">"[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Creative Commons 10th Birthday Celebration San Francisco]" by [http://www.flickr.com/photos/sixteenmilesofstring/ Timothy Vollmer], used under [http://creativecommons.org/licenses/by/4.0/ CC BY 4.0] / Cropped from original</div>

Here, information on '''T'''itle, '''A'''uthor, '''S'''ource, and '''L'''icense are all included as requested by the author. The slight modification is also noted and briefly described.

Note if the modification changes the work’s meaning in a way that would be considered creative — that is, not a purely mechanical change or a simple crop/excerpt that keeps the original message undistorted, it would be considered creating a new adaptation of the original work. You cannot rely on a CC license that does not allow adaptation (e.g., CC BY-ND or CC BY-NC-ND) when making such modifications.

<hr>

====This is a great attribution for when you have created an adaptation====

:[[File:8256206923_c77e85319e_n_90fied.jpg|300px]]

<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">This work, "90fied", is adapted from "[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Creative Commons 10th Birthday Celebration San Francisco]" by [http://www.flickr.com/photos/sixteenmilesofstring/ Timothy Vollmer], used under [http://creativecommons.org/licenses/by/4.0/ CC BY 4.0]. "90fied" is licensed under [http://creativecommons.org/licenses/by/4.0/ CC BY 4.0] by [Your name here].</div>

''Let’s go through TASL:''

Original '''T'''itle, '''A'''uthor, '''S'''ource, and '''L'''icense are all noted.

The original work is referenced and the fact that it is an adaptation is also noted, so viewers can see what has changed.

The author and other attribution information for the new adapted work is also noted.

Note: If you're at a point where you are licensing works that are adaptations, go to [[Marking your work with a CC license]].
<hr>

===Attributing music===

====When you incorporate music in an audio or video recording====
Music (both the underlying composition and the sound recordings) — such as a song, or a recording of natural sounds — can be attributed within the audio/video, and in the description text of the audio/video. How to attribute a CC licensed music in an audio or video recording will largely depend on what is reasonable for a chosen medium and platform.

Caution: Licenses with “ND” do not allow for adaptations. Your use of CC-licensed music is often an adaptation!

It is considered adaptation if you incorporate CC-licensed music into your work in a way that the CC-licensed music can no longer be seen as a stand-alone piece. For example, if you are using a song as background music in a podcast or in a video, it is considered an adaptation of the song.

Keep in mind that CC BY-ND and CC BY-NC-ND do not allow adaptations (although you may be authorized by law to do so, such as under a users’ right like fair use, or you may ask for the author’s permission independent of the CC license).
<hr>

[[File:Smithsonian_music_stand.jpeg|left|250px]]

=====This is a great attribution of background music in a podcast or a video=====
When reasonable to do so, we recommend that you include attribution both in the description box and in the podcast recording or the video recording itself.

If you are using the following song in a podcast: ‘Day Bird’ by Broke for Free ([https://brokeforfree.com brokeforfree.com]), this would be a great way to provide attribution (which you can see in [https://soundcloud.com/wearecc/open-minds-podcast-catherine-stihler-ceo-of-creative-commons the Creative Commons podcast]) —

:At the end of the podcast audio recording, the host says:
:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 90%;">Special thanks to the musician Broke for Free, whose track “Day Bird” you heard at the beginning of this episode and you are listening to right now. It's under the Creative Commons Attribution License, meaning it's free for anyone to use. You can find it at the Free Music Archive—freemusicarchive.org</div>

:In the description box, the information text reads:
:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 90%;">Theme music: “Day Bird” by Broke for Free ([https://brokeforfree.com brokeforfree.com]). Available for use under the CC BY 3.0 license ([https://creativecommons.org/licenses/by/3.0/ creativecommons.org/licenses/by/3.0/]), at [https://freemusicarchive.org/music/Broke_For_Free/Directionless_EP/Broke_For_Free_-_Directionless_EP_-_03_Day_Bird|the Free Music Archive].</div>

''Let’s go through TASL:''

:'''T'''itle? Both the recording and the description box include the title of the work, “Day Bird”

:'''A'''uthor? "Broke for Free," again, noted both in the recording and in the description box

:'''S'''ource? Both the author’s page and the archive’s page are included with links

:'''L'''icense? "CC BY 3.0" — linked to license deed

You cannot talk over, or remix, music licensed under CC BY-ND or CC BY-NC-ND.

<hr>

=====This is a bad attribution of background music in a podcast or a video=====

A bad attribution is one where you do not provide enough information for a user to find the music you are using. The following is a bad attribution for the same song:

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">No attribution is included in the podcast recording or the video itself.

In the description box, it says: “ Creative Commons music.”</div>

''Let’s go through TASL:''

:'''T'''itle? Title is not noted

:'''A'''uthor? Author is not noted

:'''S'''ource? Source is not noted; users cannot find the specific song used in the podcast

:'''L'''icense? No information on the CC license

The attribution information is not sufficient for people to find the song you have re-used.
<hr>

====When you are not adding new elements to the music====
When you re-use music without adding new elements to it, you are not making an adaptation. In that case, you can rely on any of the CC licenses, including CC BY-ND and CC BY-NC-ND. We recommend providing attribution information in writing.

[[File:Wiki_page_attributing_night_owl.png|400px]]

On [https://commons.wikimedia.org/wiki/File:Broke_For_Free_-_01_-_Night_Owl.ogg this Wikipedia page], you can see an example of great attribution for the sharing another soundtrack, “Night Owl” by Broke for Free, when it’s without adaptation.

''Let’s go through TASL:''

'''T'''itle? Title of the work, “Night Owl,” is noted

'''A'''uthor? "Broke for Free," noted and linked to the author’s webpage

'''S'''ource? A link is provided for the source

'''L'''icense? "CC BY 3.0" — linked to license deed
<hr>

===Attributing text===
Let’s take [https://github.com/getify/You-Dont-Know-JS ''You Don't Know JS Yet'' (2nd Edition)] as an example, and go over what your attribution may look like if you reuse the book series. The information under the “License & Copyright” section looks like this on the webpage where the book series was originally shared:
:[[File:attributing_You_Don't_Know_JS_Yet_(2nd_Edition).png|200px]]

We recommend that you retain all the information provided by the author of the book series when it is reasonable for you to do so. For example, if you are distributing digital copies or excerpts of the book series in a free seminar, or using parts of the book in a free online course or presentation, the attribution will likely look something like this:

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">This chapter is from “[https://github.com/getify/You-Dont-Know-JS You Don't Know JS Yet (2nd Edition)]” by [https://github.com/getify Kyle Simpson]. The book is licensed under the [https://creativecommons.org/licenses/by-nc-nd/4.0/ CC BY-NC-ND 4.0 license]. © 2019-2022 Kyle Simpson.</div>

On the other hand, if you are distributing hard copies of the book series or excerpts from the book series, instead of using hyperlinks, you may wish to include the links so it’s easier for users to locate the original source of the book, the author, and the CC license:

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">This chapter is from “You Don't Know JS Yet (2nd Edition)” (https://github.com/getify/You-Dont-Know-JS) by Kyle Simpson (https://github.com/getify). The book is licensed under the CC BY-NC-ND 4.0 license (https://creativecommons.org/licenses/by-nc-nd/4.0/). © 2019-2022 Kyle Simpson.</div>

Note that the CC BY-NC-ND license includes the NoDerivatives requirement, which indicates that no adaptations are allowed. You cannot make any adaptations relying on the CC BY-NC-CD license the author chose for the book. If you would like to make a translation of the book, for example, you will need to ask the author for permission first.

The CC BY-NC-ND license also includes the NonCommercial requirement. To learn more, take a look at [https://en.wikipedia.org/wiki/Creative_Commons_NonCommercial_license our guide about the NonCommercial licenses].
<hr>

=== Attributing materials from multiple sources ===

:[[File:Saylor_marking_example.jpg]]

''Let’s go through TASL:''

:'''T'''itle? Specific works are named, e.g., "Box-and-whisker Plots"

:'''A'''uthor? Different authors noted for the different works

:'''S'''ource? Original materials are linked for each work

:'''L'''icense? The different licenses (Creative Commons Attribution for Collaborative Statistics and Creative Commons Attribution-Noncommercial-ShareAlike for the Khan Academy video) are spelled out and linked for each work

:Lastly, it is clear which attribution belongs to which work.

You can visit the [http://www.saylor.org/courses/ma121/ Saylor.org Introduction to Statistics course page] to see how they marked it up directly.
<hr>

=== Publishing a web page for attribution ===
As stated above, recommended attribution depends on the medium you're working with. For media such as offline materials, video, audio, and images, consider publishing a web page with attribution information. For example, on a webpage featuring your audio recording, provide a credit list of material you used that adheres to best practices above. Doing so allows not only your material, but the materials you attribute, to be found by search engines and other web discovery tools. If possible within the medium, make the Author, Source, and License links the user can follow.

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">'''Example:'''<br>This video features the song [http://ccmixter.org/media/files/victor/6374 "Desaprendere (Treatment)"] by [http://fourstones.net/ fourstones], available under a Creative Commons [http://creativecommons.org/licenses/by-nc/2.5/ Attribution-Noncommercial] license.</div>

<hr>

==Attributing public domain materials==
Although attribution is not a legal obligation under [https://creativecommons.org/share-your-work/public-domain/cc0/ CC0 dedication]’s or [https://creativecommons.org/share-your-work/public-domain/pdm/ CC Public Domain Mark]’s licensing terms, we recommend that you consider providing attribution to the source for public domain materials when it is reasonable to do so. Attribution of public domain works not only encourages institutions to digitize and share more public domain materials in their physical collections, but also empowers users to easily locate the original source.

The following public domain image is digitized and hosted by the Rijksmuseum (the national museum of the Netherlands). The Rijksmuseum has applied a CC0 dedication to the image.

:[[File:Attributing_the_milkmaid.png|300px]]

You may provide credit in the following format:

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">“[http://hdl.handle.net/10934/RM0001.COLLECT.6417 The Milkmaid]” by Vermeer. The Rijksmuseum collection. The image is dedicated to the public domain under [https://creativecommons.org/share-your-work/public-domain/cc0/ CC0]. </div>

In most cases, people credit the source regardless of the work’s copyright status. Especially in an academic setting, providing source information about other people’s works has long been considered crucial to academic integrity. Copyright cannot be the only checkbox when deciding whether a source will be attributed.

== Common pitfalls ==

Below are some practices that you may wish to avoid. These practices are not always contrary to the Creative Commons licensing terms, but they often make it more challenging for users to find the original source and/or author.

'''Attribute in alt text'''
:Alt text is intended to provide accessible information about visual materials for users with cognitive disabilities or visual impairment. Using this field for licensing information makes browsing difficult for those users.

'''Attribute in metadata fields only'''
:While it is great to include attribution in metadata fields (such as EXIF for images), in most cases this is not the only place to include attribution information. This is because many users are likely not aware of, and will never see, attribution information included in metadata.

'''Credit authors by names other than the ones they have selected'''
:Many people believe that attribution must be given to the real name of the author of a work, but this is not the case — always give attribution to the name the author has specified, even if it is a pseudonym. If the author does not give a name or explicitly requests to be anonymous, you must give the other attribution information (i.e., “T” and “SL” from “TASL”) without crediting the author.

'''Credit a site (or Creative Commons itself!) instead of the author'''
:Unless an author specifically requests users to only credit a site, crediting the site where you have found the material cannot substitute crediting the author. An author may have uploaded material to a site under a CC license, but in most cases, the copyright is still held by the author, and it is the copyright holder who needs to be credited. For example, many photos sourced from Wikimedia Commons are attributed to Wikimedia when they must be attributed to the authors.

== Other guides to attribution ==

* [http://creativecommons.org.au/materials/attribution.pdf Attributing Creative Commons Material] (pdf) - Creative Commons Australia's publication is full of examples with colorful imagery.
* [http://www.newmediarights.org/guide/how_to/creative_commons/best_practices_creative_commons_attributions How to attribute works you reuse under a Creative Commons license] by New Media Rights provides real world examples by different media type

[[Category:Marking]]
[[Category:Licensing]]
[[Category:Community]]
[[Category:Media]]
[[Category:HOWTO]]
[[Category:Guide]]
{{Best Practice}}

Recommended practices for attribution

2022-12-07T20:19:38Z

CCID-yuanxiaoxu:

You can use CC-licensed materials as long as you follow the license conditions. One condition of all CC licenses is attribution: crediting the author and giving the source information. Generally speaking, attribution must reasonably include all relevant information supplied by the licensor. Because each use case is different, you can decide what form of attribution is most suitable for your specific situation. The following examples are intended to illustrate what typical prudent practices look like. We expect community norms and expectations to evolve with time, and will adapt this guide accordingly.
In addition to attribution, there are also [https://wiki.creativecommons.org/wiki/Considerations_for_licensors_and_licensees#Considerations_for_licensees|other things to consider as a licensor or a licensee]. If you are a licensor and would like to learn how to license your own material, take a look at [https://wiki.creativecommons.org/wiki/Marking_your_work_with_a_CC_license our guide on how to mark your work with a CC license].

==Basic components of attribution==

[[File:19th_century_tassel_from_Smithsonian.jpeg|290px|left]]

Whenever you are reusing CC licensed works, we recommend that the attribution include the '''T'''itle, '''A'''uthor, '''S'''ource, and '''L'''icense. This is true whether you’re sharing the work as-is or if you have made an adaptation. To remember these attribution elements, it’s helpful to think of the acronym: '''TASL'''.

Let’s now go through '''TASL''' — we will explain each element in more detail:

'''Title''': What is the name of the work?

:If a title was provided for the work, include it as a part of the attribution. Sometimes a title is not provided; in that case, there’s no need to mention the title.

:The inclusion of title is a requirement of all CC licenses version 3.0 or earlier, and it is optional for the 4.0 suites. See Devil in the details.

'''Author''': Who allows you to use the work?

:We often use “author” as a shorthand when we are, legally speaking, referring to the “licensor” (a.k.a., the “copyright holder” or “rightsholder”). This is because, in most CC-licensed works, the licensor is the same person or entity as the author. When an author is licensing their work under a CC license, and has made their name available, include the author’s name as a component in your attribution. Sometimes, the licensor may want you to give credit to some other entity, like a company or institution, or the licensor may want to be credited by a pseudonym instead of their real name. In rare cases, the licensor may not want to be attributed at all. In all of these cases, do what the licensor requests.

:Sometimes, the author will also provide a copyright notice, which consists of the copyright symbol, year of publication, and the name of the author/licensor. Include the copyright notice as a part of your attribution if such information is provided.

'''Source''': Where can people find the work?

:Please make it possible for future users to find the source of the material by including a URL or hyperlink where the work resides. This often is where you found the work. If you found it somewhere other than the original site, try to include information about the original site where the work was first shared publicly. It is also better to use the original URL instead of a shortened link, whether you are hyperlinking or printing out the entire URL.

'''License''': How can you use the work?

:You must specify which CC license was applied to the work you are reusing. Each of the six different CC licenses come with distinct requirements for re-use. We recommend that you name and provide a link to the license, e.g., [http://creativecommons.org/licenses/by/4.0 CC BY 4.0] (http://creativecommons.org/licenses/by/4.0) for a work licensed under CC BY 4.0.

:Consider also including the “disclaimer of warranties,” which clarifies that the author makes no representations or warranties about the non-infringement or absence of other defects concerning the CC-licensed work. In plain English, this means that the users will use the work at their own risk.

:To sum up, if the licensor has provided any information related to TASL, consider including them in your attribution. We also recommend providing links to the Title, Author, Source, and License, where possible, so future users can easily access the information they need on a work and the license terms.
<hr>
===Reasonable attribution===

The CC licenses ask you to be reasonable:

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 90%;">You may satisfy the attribution requirement in any reasonable manner based on the medium, means and context in which the Licensed Material is used. For example, it may be reasonable to satisfy some or all of the conditions by retaining a copyright notice, or by providing a URI or hyperlink associated with the Licensed Material, if the copyright notice or webpage includes some or all of the required information.</div>

There is no single best or correct way of attribution, as long as your attribution is reasonable and suited to the medium you're working with. That being said, please include attribution somehow, even if it's a link to an About page that has the relevant info. (More on different media below.)
<hr>

===Devil in the details===

If you have any doubts or questions, you can read the complete attribution requirements which are spelled out in detail in the legal code of every CC license, eg. http://creativecommons.org/licenses/by/4.0/legalcode This [[License_Versions#Detailed_attribution_comparison_chart|chart compares the detailed requirements across all versions of CC licenses.]]

==Examples of attribution==

We will now look at some examples in different media.

===Attributing an image===

Here is a photo. Below, we will go over some good and bad examples of how people might attribute it.

[[File:8256206923_c77e85319e_n.jpg]]
<hr>

====This is a great attribution====
<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">
"[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Creative Commons 10th Birthday Celebration San Francisco]" by [http://www.flickr.com/photos/sixteenmilesofstring/ Timothy Vollmer] is licensed under [http://creativecommons.org/licenses/by/4.0/ CC BY 4.0]</div>

''Let’s go through TASL:''
:'''T'''itle? "Creative Commons 10th Birthday Celebration San Francisco"
:'''A'''uthor? "[http://www.flickr.com/photos/sixteenmilesofstring/ Timothy Vollmer]" - linked to his profile page
:'''S'''ource? "[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Creative Commons 10th Birthday Celebration San Francisco]" - linked to original Flickr page
:'''L'''icense? "[http://creativecommons.org/licenses/by/4.0/ CC BY 4.0]" - linked to license deed

Most importantly, this attribution reasonably includes all the relevant information provided by the author.
<hr>

====This is a pretty good attribution====

<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Photo] by Timothy Vollmer/ [http://creativecommons.org/licenses/by/2.0/ CC BY]</div>

''Let’s go through TASL:''
:'''T'''itle? Title is not noted but at least the source is linked.
:'''A'''uthor? "Timothy Vollmer"
:'''S'''ource? "[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Photo]" - linked to original Flickr page
:'''L'''icense? "[http://creativecommons.org/licenses/by/4.0/ CC BY]" - linked to license deed

As you see, a good attribution includes all the essential '''TASL''' elements, even though they may not mirror the format of credit the author has requested.
<hr>

==== This is an incorrect attribution====
<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">Photo: Creative Commons</div>

''Let’s go through TASL'':
:'''T'''itle? Title of the image is not noted
:'''A'''uthor? Author is not noted (It is a common mistake to attribute CC-licensed photos to CC, but Creative Commons is not the author!)
:'''S'''ource? No link to the original source
:'''L'''icense? There is no mention of a license nor a link to the license. "Creative Commons" is the name of an organization; it does not equate to any of the licenses maintained by the Creative Commons.
<hr>

====This is a great attribution for an image you modified slightly====
:[[File:Cropped_tvol_cupcake.png|300px]]

<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">"[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Creative Commons 10th Birthday Celebration San Francisco]" by [http://www.flickr.com/photos/sixteenmilesofstring/ Timothy Vollmer], used under [http://creativecommons.org/licenses/by/4.0/ CC BY 4.0] / Cropped from original</div>

Here, information on '''T'''itle, '''A'''uthor, '''S'''ource, and '''L'''icense are all included as requested by the author. The slight modification is also noted and briefly described.

Note if the modification changes the work’s meaning in a way that would be considered creative — that is, not a purely mechanical change or a simple crop/excerpt that keeps the original message undistorted, it would be considered creating a new adaptation of the original work. You cannot rely on a CC license that does not allow adaptation (e.g., CC BY-ND or CC BY-NC-ND) when making such modifications.

<hr>

====This is a great attribution for when you have created an adaptation====

:[[File:8256206923_c77e85319e_n_90fied.jpg|300px]]

<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">This work, "90fied", is adapted from "[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Creative Commons 10th Birthday Celebration San Francisco]" by [http://www.flickr.com/photos/sixteenmilesofstring/ Timothy Vollmer], used under [http://creativecommons.org/licenses/by/4.0/ CC BY 4.0]. "90fied" is licensed under [http://creativecommons.org/licenses/by/4.0/ CC BY 4.0] by [Your name here].</div>

''Let’s go through TASL:''

Original '''T'''itle, '''A'''uthor, '''S'''ource, and '''L'''icense are all noted.

The original work is referenced and the fact that it is an adaptation is also noted, so viewers can see what has changed.

The author and other attribution information for the new adapted work is also noted.

Note: If you're at a point where you are licensing works that are adaptations, go to [[Marking your work with a CC license]].
<hr>

===Attributing music===

====When you incorporate music in an audio or video recording====
Music (both the underlying composition and the sound recordings) — such as a song, or a recording of natural sounds — can be attributed within the audio/video, and in the description text of the audio/video. How to attribute a CC licensed music in an audio or video recording will largely depend on what is reasonable for a chosen medium and platform.

Caution: Licenses with “ND” do not allow for adaptations. Your use of CC-licensed music is often an adaptation!

It is considered adaptation if you incorporate CC-licensed music into your work in a way that the CC-licensed music can no longer be seen as a stand-alone piece. For example, if you are using a song as background music in a podcast or in a video, it is considered an adaptation of the song.

Keep in mind that CC BY-ND and CC BY-NC-ND do not allow adaptations (although you may be authorized by law to do so, such as under a users’ right like fair use, or you may ask for the author’s permission independent of the CC license).
<hr>

[[File:Smithsonian_music_stand.jpeg|left|250px]]

=====This is a great attribution of background music in a podcast or a video=====
When reasonable to do so, we recommend that you include attribution both in the description box and in the podcast recording or the video recording itself.

If you are using the following song in a podcast: ‘Day Bird’ by Broke for Free ([https://brokeforfree.com brokeforfree.com]), this would be a great way to provide attribution (which you can see in [https://soundcloud.com/wearecc/open-minds-podcast-catherine-stihler-ceo-of-creative-commons the Creative Commons podcast]) —

:At the end of the podcast audio recording, the host says:
:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 90%;">Special thanks to the musician Broke for Free, whose track “Day Bird” you heard at the beginning of this episode and you are listening to right now. It's under the Creative Commons Attribution License, meaning it's free for anyone to use. You can find it at the Free Music Archive—freemusicarchive.org</div>

:In the description box, the information text reads:
:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 90%;">Theme music: “Day Bird” by Broke for Free ([https://brokeforfree.com brokeforfree.com]). Available for use under the CC BY 3.0 license ([https://creativecommons.org/licenses/by/3.0/ creativecommons.org/licenses/by/3.0/]), at [https://freemusicarchive.org/music/Broke_For_Free/Directionless_EP/Broke_For_Free_-_Directionless_EP_-_03_Day_Bird|the Free Music Archive].</div>

''Let’s go through TASL:''

:'''T'''itle? Both the recording and the description box include the title of the work, “Day Bird”

:'''A'''uthor? "Broke for Free," again, noted both in the recording and in the description box

:'''S'''ource? Both the author’s page and the archive’s page are included with links

:'''L'''icense? "CC BY 3.0" — linked to license deed

You cannot talk over, or remix, music licensed under CC BY-ND or CC BY-NC-ND.

<hr>

=====This is a bad attribution of background music in a podcast or a video=====

A bad attribution is one where you do not provide enough information for a user to find the music you are using. The following is a bad attribution for the same song:

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">No attribution is included in the podcast recording or the video itself.

In the description box, it says: “ Creative Commons music.”</div>

''Let’s go through TASL:''

:'''T'''itle? Title is not noted

:'''A'''uthor? Author is not noted

:'''S'''ource? Source is not noted; users cannot find the specific song used in the podcast

:'''L'''icense? No information on the CC license

The attribution information is not sufficient for people to find the song you have re-used.
<hr>

====When you are not adding new elements to the music====
When you re-use music without adding new elements to it, you are not making an adaptation. In that case, you can rely on any of the CC licenses, including CC BY-ND and CC BY-NC-ND. We recommend providing attribution information in writing.

[[File:Wiki_page_attributing_night_owl.png|400px]]

On [https://commons.wikimedia.org/wiki/File:Broke_For_Free_-_01_-_Night_Owl.ogg this Wikipedia page], you can see an example of great attribution for the sharing another soundtrack, “Night Owl” by Broke for Free, when it’s without adaptation.

''Let’s go through TASL:''

'''T'''itle? Title of the work, “Night Owl,” is noted

'''A'''uthor? "Broke for Free," noted and linked to the author’s webpage

'''S'''ource? A link is provided for the source

'''L'''icense? "CC BY 3.0" — linked to license deed
<hr>

===Attributing text===
Let’s take [https://github.com/getify/You-Dont-Know-JS ''You Don't Know JS Yet'' (2nd Edition)] as an example, and go over what your attribution may look like if you reuse the book series. The information under the “License & Copyright” section looks like this on the webpage where the book series was originally shared:
:[[File:attributing_You_Don't_Know_JS_Yet_(2nd_Edition).png|200px]]

We recommend that you retain all the information provided by the author of the book series when it is reasonable for you to do so. For example, if you are distributing digital copies or excerpts of the book series in a free seminar, or using parts of the book in a free online course or presentation, the attribution will likely look something like this:

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">This chapter is from “[https://github.com/getify/You-Dont-Know-JS You Don't Know JS Yet (2nd Edition)]” by [https://github.com/getify Kyle Simpson]. The book is licensed under the [https://creativecommons.org/licenses/by-nc-nd/4.0/ CC BY-NC-ND 4.0 license]. © 2019-2022 Kyle Simpson.</div>

On the other hand, if you are distributing hard copies of the book series or excerpts from the book series, instead of using hyperlinks, you may wish to include the links so it’s easier for users to locate the original source of the book, the author, and the CC license:

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">This chapter is from “You Don't Know JS Yet (2nd Edition)” (https://github.com/getify/You-Dont-Know-JS) by Kyle Simpson (https://github.com/getify). The book is licensed under the CC BY-NC-ND 4.0 license (https://creativecommons.org/licenses/by-nc-nd/4.0/). © 2019-2022 Kyle Simpson.</div>

Note that the CC BY-NC-ND license includes the NoDerivatives requirement, which indicates that no adaptations are allowed. You cannot make any adaptations relying on the CC BY-NC-CD license the author chose for the book. If you would like to make a translation of the book, for example, you will need to ask the author for permission first.

The CC BY-NC-ND license also includes the NonCommercial requirement. To learn more, take a look at [https://en.wikipedia.org/wiki/Creative_Commons_NonCommercial_license this page here].
<hr>

=== Attributing materials from multiple sources ===

:[[File:Saylor_marking_example.jpg]]

''Let’s go through TASL:''

:'''T'''itle? Specific works are named, e.g., "Box-and-whisker Plots"

:'''A'''uthor? Different authors noted for the different works

:'''S'''ource? Original materials are linked for each work

:'''L'''icense? The different licenses (Creative Commons Attribution for Collaborative Statistics and Creative Commons Attribution-Noncommercial-ShareAlike for the Khan Academy video) are spelled out and linked for each work

:Lastly, it is clear which attribution belongs to which work.

You can visit the [http://www.saylor.org/courses/ma121/ Saylor.org Introduction to Statistics course page] to see how they marked it up directly.
<hr>

=== Publishing a web page for attribution ===
As stated above, recommended attribution depends on the medium you're working with. For media such as offline materials, video, audio, and images, consider publishing a web page with attribution information. For example, on a webpage featuring your audio recording, provide a credit list of material you used that adheres to best practices above. Doing so allows not only your material, but the materials you attribute, to be found by search engines and other web discovery tools. If possible within the medium, make the Author, Source, and License links the user can follow.

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">'''Example:'''<br>This video features the song [http://ccmixter.org/media/files/victor/6374 "Desaprendere (Treatment)"] by [http://fourstones.net/ fourstones], available under a Creative Commons [http://creativecommons.org/licenses/by-nc/2.5/ Attribution-Noncommercial] license.</div>

<hr>

==Attributing public domain materials==
Although attribution is not a legal obligation under [https://creativecommons.org/share-your-work/public-domain/cc0/ CC0 dedication]’s or [https://creativecommons.org/share-your-work/public-domain/pdm/ CC Public Domain Mark]’s licensing terms, we recommend that you consider providing attribution to the source for public domain materials when it is reasonable to do so. Attribution of public domain works not only encourages institutions to digitize and share more public domain materials in their physical collections, but also empowers users to easily locate the original source.

The following public domain image is digitized and hosted by the Rijksmuseum (the national museum of the Netherlands). The Rijksmuseum has applied a CC0 dedication to the image.

:[[File:Attributing_the_milkmaid.png|300px]]

You may provide credit in the following format:

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">“[http://hdl.handle.net/10934/RM0001.COLLECT.6417 The Milkmaid]” by Vermeer. The Rijksmuseum collection. The image is dedicated to the public domain under [https://creativecommons.org/share-your-work/public-domain/cc0/ CC0]. </div>

In most cases, people credit the source regardless of the work’s copyright status. Especially in an academic setting, providing source information about other people’s works has long been considered crucial to academic integrity. Copyright cannot be the only checkbox when deciding whether a source will be attributed.

== Common pitfalls ==

Below are some practices that you may wish to avoid. These practices are not always contrary to the Creative Commons licensing terms, but they often make it more challenging for users to find the original source and/or author.

'''Attribute in alt text'''
:Alt text is intended to provide accessible information about visual materials for users with cognitive disabilities or visual impairment. Using this field for licensing information makes browsing difficult for those users.

'''Attribute in metadata fields only'''
:While it is great to include attribution in metadata fields (such as EXIF for images), in most cases this is not the only place to include attribution information. This is because many users are likely not aware of, and will never see, attribution information included in metadata.

'''Credit authors by names other than the ones they have selected'''
:Many people believe that attribution must be given to the real name of the author of a work, but this is not the case — always give attribution to the name the author has specified, even if it is a pseudonym. If the author does not give a name or explicitly requests to be anonymous, you must give the other attribution information (i.e., “T” and “SL” from “TASL”) without crediting the author.

'''Credit a site (or Creative Commons itself!) instead of the author'''
:Unless an author specifically requests users to only credit a site, crediting the site where you have found the material cannot substitute crediting the author. An author may have uploaded material to a site under a CC license, but in most cases, the copyright is still held by the author, and it is the copyright holder who needs to be credited. For example, many photos sourced from Wikimedia Commons are attributed to Wikimedia when they must be attributed to the authors.

== Other guides to attribution ==

* [http://creativecommons.org.au/materials/attribution.pdf Attributing Creative Commons Material] (pdf) - Creative Commons Australia's publication is full of examples with colorful imagery.
* [http://www.newmediarights.org/guide/how_to/creative_commons/best_practices_creative_commons_attributions How to attribute works you reuse under a Creative Commons license] by New Media Rights provides real world examples by different media type

[[Category:Marking]]
[[Category:Licensing]]
[[Category:Community]]
[[Category:Media]]
[[Category:HOWTO]]
[[Category:Guide]]
{{Best Practice}}

Recommended practices for attribution

2022-12-07T20:19:15Z

CCID-yuanxiaoxu:

You can use CC-licensed materials as long as you follow the license conditions. One condition of all CC licenses is attribution: crediting the author and giving the source information. Generally speaking, attribution must reasonably include all relevant information supplied by the licensor. Because each use case is different, you can decide what form of attribution is most suitable for your specific situation. The following examples are intended to illustrate what typical prudent practices look like. We expect community norms and expectations to evolve with time, and will adapt this guide accordingly.
In addition to attribution, there are also [https://wiki.creativecommons.org/wiki/Considerations_for_licensors_and_licensees#Considerations_for_licensees|other things to consider as a licensor or a licensee]. If you are a licensor and would like to learn how to license your own material, [https://wiki.creativecommons.org/wiki/Marking_your_work_with_a_CC_license take a look at our guide on how to mark your work with a CC license].

==Basic components of attribution==

[[File:19th_century_tassel_from_Smithsonian.jpeg|290px|left]]

Whenever you are reusing CC licensed works, we recommend that the attribution include the '''T'''itle, '''A'''uthor, '''S'''ource, and '''L'''icense. This is true whether you’re sharing the work as-is or if you have made an adaptation. To remember these attribution elements, it’s helpful to think of the acronym: '''TASL'''.

Let’s now go through '''TASL''' — we will explain each element in more detail:

'''Title''': What is the name of the work?

:If a title was provided for the work, include it as a part of the attribution. Sometimes a title is not provided; in that case, there’s no need to mention the title.

:The inclusion of title is a requirement of all CC licenses version 3.0 or earlier, and it is optional for the 4.0 suites. See Devil in the details.

'''Author''': Who allows you to use the work?

:We often use “author” as a shorthand when we are, legally speaking, referring to the “licensor” (a.k.a., the “copyright holder” or “rightsholder”). This is because, in most CC-licensed works, the licensor is the same person or entity as the author. When an author is licensing their work under a CC license, and has made their name available, include the author’s name as a component in your attribution. Sometimes, the licensor may want you to give credit to some other entity, like a company or institution, or the licensor may want to be credited by a pseudonym instead of their real name. In rare cases, the licensor may not want to be attributed at all. In all of these cases, do what the licensor requests.

:Sometimes, the author will also provide a copyright notice, which consists of the copyright symbol, year of publication, and the name of the author/licensor. Include the copyright notice as a part of your attribution if such information is provided.

'''Source''': Where can people find the work?

:Please make it possible for future users to find the source of the material by including a URL or hyperlink where the work resides. This often is where you found the work. If you found it somewhere other than the original site, try to include information about the original site where the work was first shared publicly. It is also better to use the original URL instead of a shortened link, whether you are hyperlinking or printing out the entire URL.

'''License''': How can you use the work?

:You must specify which CC license was applied to the work you are reusing. Each of the six different CC licenses come with distinct requirements for re-use. We recommend that you name and provide a link to the license, e.g., [http://creativecommons.org/licenses/by/4.0 CC BY 4.0] (http://creativecommons.org/licenses/by/4.0) for a work licensed under CC BY 4.0.

:Consider also including the “disclaimer of warranties,” which clarifies that the author makes no representations or warranties about the non-infringement or absence of other defects concerning the CC-licensed work. In plain English, this means that the users will use the work at their own risk.

:To sum up, if the licensor has provided any information related to TASL, consider including them in your attribution. We also recommend providing links to the Title, Author, Source, and License, where possible, so future users can easily access the information they need on a work and the license terms.
<hr>
===Reasonable attribution===

The CC licenses ask you to be reasonable:

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 90%;">You may satisfy the attribution requirement in any reasonable manner based on the medium, means and context in which the Licensed Material is used. For example, it may be reasonable to satisfy some or all of the conditions by retaining a copyright notice, or by providing a URI or hyperlink associated with the Licensed Material, if the copyright notice or webpage includes some or all of the required information.</div>

There is no single best or correct way of attribution, as long as your attribution is reasonable and suited to the medium you're working with. That being said, please include attribution somehow, even if it's a link to an About page that has the relevant info. (More on different media below.)
<hr>

===Devil in the details===

If you have any doubts or questions, you can read the complete attribution requirements which are spelled out in detail in the legal code of every CC license, eg. http://creativecommons.org/licenses/by/4.0/legalcode This [[License_Versions#Detailed_attribution_comparison_chart|chart compares the detailed requirements across all versions of CC licenses.]]

==Examples of attribution==

We will now look at some examples in different media.

===Attributing an image===

Here is a photo. Below, we will go over some good and bad examples of how people might attribute it.

[[File:8256206923_c77e85319e_n.jpg]]
<hr>

====This is a great attribution====
<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">
"[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Creative Commons 10th Birthday Celebration San Francisco]" by [http://www.flickr.com/photos/sixteenmilesofstring/ Timothy Vollmer] is licensed under [http://creativecommons.org/licenses/by/4.0/ CC BY 4.0]</div>

''Let’s go through TASL:''
:'''T'''itle? "Creative Commons 10th Birthday Celebration San Francisco"
:'''A'''uthor? "[http://www.flickr.com/photos/sixteenmilesofstring/ Timothy Vollmer]" - linked to his profile page
:'''S'''ource? "[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Creative Commons 10th Birthday Celebration San Francisco]" - linked to original Flickr page
:'''L'''icense? "[http://creativecommons.org/licenses/by/4.0/ CC BY 4.0]" - linked to license deed

Most importantly, this attribution reasonably includes all the relevant information provided by the author.
<hr>

====This is a pretty good attribution====

<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Photo] by Timothy Vollmer/ [http://creativecommons.org/licenses/by/2.0/ CC BY]</div>

''Let’s go through TASL:''
:'''T'''itle? Title is not noted but at least the source is linked.
:'''A'''uthor? "Timothy Vollmer"
:'''S'''ource? "[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Photo]" - linked to original Flickr page
:'''L'''icense? "[http://creativecommons.org/licenses/by/4.0/ CC BY]" - linked to license deed

As you see, a good attribution includes all the essential '''TASL''' elements, even though they may not mirror the format of credit the author has requested.
<hr>

==== This is an incorrect attribution====
<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">Photo: Creative Commons</div>

''Let’s go through TASL'':
:'''T'''itle? Title of the image is not noted
:'''A'''uthor? Author is not noted (It is a common mistake to attribute CC-licensed photos to CC, but Creative Commons is not the author!)
:'''S'''ource? No link to the original source
:'''L'''icense? There is no mention of a license nor a link to the license. "Creative Commons" is the name of an organization; it does not equate to any of the licenses maintained by the Creative Commons.
<hr>

====This is a great attribution for an image you modified slightly====
:[[File:Cropped_tvol_cupcake.png|300px]]

<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">"[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Creative Commons 10th Birthday Celebration San Francisco]" by [http://www.flickr.com/photos/sixteenmilesofstring/ Timothy Vollmer], used under [http://creativecommons.org/licenses/by/4.0/ CC BY 4.0] / Cropped from original</div>

Here, information on '''T'''itle, '''A'''uthor, '''S'''ource, and '''L'''icense are all included as requested by the author. The slight modification is also noted and briefly described.

Note if the modification changes the work’s meaning in a way that would be considered creative — that is, not a purely mechanical change or a simple crop/excerpt that keeps the original message undistorted, it would be considered creating a new adaptation of the original work. You cannot rely on a CC license that does not allow adaptation (e.g., CC BY-ND or CC BY-NC-ND) when making such modifications.

<hr>

====This is a great attribution for when you have created an adaptation====

:[[File:8256206923_c77e85319e_n_90fied.jpg|300px]]

<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">This work, "90fied", is adapted from "[http://www.flickr.com/photos/sixteenmilesofstring/8256206923/in/set-72157632200936657 Creative Commons 10th Birthday Celebration San Francisco]" by [http://www.flickr.com/photos/sixteenmilesofstring/ Timothy Vollmer], used under [http://creativecommons.org/licenses/by/4.0/ CC BY 4.0]. "90fied" is licensed under [http://creativecommons.org/licenses/by/4.0/ CC BY 4.0] by [Your name here].</div>

''Let’s go through TASL:''

Original '''T'''itle, '''A'''uthor, '''S'''ource, and '''L'''icense are all noted.

The original work is referenced and the fact that it is an adaptation is also noted, so viewers can see what has changed.

The author and other attribution information for the new adapted work is also noted.

Note: If you're at a point where you are licensing works that are adaptations, go to [[Marking your work with a CC license]].
<hr>

===Attributing music===

====When you incorporate music in an audio or video recording====
Music (both the underlying composition and the sound recordings) — such as a song, or a recording of natural sounds — can be attributed within the audio/video, and in the description text of the audio/video. How to attribute a CC licensed music in an audio or video recording will largely depend on what is reasonable for a chosen medium and platform.

Caution: Licenses with “ND” do not allow for adaptations. Your use of CC-licensed music is often an adaptation!

It is considered adaptation if you incorporate CC-licensed music into your work in a way that the CC-licensed music can no longer be seen as a stand-alone piece. For example, if you are using a song as background music in a podcast or in a video, it is considered an adaptation of the song.

Keep in mind that CC BY-ND and CC BY-NC-ND do not allow adaptations (although you may be authorized by law to do so, such as under a users’ right like fair use, or you may ask for the author’s permission independent of the CC license).
<hr>

[[File:Smithsonian_music_stand.jpeg|left|250px]]

=====This is a great attribution of background music in a podcast or a video=====
When reasonable to do so, we recommend that you include attribution both in the description box and in the podcast recording or the video recording itself.

If you are using the following song in a podcast: ‘Day Bird’ by Broke for Free ([https://brokeforfree.com brokeforfree.com]), this would be a great way to provide attribution (which you can see in [https://soundcloud.com/wearecc/open-minds-podcast-catherine-stihler-ceo-of-creative-commons the Creative Commons podcast]) —

:At the end of the podcast audio recording, the host says:
:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 90%;">Special thanks to the musician Broke for Free, whose track “Day Bird” you heard at the beginning of this episode and you are listening to right now. It's under the Creative Commons Attribution License, meaning it's free for anyone to use. You can find it at the Free Music Archive—freemusicarchive.org</div>

:In the description box, the information text reads:
:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 90%;">Theme music: “Day Bird” by Broke for Free ([https://brokeforfree.com brokeforfree.com]). Available for use under the CC BY 3.0 license ([https://creativecommons.org/licenses/by/3.0/ creativecommons.org/licenses/by/3.0/]), at [https://freemusicarchive.org/music/Broke_For_Free/Directionless_EP/Broke_For_Free_-_Directionless_EP_-_03_Day_Bird|the Free Music Archive].</div>

''Let’s go through TASL:''

:'''T'''itle? Both the recording and the description box include the title of the work, “Day Bird”

:'''A'''uthor? "Broke for Free," again, noted both in the recording and in the description box

:'''S'''ource? Both the author’s page and the archive’s page are included with links

:'''L'''icense? "CC BY 3.0" — linked to license deed

You cannot talk over, or remix, music licensed under CC BY-ND or CC BY-NC-ND.

<hr>

=====This is a bad attribution of background music in a podcast or a video=====

A bad attribution is one where you do not provide enough information for a user to find the music you are using. The following is a bad attribution for the same song:

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">No attribution is included in the podcast recording or the video itself.

In the description box, it says: “ Creative Commons music.”</div>

''Let’s go through TASL:''

:'''T'''itle? Title is not noted

:'''A'''uthor? Author is not noted

:'''S'''ource? Source is not noted; users cannot find the specific song used in the podcast

:'''L'''icense? No information on the CC license

The attribution information is not sufficient for people to find the song you have re-used.
<hr>

====When you are not adding new elements to the music====
When you re-use music without adding new elements to it, you are not making an adaptation. In that case, you can rely on any of the CC licenses, including CC BY-ND and CC BY-NC-ND. We recommend providing attribution information in writing.

[[File:Wiki_page_attributing_night_owl.png|400px]]

On [https://commons.wikimedia.org/wiki/File:Broke_For_Free_-_01_-_Night_Owl.ogg this Wikipedia page], you can see an example of great attribution for the sharing another soundtrack, “Night Owl” by Broke for Free, when it’s without adaptation.

''Let’s go through TASL:''

'''T'''itle? Title of the work, “Night Owl,” is noted

'''A'''uthor? "Broke for Free," noted and linked to the author’s webpage

'''S'''ource? A link is provided for the source

'''L'''icense? "CC BY 3.0" — linked to license deed
<hr>

===Attributing text===
Let’s take [https://github.com/getify/You-Dont-Know-JS ''You Don't Know JS Yet'' (2nd Edition)] as an example, and go over what your attribution may look like if you reuse the book series. The information under the “License & Copyright” section looks like this on the webpage where the book series was originally shared:
:[[File:attributing_You_Don't_Know_JS_Yet_(2nd_Edition).png|200px]]

We recommend that you retain all the information provided by the author of the book series when it is reasonable for you to do so. For example, if you are distributing digital copies or excerpts of the book series in a free seminar, or using parts of the book in a free online course or presentation, the attribution will likely look something like this:

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">This chapter is from “[https://github.com/getify/You-Dont-Know-JS You Don't Know JS Yet (2nd Edition)]” by [https://github.com/getify Kyle Simpson]. The book is licensed under the [https://creativecommons.org/licenses/by-nc-nd/4.0/ CC BY-NC-ND 4.0 license]. © 2019-2022 Kyle Simpson.</div>

On the other hand, if you are distributing hard copies of the book series or excerpts from the book series, instead of using hyperlinks, you may wish to include the links so it’s easier for users to locate the original source of the book, the author, and the CC license:

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">This chapter is from “You Don't Know JS Yet (2nd Edition)” (https://github.com/getify/You-Dont-Know-JS) by Kyle Simpson (https://github.com/getify). The book is licensed under the CC BY-NC-ND 4.0 license (https://creativecommons.org/licenses/by-nc-nd/4.0/). © 2019-2022 Kyle Simpson.</div>

Note that the CC BY-NC-ND license includes the NoDerivatives requirement, which indicates that no adaptations are allowed. You cannot make any adaptations relying on the CC BY-NC-CD license the author chose for the book. If you would like to make a translation of the book, for example, you will need to ask the author for permission first.

The CC BY-NC-ND license also includes the NonCommercial requirement. To learn more, take a look at [https://en.wikipedia.org/wiki/Creative_Commons_NonCommercial_license this page here].
<hr>

=== Attributing materials from multiple sources ===

:[[File:Saylor_marking_example.jpg]]

''Let’s go through TASL:''

:'''T'''itle? Specific works are named, e.g., "Box-and-whisker Plots"

:'''A'''uthor? Different authors noted for the different works

:'''S'''ource? Original materials are linked for each work

:'''L'''icense? The different licenses (Creative Commons Attribution for Collaborative Statistics and Creative Commons Attribution-Noncommercial-ShareAlike for the Khan Academy video) are spelled out and linked for each work

:Lastly, it is clear which attribution belongs to which work.

You can visit the [http://www.saylor.org/courses/ma121/ Saylor.org Introduction to Statistics course page] to see how they marked it up directly.
<hr>

=== Publishing a web page for attribution ===
As stated above, recommended attribution depends on the medium you're working with. For media such as offline materials, video, audio, and images, consider publishing a web page with attribution information. For example, on a webpage featuring your audio recording, provide a credit list of material you used that adheres to best practices above. Doing so allows not only your material, but the materials you attribute, to be found by search engines and other web discovery tools. If possible within the medium, make the Author, Source, and License links the user can follow.

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">'''Example:'''<br>This video features the song [http://ccmixter.org/media/files/victor/6374 "Desaprendere (Treatment)"] by [http://fourstones.net/ fourstones], available under a Creative Commons [http://creativecommons.org/licenses/by-nc/2.5/ Attribution-Noncommercial] license.</div>

<hr>

==Attributing public domain materials==
Although attribution is not a legal obligation under [https://creativecommons.org/share-your-work/public-domain/cc0/ CC0 dedication]’s or [https://creativecommons.org/share-your-work/public-domain/pdm/ CC Public Domain Mark]’s licensing terms, we recommend that you consider providing attribution to the source for public domain materials when it is reasonable to do so. Attribution of public domain works not only encourages institutions to digitize and share more public domain materials in their physical collections, but also empowers users to easily locate the original source.

The following public domain image is digitized and hosted by the Rijksmuseum (the national museum of the Netherlands). The Rijksmuseum has applied a CC0 dedication to the image.

:[[File:Attributing_the_milkmaid.png|300px]]

You may provide credit in the following format:

:<div style="padding: 1em; margin-bottom: 1em; border: 1px; background-color: #eee; width: 65%;">“[http://hdl.handle.net/10934/RM0001.COLLECT.6417 The Milkmaid]” by Vermeer. The Rijksmuseum collection. The image is dedicated to the public domain under [https://creativecommons.org/share-your-work/public-domain/cc0/ CC0]. </div>

In most cases, people credit the source regardless of the work’s copyright status. Especially in an academic setting, providing source information about other people’s works has long been considered crucial to academic integrity. Copyright cannot be the only checkbox when deciding whether a source will be attributed.

== Common pitfalls ==

Below are some practices that you may wish to avoid. These practices are not always contrary to the Creative Commons licensing terms, but they often make it more challenging for users to find the original source and/or author.

'''Attribute in alt text'''
:Alt text is intended to provide accessible information about visual materials for users with cognitive disabilities or visual impairment. Using this field for licensing information makes browsing difficult for those users.

'''Attribute in metadata fields only'''
:While it is great to include attribution in metadata fields (such as EXIF for images), in most cases this is not the only place to include attribution information. This is because many users are likely not aware of, and will never see, attribution information included in metadata.

'''Credit authors by names other than the ones they have selected'''
:Many people believe that attribution must be given to the real name of the author of a work, but this is not the case — always give attribution to the name the author has specified, even if it is a pseudonym. If the author does not give a name or explicitly requests to be anonymous, you must give the other attribution information (i.e., “T” and “SL” from “TASL”) without crediting the author.

'''Credit a site (or Creative Commons itself!) instead of the author'''
:Unless an author specifically requests users to only credit a site, crediting the site where you have found the material cannot substitute crediting the author. An author may have uploaded material to a site under a CC license, but in most cases, the copyright is still held by the author, and it is the copyright holder who needs to be credited. For example, many photos sourced from Wikimedia Commons are attributed to Wikimedia when they must be attributed to the authors.

== Other guides to attribution ==

* [http://creativecommons.org.au/materials/attribution.pdf Attributing Creative Commons Material] (pdf) - Creative Commons Australia's publication is full of examples with colorful imagery.
* [http://www.newmediarights.org/guide/how_to/creative_commons/best_practices_creative_commons_attributions How to attribute works you reuse under a Creative Commons license] by New Media Rights provides real world examples by different media type

[[Category:Marking]]
[[Category:Licensing]]
[[Category:Community]]
[[Category:Media]]
[[Category:HOWTO]]
[[Category:Guide]]
{{Best Practice}}