W3C home > Mailing lists > Public > public-html@w3.org > September 2009

Re: ISSUE-81 (resource vs representation)

From: Karl Dubost <karl+w3c@la-grange.net>
Date: Mon, 28 Sep 2009 06:58:49 -0400
Message-Id: <2C6AECC0-3570-44CE-85A1-B8AF8CCE7916@la-grange.net>
Cc: Julian Reschke <julian.reschke@gmx.de>, "public-html@w3.org" <public-html@w3.org>
To: Maciej Stachowiak <mjs@apple.com>

Le 27 sept. 2009 à 05:36, Maciej Stachowiak a écrit :
> It seems to me that "resource" and "representation" are both normal  
> English words that are used in a variety of ways in the world of  
> computing. Since there is no ambiguity in HTML5's use, I do not  
> think we need to micromanage the word choice.

On Wed, 10 Aug 2005 12:30:15 GMT
In QA Framework: Specification Guidelines
At http://www.w3.org/TR/qaframe-spec/#reuse-terms-gp

Good Practice 10: Use terms already defined
without changing their definition.

What does it mean? When a definition for a term
already exists (e.g. in a different specification)
and matches the specification needs, reuse the
term and its definition without changing it, and
provide a reference to the source.

Why care? Reusing existing terms reduces the cost
of creating new definitions and makes it easier
for readers already familiar with other
specifications to get into the new one. In
addition, conflicting definitions for the same
term lead to reduced interoperability.




-- 
Karl Dubost
Montréal, QC, Canada
http://twitter.com/karlpro
Received on Monday, 28 September 2009 10:59:03 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:39:08 UTC