W3C home > Mailing lists > Public > www-qa@w3.org > May 2004

Re: Extension/Extensibility examples in W3C Specifications

From: Dominique HazaŽl-Massieux <dom@w3.org>
Date: Tue, 04 May 2004 17:20:47 +0200
To: Mark Skall <mark.skall@nist.gov>
Cc: Lynne Rosenthal <lynne.rosenthal@nist.gov>, Karl Dubost <karl@w3.org>, www-qa@w3.org
Message-Id: <1083684047.1292.4987.camel@stratustier>
Hi Mark, Lynne,

Le mar 04/05/2004 ŗ 16:47, Mark Skall a ťcrit :
> >Thanks for this clarification ; for what it's worth, this is probably
> >the first time I see "extension" used in this meaning
> One more question.  Lynne and I have been looking at various W3C recs and 
> can not find the term "extensions" used in the generic way we're using 
> it.  Can you point us to some place where "extensions" are used in that way 
> and perhaps where it's defined. 

The W3C Glossary have only few matches on "extension":
"SOAP feature: An extension of the SOAP messaging framework typically
associated with the exchange of messages between communicating SOAP

Besides, using Google reveals much more matches in TR docs:
- PEP - an Extension Mechanism for HTTP
http://www.w3.org/TR/WD-http-pep-971121 (see also
http://www.w3.org/Protocols/HTTP/ietf-http-ext/ leading to

- XSLT 1.0 has an extensions framework:
"XSLT allows two kinds of extension, extension elements and extension
functions. This version of XSLT does not provide a mechanism for
defining implementations of extensions"

- Component Extension (CX) API requirements Version 1.0
has a glossary entry: "Component Extension:
        The term Component Extension (also well-known as plug-ins in Web
        browsers) refers to any software in charge of providing the
        client-side part of the Component Extension API. It is a program
        that runs as part of the Host implementation and that is not
        part of content."

- the somewhat older "PICSRules" Recommendation declares having "hooks
for expected future extensions to the PICSRules language to accommodate
signature verification."

- the WSDL 2.0 drafts have "Binding extension elements"

>  One possibility Lynne and I discussed is 
> to just use "extensibility" and not use, or define, "extensions"

I think that extensibility is indeed a better term to describe what we
want to talk about in SpecGl ; that said, given that the term
"extensions" seems to give us troubles, it would be good to have the set
of definitions that the term "extension" covers, so as to reduce the
ambiguity later on.

Dominique HazaŽl-Massieux - http://www.w3.org/People/Dom/

Received on Tuesday, 4 May 2004 11:22:10 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:40:35 UTC