
From derhoermi@gmx.net  Thu Mar 12 17:01:40 2009
Return-Path: <derhoermi@gmx.net>
X-Original-To: collation@core3.amsl.com
Delivered-To: collation@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9320E3A69F4 for <collation@core3.amsl.com>; Thu, 12 Mar 2009 17:01:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level: 
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[BAYES_50=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wiAfWohpQA3C for <collation@core3.amsl.com>; Thu, 12 Mar 2009 17:01:39 -0700 (PDT)
Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by core3.amsl.com (Postfix) with SMTP id 41D043A692F for <collation@ietf.org>; Thu, 12 Mar 2009 17:01:38 -0700 (PDT)
Received: (qmail invoked by alias); 13 Mar 2009 00:02:15 -0000
Received: from dslb-088-075-233-054.pools.arcor-ip.net (EHLO hive) [88.75.233.54] by mail.gmx.net (mp027) with SMTP; 13 Mar 2009 01:02:15 +0100
X-Authenticated: #723575
X-Provags-ID: V01U2FsdGVkX1+KypBvUjWK9j6JhiCt8vtgBGg0fNZOGZxsPvM+ZT KHVebgDhIQmz+j
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: collation@ietf.org
Subject: RFC 4790 code point collation identifier
Date: Fri, 13 Mar 2009 01:02:19 +0100
Message-ID: <rb8jr4h5bes498mtbk1maclmkbdfrc3abh@hive.bjoern.hoehrmann.de>
X-Mailer: Forte Agent 3.3/32.846
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Y-GMX-Trusted: 0
X-FuHaFi: 0.75
Cc: www-international@w3.org
X-BeenThere: collation@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Collation registration and discussion \(see RFC 4790\)" <collation.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/collation>, <mailto:collation-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/collation>
List-Post: <mailto:collation@ietf.org>
List-Help: <mailto:collation-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/collation>, <mailto:collation-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Mar 2009 00:01:40 -0000

Hi,

  I am interested in having a collation identifier as per RFC 4790 for
the Unicode code point collation as more or less defined in the XQ
Functions and Operators specification. It does not seem that there is
an Internet-Draft or other attempt at specifying it. Did I miss some-
thing? What would a specification say for the validity operation?

Thanks,
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ 

From arnt@oryx.com  Fri Mar 13 01:38:21 2009
Return-Path: <arnt@oryx.com>
X-Original-To: collation@core3.amsl.com
Delivered-To: collation@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EF3883A689E for <collation@core3.amsl.com>; Fri, 13 Mar 2009 01:38:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8SfwSgFhQIQj for <collation@core3.amsl.com>; Fri, 13 Mar 2009 01:38:14 -0700 (PDT)
Received: from kalyani.oryx.com (kalyani.oryx.com [195.30.37.30]) by core3.amsl.com (Postfix) with ESMTP id 41B373A6891 for <collation@ietf.org>; Fri, 13 Mar 2009 01:38:13 -0700 (PDT)
Received: from kalyani.oryx.com (localhost.oryx.com [127.0.0.1]) by kalyani.oryx.com (Postfix) with ESMTP id 9F8C44AC59; Fri, 13 Mar 2009 09:38:47 +0100 (CET)
Received: from arnt@oryx.com (HELO lochnagar.oryx.com) by kalyani.oryx.com (Archiveopteryx 3.1.0) with esmtp id 1236933526-87767-1/6/43 (3 recipients); Fri, 13 Mar 2009 09:38:46 +0100
Message-Id: <IkeeTWscmdhSPrs/s0A93g.md5@lochnagar.oryx.com>
Date: Fri, 13 Mar 2009 09:37:25 +0100
From: Arnt Gulbrandsen <arnt@oryx.com>
To: Bjoern Hoehrmann <derhoermi@gmx.net>
Subject: Re: RFC 4790 code point collation identifier
References: <rb8jr4h5bes498mtbk1maclmkbdfrc3abh@hive.bjoern.hoehrmann.de>
In-Reply-To: <rb8jr4h5bes498mtbk1maclmkbdfrc3abh@hive.bjoern.hoehrmann.de>
Content-Type: text/plain; format=flowed
Mime-Version: 1.0
Cc: www-international@w3.org, collation@ietf.org
X-BeenThere: collation@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Collation registration and discussion \(see RFC 4790\)" <collation.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/collation>, <mailto:collation-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/collation>
List-Post: <mailto:collation@ietf.org>
List-Help: <mailto:collation-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/collation>, <mailto:collation-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Mar 2009 08:38:22 -0000

Bjoern Hoehrmann writes:
> I am interested in having a collation identifier as per RFC 4790 for 
> the Unicode code point collation as more or less defined in the XQ 
> Functions and Operators specification.

OK.

> It does not seem that there is an Internet-Draft or other attempt at 
> specifying it. Did I miss some- thing?

Perhaps RFC 5051. At a superficial glance, it and the the default 
collation described in XQ 7.3.1 look equivalent.

There has been an attempt to define the Unicode Collation Algorithm 
(also mentioned in 7.3.1) in RFC terms. Not duplicating it, just naming 
things so that the algorithm can be used in RFCs.

That document landed in my lap after a while. If you care I could finish 
it. There isn't much left to do. (I didn't finish it until now for a 
variety of reasons. Mostly blah health blah priority blah.)

> What would a specification say for the validity operation?

Depends on which collation you mean.

Arnt

