W3C home > Mailing lists > Public > www-tag@w3.org > December 2008

Re: Extensibility and Uniformity; defining "error" behavior

From: John Kemp <john.kemp@nokia.com>
Date: Tue, 30 Dec 2008 09:53:56 -0500
Message-ID: <495A3604.9010500@nokia.com>
To: ext Anne van Kesteren <annevk@opera.com>
CC: Larry Masinter <masinter@adobe.com>, Ian Hickson <ian@hixie.ch>, "www-tag@w3.org" <www-tag@w3.org>

ext Anne van Kesteren wrote:
> 
> On Tue, 30 Dec 2008 15:23:00 +0100, Larry Masinter <masinter@adobe.com> 
> wrote:
>> I think you are talking about "uniformity" when you use the word
>> "interoperability".
> 
> FWIW, the W3C generally uses the word "interoperability" where you say 
> "uniformity". See e.g. http://www.w3.org/TR/CSS21/#crec

Nonetheless, I think Larry's distinction is a useful one.

http://en.wikipedia.org/wiki/Interoperability

vs.

http://en.wiktionary.org/wiki/uniformity

(for example)

My understanding of this distinction at the specification level is that 
the technical specification(s) should provide the interface at which two 
implementations will interoperate. The "application statement" (which I 
have personally previously referred to as "implementation guidelines") 
then defines uniform behaviour across implementations within an 
"implementation class" with respect to the defined interface.

- johnk
Received on Tuesday, 30 December 2008 14:54:54 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 26 April 2012 12:48:09 GMT