JSON::...taData(3pm)

💅 NAME

okay bestie, so like — JSON::Schema::Modern::Vocabulary::MetaData is literally the implementation of the JSON Schema Meta-Data vocabulary. That's it. That's the whole vibe. ✨

This is a perl manual page (a 3pm one, if you're keeping track), and yes it's from the User Contributed Perl Documentation, and yes you're gonna read the whole thing with me, no skipping 🫶

---

🌸 VERSION

version 0.642

so like, the version numbers here just go up one at a time, linearly, forever. no cap. it's giving "I just increment the counter and go to bed." please do not read anything into the version being less than 1.0 — no meaning should be presumed or inferred from that. it means nothing. it's just a number. lowkey iconic of her to say so.

---

🦋 DESCRIPTION

This is the implementation of the JSON Schema Draft 2020-12 "Meta-Data" vocabulary. You can spot it in metaschemas by the URI

https://json-schema.org/draft/2020-12/vocab/meta-data

and it's formally specified right here 👉 <https://json-schema.org/draft/2020-12/json-schema-validation.html#section-9>

But wait, there's more (there's always more, bestie), because support is ALSO provided for:

• the equivalent Draft 2019-09 keywords, indicated in metaschemas with the URI https://json-schema.org/draft/2019-09/vocab/meta-data and formally specified in <https://datatracker.ietf.org/doc/html/draft-handrews-json-schema-validation-02#section-9>.
• the equivalent Draft 7 keywords that correspond to this vocabulary and are formally specified in <https://datatracker.ietf.org/doc/html/draft-handrews-json-schema-validation-01#section-10>.
• the equivalent Draft 6 keywords that correspond to this vocabulary and are formally specified in <https://json-schema.org/draft-06/draft-wright-json-schema-validation-01#rfc.section.7>.
• the equivalent Draft 4 keywords that correspond to this vocabulary and are formally specified in <https://json-schema.org/draft-04/draft-fge-json-schema-validation-00#rfc.section.6>.

like. four whole drafts of backwards compatibility?? she's serving range. the way this module just handles everyone's old schemas with grace and zero drama 🎀

---

💖 GIVING THANKS

If you found this module useful — and bestie, if you're here, you probably did — please show your appreciation by:

• adding a +1 in MetaCPAN <https://metacpan.org/dist/JSON-Schema-Modern>
• and a star in GitHub <https://github.com/karenetheridge/JSON-Schema-Modern>

it costs you nothing and it means everything to the maintainer. literally the cheapest act of kindness in open source. do it. i'm not asking 🙈✨

---

🔥 SUPPORT

Bugs? bestie, bugs are a thing that happen, no one's mad. Submit them through <https://github.com/karenetheridge/JSON-Schema-Modern/issues>.

She's also usually active on irc, as ether at irc.perl.org and irc.libera.chat. so if you wanna chat, she's there. Ctrl+C out of your terminal and go say hi 💜

You can also find her on the JSON Schema Slack server <https://json-schema.slack.com> and the OpenAPI Slack server <https://open-api.slack.com> — which are also great resources for finding help, in case irc isn't your thing. pick your platform, she's got you covered fr fr.

---

👑

Karen Etheridge <ether@cpan.org>

---

🌈 COPYRIGHT AND LICENCE

This software is copyright (c) 2020 by Karen Etheridge.

This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself. slay.

Some schema files have their own licence, in share/LICENSE. (yes, individual files with their own lil licences. check before you assume. iykyk.)

---

and that's the whole page, bestie!! you read all of it and i'm so proud of you 🥹💖

this delightful little document was rendered by perl v5.40.1 on 2026-07-31, and it's page JSON::...taData(3pm) from the User Contributed Perl Documentation. go write some schemas, my main character. periodt. 💅👑✨