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

Mark Nottingham <mnot@mnot.net> Tue, 07 December 2010 02:58 UTC

Return-Path: <mnot@mnot.net>
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 3987F3A68ED for <link-relations@core3.amsl.com>; Mon, 6 Dec 2010 18:58:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.683
X-Spam-Level:
X-Spam-Status: No, score=-104.683 tagged_above=-999 required=5 tests=[AWL=-2.084, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 UKg6g7yDokZ0 for <link-relations@core3.amsl.com>; Mon, 6 Dec 2010 18:58:14 -0800 (PST)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by core3.amsl.com (Postfix) with ESMTP id 8ACFA3A68E5 for <link-relations@ietf.org>; Mon, 6 Dec 2010 18:58:14 -0800 (PST)
Received: from chancetrain-lm.mnot.net (unknown [118.209.2.20]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 1B11C22E257; Mon, 6 Dec 2010 21:59:36 -0500 (EST)
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset="us-ascii"
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <AANLkTim6kvzLLDEDdOD5gsXO9Vwag1Jbb8_VpqqpyiYp@mail.gmail.com>
Date: Tue, 07 Dec 2010 13:59:33 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <E6BA6AB7-A2CA-4B97-A7AF-5916064BE2E8@mnot.net>
References: <4CFBAC1D.5090604@gmx.de> <AANLkTim6kvzLLDEDdOD5gsXO9Vwag1Jbb8_VpqqpyiYp@mail.gmail.com>
To: Tim Williams <williamstw@gmail.com>
X-Mailer: Apple Mail (2.1082)
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:58:16 -0000

We're happy to give advice about what makes a good relation, specification text, etc. here, and asking for that advice early on, rather than last minute, is much preferred. :) 

Generally, though, the discussion of a relation itself should probably happen within the community that's appropriate to it -- whether that's HTML5, uFormats, RDF, etc. We will try to get the right people involved if something starts here, of course, but it's easier when the community hammers out the basics ahead of time, so we're not minting things that aren't connected to running code.

Cheers,


On 07/12/2010, at 1:36 PM, Tim Williams wrote:

> 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.
>> 
> _______________________________________________
> link-relations mailing list
> link-relations@ietf.org
> https://www.ietf.org/mailman/listinfo/link-relations

--
Mark Nottingham   http://www.mnot.net/