On 2015/03/03 06:53, Peter Saint-Andre - &yet wrote:
On 3/2/15 12:20 PM, John C Klensin wrote:

--On Monday, March 02, 2015 09:21 -0700 Peter Saint-Andre - &yet
<[email protected]> wrote:


We had some discussion months ago (IIRC occasioned by comments
from John Klensin) about citing a particular version when
necessary (e.g., 3.2 or 6.3 or 7.0) but otherwise having a
generic pointer to the Unicode Standard when we're talking
about the technology in general, rather than a particular
version.

This is of course exactly the right thing to do. W3C does the same, and it's even called out in the Character Model spec (see http://www.w3.org/TR/charmod/#C063).


I have heard back from the RFC Editor and they note that several recent
RFCs use this as a citation:

    [UNICODE]  The Unicode Consortium, "The Unicode Standard",
               <http://www.unicode.org/versions/latest/>.

I think that works fine in most instances.

Yes indeed.

I do have a question about how to handle pointers to particular
chapters, such as:

        using Unicode Default Case Folding as defined in Chapter 3
        of the Unicode Standard [UNICODE]

As John notes, chapter numbers might change. If we want to provide a
pointer to a particular chapter, we could modify such text like so:

        using Unicode Default Case Folding as defined in the Unicode
        Standard [UNICODE] (at the time of this writing, the algorithm
        is specified in Chapter 3 of [UNICODE7.0])

However, I'm not sure if we really need to point to a particular chapter
in a particular version.

Yes. If we do, I suggest two things:

- Make the section number more specific, if possible (in the case at hand, it would be section 3.13).

- Make the text shorter, if possible:
         using Unicode Default Case Folding as defined in the Unicode
         Standard [UNICODE] (e.g. Chapter 3.13 of [UNICODE7.0])

But in many cases, it is necessary to look at more than one chapter, so it may be better to not give just one exact pointer.

Regards,    Martin.

_______________________________________________
precis mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/precis

Reply via email to