From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp0 ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms11 with LMTPS id uMfyCmtndV8sUQAA0tVLHw (envelope-from ) for ; Thu, 01 Oct 2020 05:21:47 +0000 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp0 with LMTPS id 4PPKBmtndV9VVgAA1q6Kng (envelope-from ) for ; Thu, 01 Oct 2020 05:21:47 +0000 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 8A77594042A for ; Thu, 1 Oct 2020 05:21:46 +0000 (UTC) Received: from localhost ([::1]:36758 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kNr2H-0005B9-8B for larch@yhetil.org; Thu, 01 Oct 2020 01:21:45 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:56530) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kNr1p-0005Aw-57 for emacs-orgmode@gnu.org; Thu, 01 Oct 2020 01:21:17 -0400 Received: from fencepost.gnu.org ([2001:470:142:3::e]:49017) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kNr1o-00066l-1J; Thu, 01 Oct 2020 01:21:16 -0400 Received: from [2a01:e35:2fe1:f780:3001:4ba4:f2a0:5df7] (port=57424 helo=guerry) by fencepost.gnu.org with esmtpsa (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.82) (envelope-from ) id 1kNr1n-0007F5-Kg; Thu, 01 Oct 2020 01:21:15 -0400 Received: by guerry (Postfix, from userid 1000) id B98991A60D6D; Thu, 1 Oct 2020 07:21:13 +0200 (CEST) From: Bastien To: TEC Subject: Re: Shower thought: submit an IETF RFC to register Org as a MIME type References: <871rjhha8t.fsf@gmail.com> <5f5325db.1c69fb81.53d7d.5b93@mx.google.com> <87pn70ai0t.fsf@gnu.org> <87y2log45r.fsf@gmail.com> <87sgbgg9r0.fsf@gmail.com> <09b16f10-06ea-d28c-79a9-424c6940fe56@XXXXXXXXX.XXX> <87r1qt9cf0.fsf@gnu.org> <87zh56fwbc.fsf@gmail.com> Date: Thu, 01 Oct 2020 07:21:13 +0200 In-Reply-To: <87zh56fwbc.fsf@gmail.com> (TEC's message of "Thu, 01 Oct 2020 11:40:23 +0800") Message-ID: <87362y1pyu.fsf@bzg.fr> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: emacs-orgmode@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: hj-orgmode-1@hj.proberto.com, emacs-orgmode@gnu.org Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: "Emacs-orgmode" X-Scanner: scn0 Authentication-Results: aspmx1.migadu.com; dkim=none; dmarc=pass (policy=none) header.from=gnu.org; spf=pass (aspmx1.migadu.com: domain of emacs-orgmode-bounces@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=emacs-orgmode-bounces@gnu.org X-Spam-Score: -1.51 X-TUID: ONBS7GwyrCqN Hi Timothy, TEC writes: >> Is anyone willing to check that there are no constraints? > > I've read through https://tools.ietf.org/html/rfc6838 and I couldn't > see any constraints placed on us beyond the initial registration's > requirements. You register once and for all? Is there some red tape involved in maintaining the registration? > For that, I think a formal syntax specification would be > needed. Perhaps https://orgmode.org/worg/dev/org-syntax.html will > do? It looks complete. We should first read https://orgmode.org/worg/dev/org-syntax.html and carefully check that it is up to date and still accurate, then make it more user oriented (for now it more developers oriented.) I'm ready to work on this before the end of the year. > Perhaps it could be worth putting the syntax spec under the main > site as something like orgmode.org/syntax-spec.html. I would not go into this direction: as you know, I'd like the home of orgmode.org to be just one page (index.org/html) and move other pages to Worg. So let's not move org-syntax.org to the website, it is good as a worg resource. > I've also been considering spinning off the manual into a bit of a > specification document (e.g. less of a guide / how-to, stripped down > to just the bare information), so perhaps > orgmode.org/specification.html#syntax ? I'd really like some second > opinions. This would be too many docs to maintain. >> Is anyone willing to move forward with this registration? > > In about two months, I am. Okay, thanks! Let's work on stabilizing Org syntax and reconsider the registration idea then. I will also ping future maintainers on this. Thanks, -- Bastien