On Tue, 25 Jan 2005 14:37:56 -0500, Robert Sayre [EMAIL PROTECTED]
wrote:
Asbjørn, I can sympathize with the goal, but it's not appropriate to
include in the spec. It's babysitting.
I kind of agree.
If the mythical Implementor's Guide were to materialize, it might make a
good home for this
It reads like more of a guideline than a Pace. Inspecting the format
for conformance to these guidelines and generating Paces for
non-conformances seems like a better way to proceed than to actually
add this text to the spec.
-joe
On Mon, 24 Jan 2005 16:17:36 -0800, Tim Bray [EMAIL
On Jan 24, 2005, at 5:02 PM, Joe Gregorio wrote:
It reads like more of a guideline than a Pace. Inspecting the format
for conformance to these guidelines and generating Paces for
non-conformances seems like a better way to proceed than to actually
add this text to the spec.
Actually, take a
On Mon, 24 Jan 2005 17:08:45 -0800, Tim Bray [EMAIL PROTECTED] wrote:
On Jan 24, 2005, at 5:02 PM, Joe Gregorio wrote:
It reads like more of a guideline than a Pace. Inspecting the format
for conformance to these guidelines and generating Paces for
non-conformances seems like a better
Joe Gregorio wrote:
On Mon, 24 Jan 2005 17:08:45 -0800, Tim Bray [EMAIL PROTECTED] wrote:
On Jan 24, 2005, at 5:02 PM, Joe Gregorio wrote:
It reads like more of a guideline than a Pace. Inspecting the format
for conformance to these guidelines and generating Paces for
non-conformances seems like
7.2 Common element usage
The following actual elements should only be used in the ways
specified below.
* link: Purposes of link elements are specified by a list of legal
values for link/@rel, and we are considering allowing extensions to
specify additional values. If the external
