Teaching Whose Code Is It? in Grade 5: Oklahoma Standard 5.AP.PD.02

Teaching intellectual property in grade 5 does not have to be complicated. Picture a filmmaker licensing every song and listing everyone in the closing credits. That kind of thinking is exactly what Oklahoma's grade 5 computer science standard 5.AP.PD.02 asks students to practice — and it is very teachable with the right materials. This post walks through what the standard means, the misconceptions students bring to it, and discussion starters you can use tomorrow, whether you teach in a classroom or at your kitchen table.

What Does Standard 5.AP.PD.02 Actually Ask?

Observe intellectual property rights and give appropriate credit when creating programs using original code or code reuse. — Oklahoma Academic Standards for Computer Science (February 2023)

In plain language: Oklahoma's standard asks fifth graders to respect intellectual property rights and give appropriate credit when they build programs, whether they write their own original code or reuse code that someone else shared.

In student-friendly terms, the learning target is: "I can observe intellectual property rights and give appropriate credit when I create programs, whether I write original code or reuse code from someone else."

What Students Should Be Able to Do

• I can explain what intellectual property and copyright mean in my own words.
• I can read a license to find out how I am allowed to reuse someone's work.
• I can write a credit line that names the creator, the work, and the source.
• I can explain the difference between honest reuse and plagiarism.

Along the way, students pick up the working vocabulary of the topic: program, source, copyright, share, rights, reuse, plagiarism, credit, permission, original, creator, license.

Intellectual Property: Misconceptions to Watch For

These are the wrong turns students reliably take with this standard — knowing them ahead of time is half the lesson plan. Each correction strategy below comes straight from the unit's teacher guide (the paragraph and activity references point into the unit itself).

1. "Reusing someone else's code is always cheating or against the rules."

Return to paragraph 3: licenses make reuse honest and legal. Reuse becomes wrong only when you ignore the license or hide the source. Have students name a license rule that makes reuse allowed.

2. "It is only plagiarism if you copy a large amount of work."

Use paragraph 5: the difference is honesty, not quantity. A clearly credited hundred lines is honest; ten hidden lines is plagiarism. Ask students to judge examples by honesty, not size.

3. "You only own a copyright if you officially register or pay for it."

Paragraph 2 explains copyright begins automatically when an original work is created. Reinforce that even a fifth grader's program is automatically protected.

4. "Giving credit is just being polite; it does not really matter."

Paragraphs 4 and 7 frame credit as honesty, respect, and what keeps creators sharing. Connect to professional consequences: lawsuits and lost jobs for skipping credit.

Discussion Starters You Can Use Tomorrow

• How would you feel if someone copied a project you worked hard on and put their name on it? What does that tell you about why these rules exist?
• Why do you think so many programmers share their code with licenses that allow reuse if you give credit?
• What is the difference between borrowing a friend's idea honestly and plagiarizing it?

Bringing It Home

This topic is a natural one for families. One ten-minute activity to try: Watch the credits at the end of a movie or show together, or look at the small print on a song or app. Ask your child to explain why all those names are listed and connect it to 'giving credit' in a computer program. Then have them point out one thing they made that is their own intellectual property.

Where This Leads

Students who can observe intellectual property rights and give appropriate credit when I create programs, whether I write original code or reuse code from someone else are building skills used every day in software development, law and intellectual property, music and film production, publishing, and digital media.

Part of the Complete Grade 5 Computer Science Curriculum

This lesson covers just one standard. It is part of a complete grade 5 computer science curriculum aligned to every Oklahoma OAS CS standard. See the full listing — every standard, organized by strand — here: Grade 5 Computer Science Curriculum: Every Oklahoma OAS CS Standard.

See the Unit in Action

Get the Complete 5.AP.PD.02 Unit

I built a complete, no-prep unit for this standard — Whose Code Is It? Intellectual Property and Giving Credit — covering 3-4 days of instruction across 40 pages:

• Teacher guide — day-by-day pacing, misconceptions to watch for, discussion questions, differentiation for support / ELL / extension, and a 4-point rubric
• Student learning target page — a kid-friendly "I can" statement with success criteria
• Full content lesson with 3 embedded "Check Your Understanding" checkpoints
• 12-question assessment (6 multiple choice, 4 true/false, 2 short answer) with a complete answer key, explanations, and exemplar responses
• Group activity — "Credit Detectives: Reuse It the Right Way" (25-30 minutes)
• Individual activity — "My Credits Page" (15-20 minutes)
• Crossword and word search built from all 12 vocabulary terms (with answer keys)
• Family connection letter — a plain-language page for parents, with dinner-table questions and a 10-minute home activity
• Certificate of achievement — ready to sign and send home
• Reuse Scenario Cards (separate printable, 2 pages)
• Intellectual Property Reference Sheet (separate printable, 2 pages)
• My Credits Page (separate printable, 1 page)

Get Whose Code Is It? on Teachers Pay Teachers →

Also aligned to CSTA 1B-AP-14: Observe intellectual property rights and give appropriate attribution when creating or remixing programs.

Every Sooner Standards resource is built directly from the official Oklahoma Academic Standards for Computer Science (February 2023) — standard text verified, never paraphrased from memory.