IETF Logo Mail Archive

Re: [hybi] [Uri-review] ws: and wss: schemes

Kristof Zelechovski <giecrilj@stegny.2a.pl> Sat, 05 September 2009 20:23 UTC

Return-Path: <giecrilj@stegny.2a.pl>
X-Original-To: hybi@core3.amsl.com
Delivered-To: hybi@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 307663A681C; Sat, 5 Sep 2009 13:23:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.702
X-Spam-Level: **
X-Spam-Status: No, score=2.702 tagged_above=-999 required=5 tests=[AWL=-0.198, BAYES_40=-0.185, HELO_EQ_PL=1.135, HOST_EQ_PL=1.95]
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 zDCo4BHwc7dI; Sat, 5 Sep 2009 13:23:09 -0700 (PDT)
Received: from shark.2a.pl (shark.2a.pl [195.117.102.3]) by core3.amsl.com (Postfix) with ESMTP id 580383A682D; Sat, 5 Sep 2009 13:23:08 -0700 (PDT)
Received: from av.2a.pl (av.2a.pl [195.117.102.9]) by shark.2a.pl (Postfix) with ESMTP id 384602A69E7; Sat, 5 Sep 2009 21:53:45 +0200 (CEST)
X-Virus-Scanned: amavisd-new at 2a.pl
Received: from shark.2a.pl ([195.117.102.3]) by av.2a.pl (av.2a.pl [195.117.102.9]) (amavisd-new, port 10024) with ESMTP id AVPvXBShO2Kz; Sat, 5 Sep 2009 21:53:38 +0200 (CEST)
Received: from POCZTOWIEC (unknown [10.8.1.26]) by shark.2a.pl (Postfix) with ESMTPA id 56ED72A6A9C; Sat, 5 Sep 2009 21:53:38 +0200 (CEST)
From: Kristof Zelechovski <giecrilj@stegny.2a.pl>
To: 'Ian Hickson' <ian@hixie.ch>, 'URI' <uri@w3.org>, hybi@ietf.org, uri-review@ietf.org, public-i18n-core@w3.org
References: <OF22CD1320.96C55266-ON85257610.004AB599-85257610.004BC9CA@lotus.com><C9931C12-E123-437D-8E7D-F8C680C62397@mnot.net><4A8CAA72.3000209@berkeley.edu><Pine.LNX.4.62.0909040147300.6775@hixie.dreamhostps.com><4AA14792.4020009@gmx.de><4D25F22093241741BC1D0EEBC2DBB1DA01AD6282C2@EX-SEA5-D.ant.amazon.com><Pine.LNX.4.62.0909041947250.26930@hixie.dreamhostps.com><4AA17310.1090108@gmx.de><Pine.LNX.4.62.0909042013300.26930@hixie.dreamhostps.com><4AA20894.9040704@gmx.de> <Pine.LNX.4.62.0909051042290.26930@hixie.dreamhostps.com>
Date: Sat, 05 Sep 2009 21:53:54 +0200
Message-ID: <9102D21CB1354229969F7A2802F43F89@POCZTOWIEC>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
In-Reply-To: <Pine.LNX.4.62.0909051042290.26930@hixie.dreamhostps.com>
Thread-Index: AcouGzh6rsWTYmMWSCOzKtBV50z+BgARs6YQ
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
Subject: Re: [hybi] [Uri-review] ws: and wss: schemes
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Server-Initiated HTTP <hybi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hybi>
List-Post: <mailto:hybi@ietf.org>
List-Help: <mailto:hybi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 05 Sep 2009 20:23:10 -0000

Ian, you are already going out of your way to make HTML back into XML.  You
are swimming against the current.  A noble exercise, I must admit, but
hardly worth the effort in this case :-)
Cheers,
Chris

-----Original Message-----
From: uri-review-bounces@ietf.org [mailto:uri-review-bounces@ietf.org] On
Behalf Of Ian Hickson
Sent: Saturday, September 05, 2009 12:46 PM
To: URI; hybi@ietf.org; uri-review@ietf.org; public-i18n-core@w3.org
Subject: Re: [Uri-review] [hybi] ws: and wss: schemes

> The source file that you feed into xml2rfc is an XML file using the 
> RFC2629bis syntax. You control that file. Put into it what you need.

There's no such file; the XML is generated by a script and posted straight 
to the xml2rfc Web service. I have every intention of keeping this as 
automatic as possible; I already have to go out of my way to make the 
references to [WEBADDRESSES] and [HTML5] work, I really don't want to have 
to start doing the same for IETF documents when I don't actually have to.

v2.23.0 | Report a Bug | By Email