- HOW TO PROPERLY CITE SOURCES MLA HOW TO
- HOW TO PROPERLY CITE SOURCES MLA FULL
- HOW TO PROPERLY CITE SOURCES MLA SOFTWARE
- HOW TO PROPERLY CITE SOURCES MLA CODE
If the URL does not provide the full path to the file, you should include the full path as the file name. If you are citing these sources in a format that has the ability to display hyperlinks-for instance, if they will be displayed in html-do include the protocol. The MLA recommends removing “ and “ protocols from URL addresses in printed works, in which the creation of hyperlinks is irrelevant, although if the protocol is anything else, such as “ftp://,” you should include it.
HOW TO PROPERLY CITE SOURCES MLA CODE
If you are documenting source code on a website, provide the URL as the location.
HOW TO PROPERLY CITE SOURCES MLA SOFTWARE
In what follows, the website GitHub is the second container. No publisher is specified for the website GitHub, because it is published by GitHub ( MLA Handbook 42).Ĭ1dbc3e6fce133f77, Apache Software Foundation, 2015. If you are consulting code on a website, you will need to provide information for that website as the second container. Since there is no information relevant to the “Location” element, this is the end of container 1.
If you do see a date, provide it:Ĭ1dbc3e6fce133f77, Apache Software Foundation, 2015. The date may not be specified in source code, in which case you can omit it. Here, the software that contains the source code is published by the Apache Software Foundation:īuffer.java. The publisher for the software or the package in which the code is found is usually the organization that produced the code. In the example that follows, the commit hash appears after the package name and specifies the version of the code being cited:īuffer.java. This is important information because both URLs and source code tend to change, so providing as much information as possible makes it more likely that readers will be able to find what you are citing. This could be a version of software, a particular revision in a repository, or a commit hash (a unique string of letters and numbers that identifies a version of a piece of code). Since source code often exists in several versions, provide the version of the code you consulted. For Buffer.java, the container is Apache Hadoop, a collection of software: The code for a piece of software is contained in the software itself, and so the software is the container. 2 A package is a container of source code files within a larger program. The container will be either the name of the software or the package in which the code is found. To cite the source code for Buffer.java, begin your entry with the title: Examples of file extensions on source code files include. Provide the file extension when you give the title. The cases of characters are meaningful in a programming context, so you should reproduce the file name exactly as you found it. However, you should not do this for titles of source code. When citing titles in MLA style you would normally standardize the capitalization.
Source code is typically presented in discrete text files, and the file name can serve as the title.
In the rest of the post, I walk you through the process of creating a works-cited-list entry for a work of source code, Buffer.java, where the publisher is the author. If the organization is both author and publisher, begin your entry with the title. If individual contributors are not given, treat the organization named as the owner of the license or the holder of the copyright as the author. Authors are usually specified in the code itself or, on a website like GitHub, as the owner of the repository in which the code appears. Source code can be written by a person, a group of persons, or an organization (e.g., Chromium Authors).
HOW TO PROPERLY CITE SOURCES MLA HOW TO
1 In what follows, I explain how elements on the template apply to source code and show you how to construct an entry. To cite source code-the written portion of a piece of software or a larger program-begin with the MLA format template. For up-to-date guidance, see the ninth edition of the MLA Handbook. Note: This post relates to content in the eighth edition of the MLA Handbook.
0 kommentar(er)
