New issue: RFC Language for Copy Operations in Section 8.4.2

["Monica J. Martin" <Monica.Martin@Sun.COM>]

Background: Several times in our discussions (such as for Issue 270), we identified that normative language was required in several places in Section 8.4.2, Replacement Logic for Copy Operations.  In order to lessen the amount of changes required and circumvent having to handle each individually, a normative statement has been proposed for the introduction of this section. A typographical error also needs to be corrected (comma as shown in submitter's proposal).

Section 8.4.2, Replacement Logic for Copy Operations

Submitter's proposal:
Change from:
This section provides rules for replacing data referenced by the to-spec in a <copy> operation. Detailed examples are provided in Appendix C.  Examples of Replacement Logic.

Change to:
This section provides rules for replacing data referenced by the to-spec in a <copy> operation. These rules MUST be followed unless otherwise explicitly stated. Detailed examples are provided in Appendix C, Examples of Replacement Logic.

Note:

   1. Either 'followed' or 'used' are equally appropriate.
   2. MAY and MUST NOT exist in this section so these are otherwise
      specified explicitly.