# Consistent attribute syntax

**URL:** <https://talk.commonmark.org/t/consistent-attribute-syntax/272>\
**Category:** Extensions\
**Created:** [September 4, 2014, 10:28am UTC](https://talk.commonmark.org/t/consistent-attribute-syntax/272 "2014-09-04T10:28:34Z")\
**Posts on this page:** 1\
**Showing post:** 123

<div class="post-metadata">

**Author:** ![aoudad](https://talk.commonmark.org/letter_avatar_proxy/v2/letter/a/b782af/32.png) [@aoudad](https://talk.commonmark.org/u/aoudad)\
**Post date:** [January 13, 2019, 9:32pm UTC](https://talk.commonmark.org/t/consistent-attribute-syntax/272/123 "2019-01-13T21:32:49Z")

</div>

> [@real\_ate](#):
>
> I have been using a custom syntax for attributes for code-blocks for quite some time now in a reasonably large app and I’m interested in making it “more standard”. Is this the right place to chip in with the discussion?

Yes, I believe it is. You could describe a syntax and invite other people here to share their thoughts.

Keep in mind, there’s already some variation (or is it fragmentation?) in attribute syntax among different Markdown flavors and other writing formats like Markua. For example…

[Pandoc](http://pandoc.org/MANUAL.html#generic-raw-attribute) / [PHP Markdown Extra](https://michelf.ca/projects/php-markdown/extra/#spe-attr) / [Earlier version of CommonMark spec](https://mb21.github.io/stmd/spec.html#extensions):

```
{#myId .myClass key=val key2="val 2"}

```

[Maruku](http://maruku.rubyforge.org) / [Kramdown](https://kramdown.gettalong.org/syntax.html#attribute-list-definitions):

```
{:ref-name: #myid .my-class}

```

[Markua](https://leanpub.com/markua/read#attributes):

```
{key_one: value1, key_two: value_two, key_three: "value three!", key_four: true, key_five: 0, key_six: 3.14}

```

---

_[View the full topic](https://talk.commonmark.org/t/consistent-attribute-syntax/272)._