In conversing about the DC, we have used the terms Resource and Object
interchangeably. That habit is not a big problem in speech, but in
technical writing (eg, User Guide) and in the naming of DC elements it's
ill-advised to use more than one term for the same concept. I propose
that we officially adopt the habit of writing only the term "Resource".
Pro: "resource" is consistent with IETF terminology, the R in URL, URN, URI.
Pro: "object" is one of the more hyped and overloaded words in computer
science; unless we clearly mean "object oriented" (which we don't), we will
forever be explaining and avoiding words in the object oriented lexicon,
such as "class", "method", "message", "inheritance", etc. We'll have no
trouble using those words if we don't encourage the wrong interpretation
by bandying about the term "object" as if we meant you-know-what by it.
-John
|