deletions | additions       diff --git a/Rule 7. Be explicit about credit.md b/Rule 7. Be explicit about credit.md  index a23d172..5f99091 100644  --- a/Rule 7. Be explicit about credit.md  +++ b/Rule 7. Be explicit about credit.md 
...
#Rule 7. Say how you want to get credit.  Chances are that you want to get credit for what you share. The attribution system used for scholarly articles, accomplished via citations, often breaks in the case of data and software. When other authors reuse or cite your data or code, you may get an acknowledgement or an incoming link. If you and your colleagues have gone to the trouble to write a "data paper," whose main purpose is to describe your data and/or code, you may also get a citation. \cite{Chavan_Penev_2011} But, "data paper" writing is not always desirable, or relevant. So, how do you go about getting the full credit you deserve for your data and code? **The best way is to simply describe your expectations on how you would like to be acknowledged.** If you want, **you can also release your data under a license and indicate explicitly in the paper or in the metadata how you want others to give you credit.** But, while legal mechanisms have advantages, they can also inadvertently lead to limitations on the reuse of the data you are sharing. In any case, **make information about you (e.g. name, institution), about the data and/or code (e.g. origin, version, associated files and metadata), and about exactly how you would like to get credit, as clear as possible.** Easy-to-implement licenses, many of which offer the advantage of being machine-readable, are offered by the [Creative Commons](http://creativecommons.org/choose/) organization, as are other similar options, such as those offered by [Open Data Commons](http://opendatacommons.org/licenses/pddl/).The  Appendix G  provides more information information.