From derhoermi@gmx.net  Fri Mar 13 08:49:13 2009
Return-Path: <derhoermi@gmx.net>
X-Original-To: collation@core3.amsl.com
Delivered-To: collation@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F3A413A6B2D for <collation@core3.amsl.com>; Fri, 13 Mar 2009 08:49:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_15=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zN0III0TmbhV for <collation@core3.amsl.com>; Fri, 13 Mar 2009 08:49:05 -0700 (PDT)
Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by core3.amsl.com (Postfix) with SMTP id C3ACD3A687E for <collation@ietf.org>; Fri, 13 Mar 2009 08:49:01 -0700 (PDT)
Received: (qmail invoked by alias); 13 Mar 2009 15:49:39 -0000
Received: from dslb-092-078-028-181.pools.arcor-ip.net (EHLO hive) [92.78.28.181] by mail.gmx.net (mp069) with SMTP; 13 Mar 2009 16:49:39 +0100
X-Authenticated: #723575
X-Provags-ID: V01U2FsdGVkX18U5nZEzgMUBqQlAbqpPEjzYgOLOR2LPa5EJnQZdL 6ve1i86LL/Jsls
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: Arnt Gulbrandsen <arnt@oryx.com>
Subject: Re: RFC 4790 code point collation identifier
Date: Fri, 13 Mar 2009 16:49:43 +0100
Message-ID: <uivkr45ijt77m95rfgpnc9rigu2kjpuepv@hive.bjoern.hoehrmann.de>
References: <rb8jr4h5bes498mtbk1maclmkbdfrc3abh@hive.bjoern.hoehrmann.de> <IkeeTWscmdhSPrs/s0A93g.md5@lochnagar.oryx.com>
In-Reply-To: <IkeeTWscmdhSPrs/s0A93g.md5@lochnagar.oryx.com>
X-Mailer: Forte Agent 3.3/32.846
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Y-GMX-Trusted: 0
X-FuHaFi: 0.66
Cc: www-international@w3.org, collation@ietf.org
X-BeenThere: collation@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Collation registration and discussion \(see RFC 4790\)" <collation.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/collation>, <mailto:collation-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/collation>
List-Post: <mailto:collation@ietf.org>
List-Help: <mailto:collation-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/collation>, <mailto:collation-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Mar 2009 15:49:13 -0000

* Arnt Gulbrandsen wrote:
>Perhaps RFC 5051. At a superficial glance, it and the the default 
>collation described in XQ 7.3.1 look equivalent.

As I understand it, i;unicode-casemap performs case conversion and some
normalization and then compares the result. What I am looking for, and
what I think the default collation is, is strict Unicode identity. Put
simply, represent both strings as UTF-8 sequences and apply i;octet.

>That document landed in my lap after a while. If you care I could finish 
>it. There isn't much left to do. (I didn't finish it until now for a 
>variety of reasons. Mostly blah health blah priority blah.)

I found that draft and think it would be nice if it was finished, but
there is no hurry, from my perspective, to finish it.
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ 

From derhoermi@gmx.net  Fri Mar 13 16:49:32 2009
Return-Path: <derhoermi@gmx.net>
X-Original-To: collation@core3.amsl.com
Delivered-To: collation@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6B99928C207 for <collation@core3.amsl.com>; Fri, 13 Mar 2009 16:49:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=0.300,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 96v5VrNPDB6g for <collation@core3.amsl.com>; Fri, 13 Mar 2009 16:49:31 -0700 (PDT)
Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by core3.amsl.com (Postfix) with SMTP id 041B23A6B6E for <collation@ietf.org>; Fri, 13 Mar 2009 16:49:30 -0700 (PDT)
Received: (qmail invoked by alias); 13 Mar 2009 23:50:07 -0000
Received: from dslb-092-078-028-181.pools.arcor-ip.net (EHLO hive) [92.78.28.181] by mail.gmx.net (mp070) with SMTP; 14 Mar 2009 00:50:07 +0100
X-Authenticated: #723575
X-Provags-ID: V01U2FsdGVkX19CdfE2GjJCVR8ZyjPBzJwgZll1JfJX1nLkFEdZPL ufWUJetBjMR4Ng
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: Bjoern Hoehrmann <derhoermi@gmx.net>
Subject: Re: RFC 4790 code point collation identifier
Date: Sat, 14 Mar 2009 00:50:12 +0100
Message-ID: <r0slr4phld2bpf9lqrlu96igalj2ca1ffp@hive.bjoern.hoehrmann.de>
References: <rb8jr4h5bes498mtbk1maclmkbdfrc3abh@hive.bjoern.hoehrmann.de>
In-Reply-To: <rb8jr4h5bes498mtbk1maclmkbdfrc3abh@hive.bjoern.hoehrmann.de>
X-Mailer: Forte Agent 3.3/32.846
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Y-GMX-Trusted: 0
X-FuHaFi: 0.72
Cc: www-international@w3.org, collation@ietf.org
X-BeenThere: collation@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Collation registration and discussion \(see RFC 4790\)" <collation.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/collation>, <mailto:collation-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/collation>
List-Post: <mailto:collation@ietf.org>
List-Help: <mailto:collation-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/collation>, <mailto:collation-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Mar 2009 23:49:32 -0000

* Bjoern Hoehrmann wrote:
>  I am interested in having a collation identifier as per RFC 4790 for
>the Unicode code point collation as more or less defined in the XQ
>Functions and Operators specification. It does not seem that there is
>an Internet-Draft or other attempt at specifying it. Did I miss some-
>thing? What would a specification say for the validity operation?

I am considering to post the following Internet-Draft when publication
resumes and would appreciate comments, particularily on identifier and
title:

  http://www.websitedev.de/ietf/draft-hoehrmann-id-collation-00.txt

regards,
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ 
