22 NOV 2026

What's New In November

Recent updates to Lexicon Community schemas: richer app listings, event media, books, and calendar spaces

Lexicon Community
@lexicon.community


Lexicon Community lexicons have grown in several directions recently: app listings gained support for long-form descriptions, calendar events learned to carry media, and the Books working group shipped a new namespace for book data. We also introduced a first space type for calendars. As ever, the goal is practical interoperability: each addition is already in use or moving toward it.

The community made all of this possible. Thanks to the PR authors below, and to everyone who reviewed the proposals on the forum and in pull requests.

Long-form app descriptions

App listings now have room to breathe. Alongside the short description, app records can include a longDescription of up to 4,000 graphemes. That gives directories and app stores enough space to present a full listing on a detail page, rather than squeezing every explanation into a few hundred characters.

The two fields have different jobs: the short description stays concise for rails, cards, and thumbnails; the long description is where an app can explain what it does and why someone might want to use it. The result is a small schema change that gives listings more room to tell their story wherever a fuller presentation makes sense.

Media on calendar events

Calendar events can now include up to 16 images, each with an explicit display role: thumbnail, flyer, or header. Images may also include alt text and an aspect_ratio, giving publishers a way to supply useful context and giving consuming apps hints about how the media is intended to appear.

Those roles are display hints, not rigid rendering rules. A consumer can adapt a header image for a wide event page or a square thumbnail while still working from the same event record. That makes the addition useful for both full-featured event platforms and simpler use cases, like attaching a flyer to an event.

A shared home for book data

The Books working group shipped a new namespace for sharing book-related data. Its records cover editions, reviews, and catalog search and resolution, giving applications a common foundation for working across books and providers.

An edition record describes a specific publication, such as a particular printing, translation, or audiobook. A portable review record supports a rating from 1 to 20, plain-text content with optional rich content, and a spoiler flag. The namespace also includes procedures for searching and resolving entries against provider catalogs.

Shared definitions make identifiers and metadata easier to exchange. Supported identifiers include ISBN-13, ISSN, DOI, ASIN, OCLC, and LCCN. Contributor roles follow the ONIX taxonomy, alongside publisher and series metadata. Covers can be stored in-repository as blobs or represented as plain URLs in API responses.

Calendar spaces

Calendar collections introduce a shared space for events and their RSVPs. A collection can hold one event or many, with one author or several; the space authority determines who else can write to it.

Events and RSVPs remain ordinary calendar records. What changes is their address: they live in the collection rather than only under an individual author. That gives calendar apps a way to represent shared, permissioned spaces without requiring a separate kind of event or RSVP record.

Status: The collection space type is still a draft, as noted in the schema README.

What’s next

A lot is happening, and there are many ways to jump in and participate. The discussion is on the forum, our lexicon schemas are in tangled, and news and announcements go out on @lexicon.community

.

Enjoyed this article?

Join our free newsletter and never miss an update.


Related Articles