Re: [precis] WGLC: draft-ietf-precis-framework-09.txt

Peter Saint-Andre <stpeter@stpeter.im> Thu, 10 October 2013 23:36 UTC

Return-Path: <stpeter@stpeter.im>
X-Original-To: precis@ietfa.amsl.com
Delivered-To: precis@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C89A011E817E for <precis@ietfa.amsl.com>; Thu, 10 Oct 2013 16:36:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.273
X-Spam-Level:
X-Spam-Status: No, score=-102.273 tagged_above=-999 required=5 tests=[AWL=0.326, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Zlr8-30c8qKC for <precis@ietfa.amsl.com>; Thu, 10 Oct 2013 16:36:05 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id BE3E111E8177 for <precis@ietf.org>; Thu, 10 Oct 2013 16:36:05 -0700 (PDT)
Received: from ergon.local (unknown [71.237.13.154]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id EFD654100F; Thu, 10 Oct 2013 17:42:06 -0600 (MDT)
Message-ID: <525739E3.8030201@stpeter.im>
Date: Thu, 10 Oct 2013 17:36:03 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Andrew Sullivan <ajs@anvilwalrusden.com>
References: <20130828154603.a94201dea74f29229b4767b2@jprs.co.jp> <20131005030751.GB38902@mx1.yitter.info> <5254C12F.90708@stpeter.im> <20131009042358.GB47597@mx1.yitter.info>
In-Reply-To: <20131009042358.GB47597@mx1.yitter.info>
X-Enigmail-Version: 1.5.2
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: precis@ietf.org
Subject: Re: [precis] WGLC: draft-ietf-precis-framework-09.txt
X-BeenThere: precis@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Preparation and Comparison of Internationalized Strings <precis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/precis>, <mailto:precis-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/precis>
List-Post: <mailto:precis@ietf.org>
List-Help: <mailto:precis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/precis>, <mailto:precis-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Oct 2013 23:36:10 -0000

On 10/8/13 10:23 PM, Andrew Sullivan wrote:

>>> clear how useful such a class would be.  In any case, because of the
>>> ability to subclass FreeformClass, a protocol needing something more
>>> particular is always able to create it."  I don't really care about
>>> this; it was just something that struck me on the way by.
>> OK, I will try to find better wording, or just reuse what you've sent.
> 
> It could be that, with your other proposal (in another thread) about
> getting rid of subclassing and making it all use profiles, this point
> will find a more natural expression.

How's this?

   Future specifications might define additional PRECIS string classes
   (e.g., a class that falls somewhere between the IdentifierClass and
   the FreeformClass).  At this time, it is not clear how useful such a
   class would be.  In any case, because application developers are able
   to define profiles of PRECIS string classes, a protocol needing a
   construct between the IdentiferClass and the FreeformClass could of
   course define a restricted profile of the FreeformClass if needed.

Peter

-- 
Peter Saint-Andre
https://stpeter.im/