W3C home > Mailing lists > Public > www-qa@w3.org > October 2002

Re: Defining "public interfaces" in specifications

From: Thomas B. Passin <tpassin@comcast.net>
Date: Sat, 26 Oct 2002 10:43:11 -0400
To: www-qa@w3.org
Message-id: <002801c27cfe$02045150$fe193044@tbp1>

[Eric van der Vlist]
> If that had been the case, other specs such as XPath 1.0 could have
> refered to "the latest definition of a XML Name" instead of nominatively
> quote "the current definition of a XML Name in XML 1.0".

Including  specs by reference is good, but including the "current version"
by reference is onerous and even dangerous.  Should the referenced spec get
changed, entirely out of your control, your product is suddenly
non-conforming.  It would be impossible to know what really is supported or
how a processor should work, since it might or might not have been brought
up to the new standard.

In practically all US government specs, you will see other documents
included by reference, by always qualified by the phrase "of the exact issue
specified".  That is how it should be.


Tom P
Received on Saturday, 26 October 2002 10:42:36 UTC

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