| LinkML Quarterly Newsletter: June 2026 |
|
| |
|
| The LinkML meta-model and the LinkML runtime are in sync. Both are at version 1.11.1. |
|
| |
|
| LinkML v1.11.1 (Release Notes) --- Highlights: New TypeDB, C++ header, and SQL-validation generators, SQLAlchemy 2.x code generation, and broad generator fixes plus SchemaView/pythongen performance work. Note: linkml-lint is now stricter about metamodel types. |
|
| |
|
| LinkML-Map v0.5.2 (Release Notes) --- Highlights: Heavy development toward the next release: cross-table join resolution, multi-file spec loading, semantic spec validation as a CLI pre-flight, and sentinel-to-null value mapping. New v0.5.3-rc1 is out; please test! |
|
Schema Automator v0.5.4 (Release Notes) --- Highlights: Heavy development toward the next release: a canonical data dictionary format spec, Frictionless Table Schema and dbGaP variable digest adapters, and a reusable schema-driven XML loader. |
|
| |
|
| LinkML Reference Validator v0.2.0 (Release Notes) --- Highlights: Expanded into a plugin-based framework spanning Crossref/DOI, Entrez (GEO, BioProject, BioSample), ClinicalTrials.gov, and DataCite, with automated repair mode and fuzzy-match suggestions. |
|
| |
|
| LinkML Java v0.1.2 (Release Notes) --- Highlights: Now split into a low-level linkml-core and a higher-level linkml-ext with a full LinkML metamodel representation; the latest release adds refined-inherited-slot support. |
|
Rust LinkML Core v0.4.0 (Release Notes) --- Highlights: v0.4.0 syncs the bundled metamodel to LinkML 1.11.0 and adds streaming RDF/TTL import-export with optional disk spill, for converting huge datasets without running out of memory. |
|
| |
|
| Notable removals in linkml 1.11.1 |
|
| |
|
| There were no hard removals in Linkml 1.11.1. However, linkml-lint now behaves more stringently: Bare scalar values for multivalued slots are no longer accepted. Slots like comments, notes, in_subset, see_also, aliases, and the *_mappings family must now be written as YAML lists. deprecated as a bare boolean is no longer accepted — it's a string carrying the reason for deprecation. Use a quoted value (e.g. deprecated: "true") if you have no reason to give. Non-string examples.value is no longer accepted. examples.value must be a string; mappings, numbers, booleans, and nested objects belong under examples.object. The linkml-lint --validate step is no longer a separate option — metamodel validation now always runs automatically before linting.
|
|
| |
|
| Formalisation of Contributor Hierarchy and CODEOWNERs policy The LinkML project has merged a new contributor governance framework (PR #3395) that formalizes how the open-source community is organized and how code ownership works going forward.
The change introduces a four-tier contributor hierarchy: Community contributor Collaborator Core developer Admin
Alongside this, a .github/CODEOWNERS file has been seeded, designating specific maintainers for key parts of the codebase. For most users this won't change day-to-day usage. PRs touching actively-stewarded areas will now get routed to subject-matter experts automatically, which should mean faster, higher-quality reviews. Areas without a declared owner continue to work exactly as before and a one-month fallback ensures PRs don't get blocked if a CODEOWNER is unavailable.
If you're a regular contributor or thinking about becoming one, the new docs (contributor-hierarchy.md and codeowners.md) are worth a read, and the path to claiming ownership of a module you maintain is now clearly spelled out.
|
|
| |
|
| 3648 How should a mapping to RDF 1.2 be defined? 3647 Proposed Principle: Avoid generator-specific schema rewrites 3482 Virtual LinkML community workshop — gauging interest 3478 LinkML editor web app 3586 RO-Crate profile validation with LinkML — anyone got a full stack working?
|
|
| |
|
| The LinkML Community is the heart of this project! None of this would be possible without your contributions, questions, and enthusiasm. We're so grateful for every one of you. Here's a look at what we accomplished together in March through May 2026. Pull Requests: 176 created, 124 merged, 41 authors, 28 distinct reviewers Issues: 181 created, 127 closed Contributors: 71 unique contributors
|
|
| |
|
| Join the LinkML community for regular sessions featuring presentations on LinkML applications, best practices, and community projects. The community meeting is hosted on the third Thursday of the month 8:00 AM PT / 3:00 PM UTC.
The next community meetings will be held on: July 16, 2026 August 20, 2026 September 17, 2026
Here are some of the recent community talks: Introducing PLUGIN and why we fell in love with LinkML (YouTube) Community Discussion: RareLink/REDCap + LinkML (YouTube) AI Atlas Nexus: A System for Managing AI Risks with LinkML (YouTube) TypeDB: the Natural Backend for LinkML?…a presentation about philosophical and practical alignments (YouTube)
If you are interested in presenting at a community meeting, please reach out to Sarah Gehrke via Slack or sa...@tislab.org.
Find more information including links to previous sessions and how to join future meetings here: https://linkml.io/linkml/get-involved/Community-Meetings.html |
|
| |
|
| Linked Data Modeling Language (LinkML) development is supported by the Community and CZI 313291/Z/24/Z.
For questions, make an issue at github.com/linkml/linkml/issues |
|
| |
|
|
|
