From: TEC <tecosaur@gmail.com>
To: Bastien <bzg@gnu.org>
Cc: hj-orgmode-1@hj.proberto.com, emacs-orgmode@gnu.org
Subject: Re: Shower thought: submit an IETF RFC to register Org as a MIME type
Date: Thu, 01 Oct 2020 11:40:23 +0800 [thread overview]
Message-ID: <87zh56fwbc.fsf@gmail.com> (raw)
In-Reply-To: <87r1qt9cf0.fsf@gnu.org>
Bastien <bzg@gnu.org> writes:
> If there is absolutely zero burden put on the shoulders of Org's
> maintainers, then I'm all for it.
From the look of things, there's just effort in the initial
creation.
>> I think it would serve well the proliferation and
>> popularization of org-mode.
>
> Agreed.
This is the main reason why I'm a fan of the idea :)
> 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.
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.
I'm hoping we could then use https://tools.ietf.org/html/rfc7763
(registration of text/markdown) as a template, where we could just
link
to the syntax specification.
Perhaps it could be worth putting the syntax spec under the main
site as
something like orgmode.org/syntax-spec.html.
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.
> Is anyone willing to move forward with this registration?
In about two months, I am.
It looks like creating and draft and then emailing it to
media-types@iana.org would probably be the best approach.
All the best,
Timothy.
next prev parent reply other threads:[~2020-10-01 3:41 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-04 14:44 TEC
2020-09-04 16:14 ` Gustav Wikström
2020-09-05 5:30 ` stardiviner
2020-09-05 5:50 ` Bastien
2020-09-05 5:53 ` TEC
2020-09-17 7:09 ` TEC
2020-09-17 7:18 ` hj-orgmode-1
2020-09-23 7:31 ` Bastien
2020-10-01 3:40 ` TEC [this message]
2020-10-01 5:21 ` Bastien
2020-10-01 5:48 ` TEC
2020-10-01 6:46 ` Bastien
2020-10-01 15:39 ` Wes Hardaker
2020-10-01 15:45 ` TEC
2020-10-06 18:03 ` Wes Hardaker
2020-10-06 19:03 ` TEC
2020-10-06 20:39 ` Palak Mathur
2020-10-24 12:09 ` Bastien
2020-10-24 12:28 ` Palak Mathur
2020-10-24 12:50 ` Bastien
2020-10-24 13:09 ` Leo Vivier
2020-10-24 13:38 ` Bastien
2020-10-24 13:49 ` Leo Vivier
2020-10-24 15:12 ` Bastien
2020-10-24 15:00 ` Palak Mathur
2020-10-24 15:40 ` Bastien
2020-10-24 15:57 ` Palak Mathur
2020-10-14 9:52 ` Lennart C. Karssen
2020-10-14 14:22 ` Nicolas Goaziou
2021-03-23 3:00 ` Timothy
2020-09-24 20:25 Andrea
2020-09-24 20:25 Andrea
2021-10-22 1:21 Carlos Pita
2021-10-23 6:45 ` Ihor Radchenko
2021-10-23 8:34 ` Carlos Pita
2021-10-23 8:36 ` Timothy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zh56fwbc.fsf@gmail.com \
--to=tecosaur@gmail.com \
--cc=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=hj-orgmode-1@hj.proberto.com \
--subject='Re: Shower thought: submit an IETF RFC to register Org as a MIME type' \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Code repositories for project(s) associated with this inbox:
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).