That’s not an option for those of us using Markdown to export to other formats like TeX as well.
Also, as I said above:
Finally, Kramdown, Pandoc and MarkdownExtra already have some kind of attribute syntax and as described in the draft:
[Attributes] don’t need to be implemented to conform to this spec. However, if an implementation includes [attributes], this spec strongly recommends to implement the syntax described here.
P.S. Just discovered another use case:
Instead of:
[quote="mb21, post:1, topic:272"]
quoted text
[/quote]
which this forum currently uses for quoting other posts, we could use standardized attributes:
> quoted text
{quote=mb21 post=1 topic=272}
Which is more readable and markdown-like? My point is that there will always be people that want markdown with a little cusomized extra functionality (like e.g. in this forum). Attributes enable this in a uniform way that should soon be familiar to the more advanced users that need it (if it isn’t already) and will reduce the need for many custom extensions like the [quote][\/quote]
-syntax (which I can’t seem to properly escape in an inline code span).