decoration decoration
Stories

GROKLAW
When you want to know more...
decoration
For layout only
Home
Archives
Site Map
Search
About Groklaw
Awards
Legal Research
Timelines
ApplevSamsung
ApplevSamsung p.2
ArchiveExplorer
Autozone
Bilski
Cases
Cast: Lawyers
Comes v. MS
Contracts/Documents
Courts
DRM
Gordon v MS
GPL
Grokdoc
HTML How To
IPI v RH
IV v. Google
Legal Docs
Lodsys
MS Litigations
MSvB&N
News Picks
Novell v. MS
Novell-MS Deal
ODF/OOXML
OOXML Appeals
OraclevGoogle
Patents
ProjectMonterey
Psystar
Quote Database
Red Hat v SCO
Salus Book
SCEA v Hotz
SCO Appeals
SCO Bankruptcy
SCO Financials
SCO Overview
SCO v IBM
SCO v Novell
SCO:Soup2Nuts
SCOsource
Sean Daly
Software Patents
Switch to Linux
Transcripts
Unix Books

Gear

Groklaw Gear

Click here to send an email to the editor of this weblog.


You won't find me on Facebook


Donate

Donate Paypal


No Legal Advice

The information on Groklaw is not intended to constitute legal advice. While Mark is a lawyer and he has asked other lawyers and law students to contribute articles, all of these articles are offered to help educate, not to provide specific legal advice. They are not your lawyers.

Here's Groklaw's comments policy.


What's New

STORIES
No new stories

COMMENTS last 48 hrs
No new comments


Sponsors

Hosting:
hosted by ibiblio

On servers donated to ibiblio by AMD.

Webmaster
Conflating semantics | 197 comments | Create New Account
Comments belong to whoever posts them. Please notify us of inappropriate comments.
Conflating semantics
Authored by: Anonymous on Sunday, May 13 2012 @ 06:04 PM EDT
I don't think it gets you very far to conflate two entirely different semantics
by treating ever so slightly varying grammar and context as insignificant.

"A Java bytecode" refers to a single instruction within a bytecode
file or within memory. No other data that this single instruction references
can be part of this thing called "a Java bytecode", regardless of
where it resides, if it is not contained within this single instruction.

In contrast, "Java bytecode" can refer to one or more multiples of
"a Java bytecode", or it can refer to the whole file which normally
contains bytecodes and other data, or if you use the term very generically , it
can refer to entire concepts related to Java implementation.

You have to use context to distinguish between these meanings. When the
discussion is very specifically about the operation of data referencing by a
given bytecode instruction, as in the case of that patent, then you're not
really free to bring in the broader meanings of these words that would apply in
different contexts.

English has a limited supply of words, and we reuse them very often to convey
varying semantics. In this case though, it's very clear that the context is a
single bytecode instruction, because the patent refers to that repeatedly.

[ Reply to This | Parent | # ]

Groklaw © Copyright 2003-2013 Pamela Jones.
All trademarks and copyrights on this page are owned by their respective owners.
Comments are owned by the individual posters.

PJ's articles are licensed under a Creative Commons License. ( Details )