W3C home > Mailing lists > Public > xml-names-editor@w3.org > January 2001

comma after i.e.

From: Michael McCaleb <mccaleb@eeel.nist.gov>
Date: Thu, 4 Jan 2001 09:57:09 -0500
Message-Id: <v02130504b67a3f7d26b5@[129.6.185.17]>
To: xml-names-editor@w3.org
Dear XML-names editor,

Below is a comment on the Namespaces in XML (14-January-1999 Edition). I
hope this is useful.


Sincerely,

Mike McCaleb

----------------------------------

Problem:

In regard to transitional expressions, "The Gregg Reference Manual" (Sixth
Edition) states:

  "Use a comma after the transition when it occurs at the start of the
   second clause... However, no comma is needed after hence, then, thus,
   so, and yet unless a pause is wanted at that point."

However, several place within the transitional expression "i.e." is not
followed by a comma.



Proposed Solution:

Change the following sentence in appendix A.1:

  In the computing disciplines, the term "namespace" conventionally
  refers to a set of names, i.e. a collection containing no duplicates.

to

  In the computing disciplines, the term "namespace" conventionally
  refers to a set of names, i.e., a collection containing no duplicates.



Change the following sentence in appendix A.2:

  In order to support the goal of making both qualified and unqualified
  names useful in meeting their intended purpose, we identify the names
  appearing in an XML namespace as belonging to one of several disjoint
  traditional (i.e. set-structured) namespaces, called namespace
  partitions.

to

  In order to support the goal of making both qualified and unqualified
  names useful in meeting their intended purpose, we identify the names
  appearing in an XML namespace as belonging to one of several disjoint
  traditional (i.e., set-structured) namespaces, called namespace
  partitions.



Change the following sentence in appendix A.4:

  The constraint expressed by "5.3 Uniqueness of Attributes" above may
  straightforwardly be implemented by requiring that no element have two
  attributes whose expanded names are equivalent, i.e. have the same
  attribute-value pairs.

to

  The constraint expressed by "5.3 Uniqueness of Attributes" above may
  straightforwardly be implemented by requiring that no element have two
  attributes whose expanded names are equivalent, i.e., have the same
  attribute-value pairs.
Received on Thursday, 4 January 2001 09:55:20 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 19:56:48 UTC