emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
* Shower thought: submit an IETF RFC to register Org as a MIME type
@ 2020-09-04 14:44 TEC
  2020-09-04 16:14 ` Gustav Wikström
                   ` (2 more replies)
  0 siblings, 3 replies; 43+ messages in thread
From: TEC @ 2020-09-04 14:44 UTC (permalink / raw)
  To: org-mode-email


Hi everyone,

Prompted by the fact that Markdown is registered as a MIME type
(RFC7763) and perusing the MIME registration procedure (RFC6838),
I wonder if it may be possible to register Org as a MIME type?

There are a few parts of RFC6838 in particular which give me hope, 
such
as:
> [§4.9] universal support and implementation of a media type are 
> NOT a
> requirement for registration.

I'm guessing the main barrier wold be a the lack of a published
specification --- I'm guessing a complete version of
https://orgmode.org/worg/dev/org-syntax.html published under the 
main
site (i.e. https://orgmode.org/standard.html) would be required.

Looking for other uses of the .org extension, there doesn't seem 
to be
much. The main result is from "Lotus Organiser", which seems to be 
a
(discontinued) PIM from IBM which used .org as its file type in 
the 1992
release. Other than that it seems that Yamaha and SoundBlaster 
have used
it as an extension for organ audio samples.

If it does seem possible to have text/org formally added as a mime 
type,
I would love to push this.

Please let me know what you think.

All the best,

Timothy.


^ permalink raw reply	[flat|nested] 43+ messages in thread
* Re: Shower thought: submit an IETF RFC to register Org as a MIME type
@ 2020-09-24 20:25 Andrea
  0 siblings, 0 replies; 43+ messages in thread
From: Andrea @ 2020-09-24 20:25 UTC (permalink / raw)
  To: bzg; +Cc: hj-orgmode-1, emacs-orgmode, tecosaur

Hi,

What are the pros?

About the cons: maybe we need to look more into the requirements.

I am looking at https://tools.ietf.org/html/rfc2048 and the one that
concerns me a little is 2.2.6: I guess somebody would need to write a
bit of docs about security concerns. Or you can go the way Markdown did
it: from https://tools.ietf.org/html/rfc7763#section-2

"Security considerations:

      Markdown interpreted as plain text is relatively harmless.  A text
      editor need only display the text.  The editor SHOULD take care to
      handle control characters appropriately and to limit the effect of
      the Markdown to the text-editing area itself; malicious Unicode-
      based Markdown could, for example, surreptitiously change the
      directionality of the text.  An editor for normal text would
      already take these control characters into consideration, however.

      Markdown interpreted as a precursor to other formats, such as
      HTML, carries all of the security considerations as the target
      formats.  For example, HTML can contain instructions to execute
      scripts, redirect the user to other web pages, download remote
      content, and upload personally identifiable information.  Markdown
      also can contain islands of formal markup, such as HTML.  These
      islands of formal markup may be passed as they are, transformed,
      or ignored (perhaps because the islands are conditional or
      incompatible) when the Markdown is processed.  Since Markdown may
      have different interpretations depending on the tool and the
      environment, a better approach is to analyze (and sanitize or
      block) the output markup, rather than attempting to analyze the
      Markdown.
"

Do they have an org-babel?

Thanks,

Andrea


^ permalink raw reply	[flat|nested] 43+ messages in thread
* Re: Shower thought: submit an IETF RFC to register Org as a MIME type
@ 2020-09-24 20:25 Andrea
  0 siblings, 0 replies; 43+ messages in thread
From: Andrea @ 2020-09-24 20:25 UTC (permalink / raw)
  To: bzg; +Cc: hj-orgmode-1, emacs-orgmode, tecosaur

Hi,

What are the pros?

About the cons: maybe we need to look more into the requirements.

I am looking at https://tools.ietf.org/html/rfc2048 and the one that
concerns me a little is 2.2.6: I guess somebody would need to write a
bit of docs about security concerns. Or you can go the way Markdown did
it: from https://tools.ietf.org/html/rfc7763#section-2

"Security considerations:

      Markdown interpreted as plain text is relatively harmless.  A text
      editor need only display the text.  The editor SHOULD take care to
      handle control characters appropriately and to limit the effect of
      the Markdown to the text-editing area itself; malicious Unicode-
      based Markdown could, for example, surreptitiously change the
      directionality of the text.  An editor for normal text would
      already take these control characters into consideration, however.

      Markdown interpreted as a precursor to other formats, such as
      HTML, carries all of the security considerations as the target
      formats.  For example, HTML can contain instructions to execute
      scripts, redirect the user to other web pages, download remote
      content, and upload personally identifiable information.  Markdown
      also can contain islands of formal markup, such as HTML.  These
      islands of formal markup may be passed as they are, transformed,
      or ignored (perhaps because the islands are conditional or
      incompatible) when the Markdown is processed.  Since Markdown may
      have different interpretations depending on the tool and the
      environment, a better approach is to analyze (and sanitize or
      block) the output markup, rather than attempting to analyze the
      Markdown.
"

Do they have an org-babel?

Thanks,

Andrea


^ permalink raw reply	[flat|nested] 43+ messages in thread
* Re: Shower thought: submit an IETF RFC to register Org as a MIME type
@ 2021-10-22  1:21 Carlos Pita
  2021-10-23  6:45 ` Ihor Radchenko
  0 siblings, 1 reply; 43+ messages in thread
From: Carlos Pita @ 2021-10-22  1:21 UTC (permalink / raw)
  To: emacs-orgmode

Hi,

in https://list.orgmode.org/87tuuw3n15.fsf@nicolasgoaziou.fr/#t it's stated:

> Org is standardized on lower case. Uppercase is used in the manual as
> a poor man's bold, and supported for historical reasons.

But C-c C-x p still inserts stuff like:

   :PROPERTIES:
   :ARCHIVE:  ...
   :END:

Maybe it should be updated or maybe I don't fully understand the
convention, perhaps it's just for blocks?

But then c-a-p is very lenient since it lists lower and upper case block
variants even when I typed a lower case prefix, and upper case usually
will go first in the list, hence promoting a seemingly bad practice.

Can you clarify?

Thank you in advance,
Carlos




^ permalink raw reply	[flat|nested] 43+ messages in thread

end of thread, other threads:[~2022-10-21 11:49 UTC | newest]

Thread overview: 43+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-09-04 14:44 Shower thought: submit an IETF RFC to register Org as a MIME type 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
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
2022-10-17 20:46         ` Org-mode syntax as a tool-independent MIME type (was: Shower thought: submit an IETF RFC to register Org as a MIME type) Karl Voit
2022-10-18  1:55           ` Timothy
2022-10-18  7:22             ` Org-mode syntax as a tool-independent MIME type Bastien
2022-10-18  8:13               ` Karl Voit
2022-10-21 11:44                 ` Ihor Radchenko
2022-10-18  8:05             ` Karl Voit
2022-10-21 11:41           ` Org-mode syntax as a tool-independent MIME type (was: Shower thought: submit an IETF RFC to register Org as a MIME type) Ihor Radchenko
2021-03-23  3:00 ` Shower thought: submit an IETF RFC to register Org as a MIME type Timothy
  -- strict thread matches above, loose matches on Subject: below --
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

Code repositories for project(s) associated with this public 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).