Learn the basics of federal statute citation with 28 U.S.C. § 1332(a)(2) (2012). This guide clarifies why the format uses 28 U.S.C., what § 1332(a)(2) means, and how it differs from state codes, while keeping the explanation practical and easy to follow.

Multiple Choice

Which citation corresponds to Section 1332(a)(2) of Title 28 of the United States Code, as printed in 2012?

The key idea is recognizing a federal statute citation in the United States Code. The correct form uses 28 U.S.C. for Title 28 (the judiciary and jurisdiction), followed by the section and subdivision: § 1332(a)(2). The year in parentheses (2012) indicates the edition of the code being cited. The other options come from different codes—the Internal Revenue Code (I.R.C.) or state codes (Georgia or Virginia)—so they do not represent Title 28 of the United States Code. Therefore, the citation that matches Section 1332(a)(2) of Title 28, as printed in 2012, is 28 U.S.C. § 1332(a)(2) (2012).

Bluebook citations are the little GPS guides of legal writing. They tell readers exactly where to find a statute, a case, or a regulation without forcing them to hunt through a library—or, heaven forbid, a maze of footnotes. If you’ve ever strained to parse a citation and wondered, “What do all those abbreviations even mean?” you’re not alone. The good news is that once you get the hang of the pattern, it feels almost like reading a map with the turn-by-turn directions already printed on it.

Let’s start with the big idea: titles, then sections. The United States Code is organized by titles. Each title covers a broad slice of the law—Title 28, for instance, is all about the judiciary and federal courts. Within each title, you’ll find sections, and sometimes subdivisions, that zero in on a precise legal rule or provision. The Bluebook standard aims for a clean, uniform way to present those references so any reader—whether a law student, a practitioner, or a judge—knows exactly where to go.

A quick orientation: the anatomy of a federal statute citation

  • The title: This is the broad bucket that holds the law. For federal matters, you usually see something like 28 U.S.C. That means Title 28 of the United States Code.

  • The source: The abbreviation for the code. U.S.C. stands for United States Code. If you’re looking at a state statute, you’ll see things like Ga. Code Ann. or Va. Code Ann., which indicate Georgia or Virginia laws.

  • The section symbol: The familiar § marks the exact section. If there’s a subdivision, you’ll see something in parentheses or with a parenthetical, like (a)(2) describing a subdivision.

  • The year: Parenthetical year at the end shows the edition of the code you’re citing. Because laws change over time, the year helps the reader find the precise edition you had in mind.

So a pristine federal citation might look like 28 U.S.C. § 1332(a)(2) (2012). That tells you: Title 28, United States Code, section 1332, subdivision (a)(2), as it appeared in the 2012 edition. It’s precise, it’s portable, and it’s familiar to anyone who’s spent time in court or law school.

Why the year matters, and how to read it in context

The United States Code gets updated regularly. New sections are added, old ones are amended, even some are repealed. That’s why the year in parentheses is critical. It signals which edition you used, and it helps a reader verify the exact language you referenced. In practice, you’ll often see multiple versions cited in the same document—one to show the current law, another to point to the exact language as it appeared in a particular edition. In most scholarly or professional writing, you’ll be careful to indicate the edition you relied on because statutes can change and the precise text can matter in interpretive questions.

The “Title 28” clue

When you’re dealing with federal courts, jurisdiction, and procedure, Title 28 is your go-to. It houses the rules governing how cases move through the federal system, how judges are appointed, and how basic justice topics are organized at the federal level. If your reader is looking up a provision about federal subject matter jurisdiction, you can be fairly confident you’re within 28 U.S.C. That consolidation makes the referencing both efficient and predictable.

Common siblings of the same family

To appreciate the specificity of 28 U.S.C. § 1332(a)(2), it helps to look at the family tree of citations and the kinds of things you’ll see:

  • Statutes from the Internal Revenue Code: I.R.C. § 2036(a) (2012). These come from a different code family—the tax code—so the citation style shares the same bones but points to a different table of contents.

  • State codes: Georgia, Virginia, or any state code will look similar, but the leading portion will tell you you’re in a state law instead of federal law. Ga. Code Ann. § 16-6-2(a) (2010) or Va. Code Ann. § 18.2-387 (2014) are good examples of how state law gets its own abbreviations and year marks.

  • Federal rules and regulations: If you see a citation to an agency’s regulations, you’ll encounter a different format (for instance, 40 C.F.R. § 1501.7), but the core idea—title, code, section, year—remains the same in spirit.

