# Feature Request: Metadata block in CommonMark?

**URL:** <https://talk.commonmark.org/t/feature-request-metadata-block-in-commonmark/4513>\
**Category:** Spec\
**Created:** [September 4, 2023, 8:13am UTC](https://talk.commonmark.org/t/feature-request-metadata-block-in-commonmark/4513 "2023-09-04T08:13:50Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![chrisalley](https://cdn.commonmark.org/user_avatar/talk.commonmark.org/chrisalley/32/906_2.png) [@chrisalley](https://talk.commonmark.org/u/chrisalley)\
**Post date:** [September 4, 2023, 8:00pm UTC](https://talk.commonmark.org/t/feature-request-metadata-block-in-commonmark/4513/2 "2023-09-04T20:00:33Z")

</div>

Refer to discussion here:

> [@Metadata in documents](https://talk.commonmark.org/t/metadata-in-documents/721/41):
>
> It would be good to have a list of YAML capabilities to support natively. I can see binary data being useful in certain context. Well, if you can get a list of core features that needs to be kept, then that can be a start (And maybe we can forward that to either YAML or diet-YAML team. A good yardstick could perhaps be if it can convert from/to json/json5 at the least (if I remember json is not very large of a specification). Alternative proposed name for this stripped down YAML: cYAML - Co…

---

_[View the full topic](https://talk.commonmark.org/t/feature-request-metadata-block-in-commonmark/4513)._