Assigned Today
Before next week, please read “Annual Report to the Nation on the Status of Cancer, 1975–2014, Featuring Survival” (2017) by Jemal et al. (LINK).
Please also read the Open Technical Communication chapter on Page Design (LINK).
Today’s Content
We’ll talk through all of the evidence provided in Adkins et al. (2008). The main question we’ll be asking ourselves is why is this here? Technical documents need to carefully choose the evidence they provide to keep a document as concise as possible. Academic documents tend to have broader audiences, so they must provide broader evidence to meet the needs of all possible readers.
So, we will dive into Adkins et al. (2008) to better understand what the function is of each citation. Audiences won’t always read the entire document we give them, but they will read what they need to (or what they think they need to, based on our signalling) to understand what we’re getting at.
We will use Nigel Harwood’s classifications of citation functions in this conversation:
| Advertising | To alert readers to authors’ own work or to the work of others |
| Building | To help authors develop methods or ideas |
| Competence | To underscore authors’ expertise |
| Credit | To acknowledge authors’ debts |
| Engaging | To help authors have a critical dialogue with their sources |
| Future | To establish future research plans |
| Position | To help authors identify viewpoints and findings |
| Signposting | To direct readers to other sources |
| Supporting | To help authors justify their research topic, method, or claim |
| Topical | To show authors are concerned with state-of-the-art issues |
| Tying | To align authors with others’ methods or with other schools of thoughts or debates |
we’ll look at the background section and talk about the ways they set some of this up. Today or Friday, we’ll talk through a summary process called a rhetorical precis, which is composed of four sentences:
- A description of what the document is (report, article, blog post, video, etc.) and what it DOES (argues, advocates, evaluates, describes, etc.)
- A description of how the document gathered or organized its information (its methods section or its supporting background info)
- A description of the document’s ultimate purpose or reason for existing
- A description of the document’s target audience or ideal user-base