Practical tips to master Bluebook style without turning it into a trivia night

  • Memorize the skeleton, not every quirky rule. The central pattern—Title Code Abbreviation § Section (Year)—is the backbone. Once that’s in your pocket, you’ll recognize most entries at a glance.

  • Learn the abbreviations that actually show up: U.S.C. for United States Code, U.S.C.A. for United States Code Annotated (where you’ll see the same mechanics but with annotated commentary), I.R.C. for Internal Revenue Code, and state codes with their own abbreviations. It’s a lot at first, but you’ll start spotting the rhythm.

  • Pay attention to the edition. If you’re unsure which year a text uses, check the surrounding citations or the bibliography in the document. If a sentence hinges on a precise statutory phrase, you’ll want the exact edition to avoid misinterpretation.

  • Use reliable reference tools. The official materials—heavily cited legislative databases, legal citator services, and, yes, the Bluebook itself—are helpful. For quick checks, many law libraries provide access to citation lookup tools. If you’re writing for a publication or a class, there’s rarely a substitute for confirming with a trusted source.

  • Practice with real-world examples. Take a well-known federal statute, pull its citation, and examine how the year and subdivision are used. Then compare with a state statute to see the similarities and differences in formatting.

A quick detour into “pattern recognition” and why it works

Humans are pattern-seeking machines. We love templates that feel almost algorithmic because they reduce cognitive load. The Bluebook format is exactly that: a compact, repeatable ritual that turns a potentially overwhelming sea of numbers into a navigable map. Once you get the hang of it, you’ll see patterns in quick glimpses—Title 28, U.S.C., § 1332(a)(2), (2012)—and you’ll instinctively know what’s inside and where to go if you need to verify a line or compare versions.

A few common pitfalls to avoid

  • Mixing up the code family. It’s easy to slip into I.R.C. land when you’re thinking about tax provisions, but the citation is not the same as a federal statute. Keep the code abbreviations straight—U.S.C. for federal code, I.R.C. for tax code, state abbreviations for state law.

  • Forgetting the year. The statute text can shift with amendments. The year matters. If you can’t recall it, you risk citing the wrong language.

  • Missing subdivisions. Some sections have multiple parts (like (a), (b), or (2)). The year tells you the edition, but the subdivision tells you exactly which slice of the text you’re pointing to.

Why precise citations matter in legal writing

Citations aren’t just about looking smart or keeping pedantry at bay. They serve three crucial purposes:

  • They anchor your assertions in a traceable source. If someone wants to see the exact text you’re relying on, they should be able to find it without guesswork.

  • They preserve intellectual honesty. A precise citation shows you’ve done the legwork and aren’t misrepresenting the source.

  • They aid comparison and interpretation. When different branches of the code or different jurisdictions are relevant, clear citations help readers compare apples to apples.

A practical example in everyday reading

Imagine you’re cataloguing a federal provision that touches on the limits of federal court jurisdiction in diversity cases. The clean citation would look something like 28 U.S.C. § 1332(a)(2) (2012). It tells you immediately:

  • Title and subject matter: federal judiciary and jurisdiction

  • The specific rule: the diversity jurisdiction cap in certain circumstances, as refined by the subdivision

  • Edition: the 2012 code you’re using as the reference point

Now imagine you’re also noting a Georgia statute about contract law. You’d switch gears but keep the same anatomy:

  • Ga. Code Ann. § 33-5-1 (2010)

Here the same structural logic applies, though the content points you to a state-specific rule, and the edition year ensures you know exactly which text you’re citing.

Bringing it all home: why this matters beyond the page

Bluebook-style citations aren’t just about pleasing professors or flipping a switch for a legal database search. They’re about building a shared language. They allow readers across offices, jurisdictions, and even countries to engage with the same material with confidence. When you see 28 U.S.C. § 1332(a)(2) (2012), you know you’re looking at a precise slice of federal law, as it appeared in a specific edition. It’s a tiny thing, but it’s a bridge—between text and interpretation, between reader and source, between memory and the actual law.

If you’re new to this world, give yourself permission to start small. Deliberately read a few citations in law review articles or court opinions. Note how the authors juggle Title, code, section, and year, and how everything else bends around that structure. As you practice, you’ll notice that the discipline isn’t stiff or dry; it’s a clean way to tell a precise legal story without getting tangled in the weeds.

A final thought to carry forward: the elegance of clarity

In the end, good legal writing distills complexity into clarity. A well-crafted citation is a compact sentence of its own—tiny, efficient, and informative. It’s not flashy, but it matters. It helps readers trust what they’re reading, locate the source, and follow the logic from statute to argument to conclusion. And that, in the grand scheme of law-writing, is a pretty elegant achievement. If you ever feel overwhelmed by the alphabet soup of abbreviations, remember that the structure is your friend. Title, code, section, year—a reliable compass in the vast landscape of U.S. law.