Repository navigation
source namespace: support different source (raw) formats #8
Description
Hello,
I was reading the http://source.scripting.com/ and my understanding is that presently this namespace cannot be used for non-Markdown sources (e.g. ReStructured Text, AsciiDoc or other). A possible alternative would be to have instead of source:markdown a source:raw (or some other name) element with a required attribute (format or possibly type) to denote the format. I'm thinking the attribute values could be either a simple string (markdown, asciidocto, rst) or possibly even the registered MIME type (if any) of the raw content.
Activity
scripting commentedon Nov 16, 2022
@Oblomov -- the <source:markdown> element is designed to move markdown text around. but there's absolutely nothing preventing anyone from creating another namespace for other data types. At this stage I can't change it without breaking my own and possibly other people's applications.
Oblomov commentedon Nov 17, 2022
The
source:markdownelement could still be kept for backward compatibility (possibly specifying the equivalence between it and the correspondingsource:raw format="text/markdown"or whatever).