Re: [link-relations] An Internet Draft template for writing a Link Relation specification

Tim Williams <williamstw@gmail.com> Tue, 07 December 2010 02:35 UTC

Return-Path: <williamstw@gmail.com>
X-Original-To: link-relations@core3.amsl.com
Delivered-To: link-relations@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 475E928C0CF for <link-relations@core3.amsl.com>; Mon, 6 Dec 2010 18:35:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.977
X-Spam-Level:
X-Spam-Status: No, score=-9.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_HI=-8]
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 fWm+1YD8MkV0 for <link-relations@core3.amsl.com>; Mon, 6 Dec 2010 18:35:02 -0800 (PST)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by core3.amsl.com (Postfix) with ESMTP id E1B2B3A68E7 for <link-relations@ietf.org>; Mon, 6 Dec 2010 18:35:01 -0800 (PST)
Received: by yxt33 with SMTP id 33so3081269yxt.31 for <link-relations@ietf.org>; Mon, 06 Dec 2010 18:36:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=aNtuO3T0d4CxBEQK51oUIzIEMACX8N43lnPxW+kbVmQ=; b=pLQHDrD8MGl2nmCcrL0Y0PUy6qhhnuakgmOR0Bnoa0Uyb/okyxp+kwn2x0dJ+XHwVs mL3SzSXonh5WxgMnooJfUQYH+aoE19LeZFnbUXlFu1RJ8+scHXFeEQeSTZEPCBg/oPu6 1VZ/2Iqv1aib70GZax0aFIini89TB1nO98KlE=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=LfaoX0svilvbvQwvCzL8SxYK8B5aCApTkNWdFx9cVg264MiwpI1eqUALN+0ju+CQM+ XsrM6cWKhMDzgMNr1aq0tmCtLqOW0FnfgFGN1tWi2vKAFmSgi9Rr3Lc1+T3T9uUkzjed /T8PSJSH0dclN7dg8SuiPlnYbVWt8NUlteKHo=
MIME-Version: 1.0
Received: by 10.150.146.17 with SMTP id t17mr857641ybd.31.1291689385894; Mon, 06 Dec 2010 18:36:25 -0800 (PST)
Received: by 10.151.150.2 with HTTP; Mon, 6 Dec 2010 18:36:25 -0800 (PST)
In-Reply-To: <4CFBAC1D.5090604@gmx.de>
References: <4CFBAC1D.5090604@gmx.de>
Date: Mon, 06 Dec 2010 21:36:25 -0500
Message-ID: <AANLkTim6kvzLLDEDdOD5gsXO9Vwag1Jbb8_VpqqpyiYp@mail.gmail.com>
From: Tim Williams <williamstw@gmail.com>
To: Julian Reschke <julian.reschke@gmx.de>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: link-relations@ietf.org
Subject: Re: [link-relations] An Internet Draft template for writing a Link Relation specification
X-BeenThere: link-relations@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <link-relations.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/link-relations>, <mailto:link-relations-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/link-relations>
List-Post: <mailto:link-relations@ietf.org>
List-Help: <mailto:link-relations-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/link-relations>, <mailto:link-relations-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Dec 2010 02:35:02 -0000

Thanks for this Julian, this seems much more approachable.  I'm
curious about process with these.

I gather there's two things that need to occur:  1) an Informational
RFC through the Independent Submission process and 2) A mail here to
ask for it to be added to the registry.

What's the process for getting these reviewed/discussing prior to 1?
Would it be appropriate to turn this mailing-list into a place for
discussing candidate link relation types - with an appropriate subject
label (e.g. [PROPOSAL])?  Or is it typical to just submit it directly
to through the form?

Thanks,
--tim

On Sun, Dec 5, 2010 at 10:13 AM, Julian Reschke <julian.reschke@gmx.de> wrote:
> Hi,
>
> to make it easier to write an Internet Draft defining a Link Relation (with
> the goal of publishing as RFC), I have created a small template.
>
> It uses the RFC2629-syntax, as consumed by xml2rfc.tcl (web service at
> xml.resource.org) and rfc2629.xslt
> (<http://greenbytes.de/tech/webdav/rfc2629xslt/rfc2629xslt.html>). (*)
>
> Additional material:
>
> Slides created by the RFC Production Center:
> <ftp://ftp.rfc-editor.org/in-notes/rfc-editor/lifecycle79.pdf> and
> <ftp://ftp.rfc-editor.org/in-notes/rfc-editor/tutorial.latest.pdf>
>
> "Guidelines to Authors of Internet-Drafts":
> <http://www.ietf.org/id-info/guidelines.html>
>
> Feedback about the template appreciated...
>
> Julian
>
> (*) For RFC2629/xml2rfc related questions, the best place to start is
> <http://lists.xml.resource.org/mailman/listinfo/xml2rfc>; feel free to cc me
> on questions.
>