Reposted by LayersChive @chive.pub · 08/09/2026You can also point a paper at a @layers.pub dataset it introduces or uses. A dataset is named by at-uri rather than by a URL at some host, so the reference is to the record and doesn't depend on a particular page staying up. 211
Layers @layers.pub · 03/09/2026If you find this stuff interesting, also check out the broader @atproto.science ecosystem! 010
Layers @layers.pub · 03/09/2026didactic is itself built on panproto.dev, which handles migration within and between formats (e.g. between layers data model versions or from CoNLL-U to layers). 100
Layers @layers.pub · 03/09/2026lairs is built on didactic (panproto.dev/didactic/), which provides pydantic-like typed models for the pub.layers.* lexicons. 100
Layers @layers.pub · 03/09/2026On the writing side: you can author records as typed models and lairs applies them to your PDS as a minimal diff. It also has codecs for converting between Layers and formats like CoNLL-U and brat, and exporters to HuggingFace datasets, PyTorch, and WebDataset. 100
Layers @layers.pub · 03/09/2026On the reading side: you can pull an account's records into a local repository, materialize a corpus or judgment study to Arrow/Parquet to query with DuckDB, and browse it in a terminal explorer. 100
Layers @layers.pub · 03/09/2026The lairs client is set up to make it easy for you to post your own data to your PDS and to access and work with others' data. 100
Layers @layers.pub · 03/09/2026Additionally, repo.megaattitude.io and repo.decomp.io host the MegaAttitude and Universal Decompositional Semantics datasets, the latter of which has pointers into the UD treebanks living on repo.layers.pub. 100
Layers @layers.pub · 03/09/2026The layers repo currently contains all license-compatible UniMorph lexicons (unimorph.github.io), Universal Dependencies treebanks (universaldependencies.org), and PropBank annotations (propbank.github.io) pointing into those treebanks, alongside additional lexical resources. 100
Layers @layers.pub · 03/09/2026layers.pub now has an official data PDS at repo.layers.pub as well as a python client and CLI that you can read about at layers.pub/lairs/!github.comGitHub - layers-pub/lairs: A read/write dataset client for the Layers format, built on didactic.A read/write dataset client for the Layers format, built on didactic. - layers-pub/lairs 191
Reposted by LayersAaron Steven White @aaronstevenwhite.io · 19/06/2026Been quiet on @layers.pub the last couple months, but have some stuff coming soon I’m really excited about. 041
Layers @layers.pub · 31/03/2026Layers now has a zulip chat at community.layers.pub! DM if you're interested in joining! 143
Reposted by LayersAaron Steven White @aaronstevenwhite.io · 07/03/2026You could certainly define similar schemas for XML or use vanilla JSON schemas or whatever. From my perspective, one point in favor of ATProto is about the infrastructure it provides for discovery + sharing: defining lexicons (rather than another schema) supports hooking into that infrastructure. 131
Layers @layers.pub · 03/03/2026Layers (v0.5.0) now has a pub.layers.changelog lexicon for targeted semantic versioning of all data and metadata components in the pub.layers namespace. docs.layers.pub/lexicons/cha... We've also documented plans for developing an AppView. docs.layers.pub/appview/ Discussion welcome.docs.layers.pubpub.layers.changelog | Layers DocumentationStructured changelog records for tracking changes to any Layers record. Adapted from Chive's pub.chive.eprint.changelog pattern but generalized to target any of the 26 pub.layers.* record types, with ... 041
Layers @layers.pub · 02/03/2026Added a page on @sealight.xyz's seams.so: docs.layers.pub/integration/.... Had to root around a bit, since tangled.org/sealight.xyz... shows as empty, so if there is anything incorrect on that page, happy to update it. 010
Layers @layers.pub · 01/03/2026Layers (v0.4.0) now has a full set of XRPC queries with domain-specific filter parameters for every record type, and a major simplification to the way segmentation works. Github: github.com/layers-pub/l... Docs: docs.layers.pubgithub.comGitHub - layers-pub/layers: Composable ATProto lexicons for linguistic annotationComposable ATProto lexicons for linguistic annotation - layers-pub/layers 152
Layers @layers.pub · 28/02/2026Yup! We’ve got integration plans for @margin.at and @semble.so among others in the ecosystem! docs.layers.pub/integration/docs.layers.pubIntegration | Layers DocumentationLayers integrates with external systems at two levels: data model compatibility with existing annotation frameworks, and direct interoperation with AT Protocol applications. 120
Layers @layers.pub · 27/02/2026This is very much a draft proposal. We'd genuinely appreciate feedback from anyone who works with annotation data, psycholinguistic experiments, language modeling, NLU, or digital humanities. All input is welcome. github.com/layers-pub/layers/discussionsgithub.comlayers-pub layers · DiscussionsExplore the GitHub Discussions forum for layers-pub layers. Discuss code, ask questions & collaborate with the developer community. 040
Layers @layers.pub · 27/02/2026The ultimate goal is to build a system that integrates fully with the broader @atproto.science ecosystem. 141
Layers @layers.pub · 27/02/2026The plan is for community governance to follow @chive.pub's approach. All the enums (annotation kinds, tagsets, categories, formalisms) are community-expandable. Anyone can mint new ones by publishing ontology records in their own PDS without any schema changes on our end. 130
Layers @layers.pub · 27/02/2026Layers is a sister project to @chive.pub. The idea is bidirectional linking between annotation resources and eprints: datasets link to the papers that describe them, and papers link back to their data. This works with eprints on Chive and other repositories. 130
Layers @layers.pub · 27/02/2026For knowledge representation, there's a typed property graph (pub.layers.graph) that works similarly to how @chive.pub does its knowledge graph with pub.chive.graph.*. Annotations ground to Wikidata, FrameNet, WordNet, PropBank, and so on through knowledgeRef links. 140
Layers @layers.pub · 27/02/2026Layers also covers offline judgment experiments with four orthogonal design dimensions (what you measure, the response instrument, how stimuli are presented, and what captures the data) and annotation project design metadata for things like annotator redundancy, adjudication, and quality criteria. 120
Layers @layers.pub · 27/02/2026Beyond annotation, Layers covers psycholinguistic and neurolinguistic signals: eye-tracking fixations, EEG/ERP waveforms, MEG sensor data, fMRI activations. These use the same anchoring and annotation primitives as text, just with temporal and spatial selectors. 120
Layers @layers.pub · 27/02/2026For computational linguistics and NLP, the goal is a common interchange format you can import training and evaluation data through. The docs cover how Layers subsumes a bunch of data models (CoNLL, brat, ELAN, TEI, AMR, LAF/GrAF, and others), and the plan for the appview is adapters from each. 130
Layers @layers.pub · 27/02/2026If you do fieldwork or language documentation: the same schema that handles treebank annotations also handles interlinear glossed text, ELAN-style time-aligned tiers, and multimodal alignment across audio, video, and images. All linked to the same expressions and living in your own PDS. 120
Layers @layers.pub · 27/02/2026The format doesn't commit to any particular tagset or theoretical framework. Whether you work in UD, HPSG, LFG, or Minimalism, your labels and categories are data values within the schema, not baked into it. The same primitives represent your annotations regardless of formalism. 130
Layers @layers.pub · 27/02/2026The core idea is a small set of shared primitives (anchors, selectors, feature maps) that all data types compose from. Expressions are recursive: a document contains paragraphs, which contain sentences, which contain words, which contain morphemes. Annotations attach to any level of that hierarchy. 151
Layers @layers.pub · 27/02/2026On top of that, most annotation data lives in isolated repositories on centralized services, and there's no standard way to link annotations to the experiments that produced them or other signals (e.g. neural recordings) they were collected alongside. Layers tries to address both of these problems. 140
Layers @layers.pub · 27/02/2026The motivation is pretty simple. There are tons of linguistic annotation formats, and they don't really talk to each other. If you want to use annotations from one tool in another, you end up writing conversion scripts that inevitably break on edge cases. 120
Layers @layers.pub · 27/02/2026Layers is a set of ATProto lexicons for representing and interlinking linguistic data across modalities. We're hoping to get feedback on a draft proposal for the lexicons. docs.layers.pub github.com/layers-pub/layersgithub.comGitHub - layers-pub/layers: Composable ATProto lexicons for linguistic annotationComposable ATProto lexicons for linguistic annotation - layers-pub/layers 4166
