IETF Logo Mail Archive

Re: [Tools-discuss] RESTful API style guide

Nico Williams <nico@cryptonector.com> Wed, 19 June 2013 16:51 UTC

Return-Path: <nico@cryptonector.com>
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0601421F9D56 for <tools-discuss@ietfa.amsl.com>; Wed, 19 Jun 2013 09:51:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.957
X-Spam-Level:
X-Spam-Status: No, score=-1.957 tagged_above=-999 required=5 tests=[AWL=0.020, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
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 QVEySGqUitDV for <tools-discuss@ietfa.amsl.com>; Wed, 19 Jun 2013 09:51:49 -0700 (PDT)
Received: from homiemail-a32.g.dreamhost.com (caiajhbdcaib.dreamhost.com [208.97.132.81]) by ietfa.amsl.com (Postfix) with ESMTP id 2EB5521F9406 for <tools-discuss@ietf.org>; Wed, 19 Jun 2013 09:51:49 -0700 (PDT)
Received: from homiemail-a32.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a32.g.dreamhost.com (Postfix) with ESMTP id 290B3584071 for <tools-discuss@ietf.org>; Wed, 19 Jun 2013 09:51:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h= mime-version:in-reply-to:references:date:message-id:subject:from :to:cc:content-type; s=cryptonector.com; bh=11mxCwO4tYolfvi6N6Yz gfXZT7k=; b=gol+EpGF/IDCcXaeA7o3yENbottAx8424qXQ+lGupgXgQKnk8bDO XYRVN9EJ21SbM3SErMbEa0h88LzDJekuTs0wV/h29UB4/oli+xtKYm6XE4g/WyJl SmyWXfpHt0WIT8eYuFGIJc0JxHj5WC7HRBPzWOUjNZzjGFW0qnXx3Ys=
Received: from mail-we0-f170.google.com (mail-we0-f170.google.com [74.125.82.170]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a32.g.dreamhost.com (Postfix) with ESMTPSA id C3746584065 for <tools-discuss@ietf.org>; Wed, 19 Jun 2013 09:51:45 -0700 (PDT)
Received: by mail-we0-f170.google.com with SMTP id w57so4725507wes.29 for <tools-discuss@ietf.org>; Wed, 19 Jun 2013 09:51:42 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=gYywIIGQd5ITDPkrt2sela5b02F77mMyw28E5qL0+s4=; b=Fye5sx2v8L2AH2qoEkoi5MyPPbo4HMMsrTZ9AxxQHADk2m6OjVkRt1QGb4UiZIgMKr 8JQ3cJJ3wO+hJmBfjXc6cYJMqi30vZ47QzoagVo+V/RxGsTar1ICkpG2lGGNSA3QPt5S zskmhqno6q8WygwPeDSR8M1PRmAFZH5SmbSWIo7X3Kh7ywlFNkgE2LY6vt8AXJK7oJ6i VH7g0EDFyGn7ImDgSvGJo9gyaobxNZol/ICrCM4ul1GLugldO8lPFBKSl0JlnsNTL73c RbpDio5paWpKbcxp2bh/nq7GToGZ1jQC7DFqZ+JTZ+qN8PGkkzxSfS4c0uPx17spDWQb aXHA==
MIME-Version: 1.0
X-Received: by 10.181.12.1 with SMTP id em1mr1696374wid.4.1371660702932; Wed, 19 Jun 2013 09:51:42 -0700 (PDT)
Received: by 10.216.29.5 with HTTP; Wed, 19 Jun 2013 09:51:42 -0700 (PDT)
In-Reply-To: <21266.1371520672@sandelman.ca>
References: <21266.1371520672@sandelman.ca>
Date: Wed, 19 Jun 2013 11:51:42 -0500
Message-ID: <CAK3OfOhZGc8d5NCxXDUNA2UZ3qg=Xtzw1r9rRZucyq2Y-YHsrg@mail.gmail.com>
From: Nico Williams <nico@cryptonector.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Content-Type: text/plain; charset="UTF-8"
Cc: tools-discuss@ietf.org
Subject: Re: [Tools-discuss] RESTful API style guide
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tools-discuss>
List-Post: <mailto:tools-discuss@ietf.org>
List-Help: <mailto:tools-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Jun 2013 16:51:54 -0000

On Mon, Jun 17, 2013 at 8:57 PM, Michael Richardson
<mcr+ietf@sandelman.ca> wrote:
> I'm writing it in markdown, although I found that neither the perl nor python
> markdown converter seems to deal properly with code samples indented by 4
> spaces.  Any suggestions on a better tool chain?

Might lyx2rfc work for you?  https://github.com/nicowilliams/lyx2rfc

v2.23.0 | Report a Bug | By Email