







This approach to a data commons could extend to so many typically shared things. For businesses to easily and authoritatively publish things like open hours or product catalogs, discographies, every kind of -ography... creative appmakers could do so much with all that
JB Hutch
Testing an idea that I've had for a while, but I think is even better suited for atproto Internet, meet plts.at
Jul 31, 2026 at 12:55 AM
From Albums to Streams: How Modularity Changes Systems
Scientific publishing is breaking under document-centric formats designed for a physical world. Borrowing from music’s shift from albums to streaming, we make the case that open access alone cannot deliver reuse, trust, or scale. The future of science depends on modular, interoperable research components that move across tools, enabling new workflows, tools, and ecosystems.
LinkML – Bring structure to your data.
An open framework that simplifies authoring, validating, and sharing data — providing an accessible platform for interdisciplinary collaboration and a reliable way to define and share data semantics.

Fed up with Big Tech, communities turn to data collectives for control
Data collectives and cooperatives, which let creators control the collection and distribution of their data, are emerging as preferred alternatives to big tech companies.

New to the Commons? | David Bollier
If you’re coming to the commons for the first time, it can be difficult to grok the idea because there are so many different ways to understand the commons. That’s because the commons is not so much a fixed, universal thing as a general concept describing durable, dynamic sets of social relationships for managing resources -- all sorts of resources: digital, urban, natural, indigenous, rural, cultural, scientific, to use some crude categories.
Lexicon Embeds Overview
ATProto’s inside out structure provides an opportunity for open, permissionless building on top of any component in the network, including its extensible data schema definition system, Lexicons. One of the opportunities this presents is users sharing their data and records with multiple apps. Those apps may be direct substitutions (different clients for microblogging say), or apps that use that data in a variety of ways, such as Popfeed an app which aggregates posts about a variety of media ty...

How the Open Knowledge Format can improve data sharing | Google Cloud Blog
Learn how the Open Knowledge Format helps secure data sharing and improves collaboration across teams with standardized documentation.

How the Open Knowledge Format can improve data sharing | Google Cloud Blog
Learn how the Open Knowledge Format helps secure data sharing and improves collaboration across teams with standardized documentation.

Licensing terms for data in the Atmosphere
I’d like to raise a fun and interesting topic, and that’s intellectual property and content licensing. The data that flies around the Atmosphere is all visible and public. We’re at a stage within the Atmosphere where services are beginning to grow, and we’re beginning to see lexicons and data that express creative works that extend in length beyond microblogging. I think that the Standard.site lexicons are a great example. But these creations lead to further questions. Who has permission to...

A Polycentric Governance Lens on Data Infrastructures
Funding policies for data infrastructure promote open data sharing to drive positive social impact. However, concerns regarding the long-term management of data within and across distributed infrastructures can hinder data sharing. We draw upon the concept of polycentric governance to demonstrate how collaborative practices of data curation, in preparing and maintaining data for (future) sharing, provide a solid foundation for understanding data governance within data infrastructures. Based on a qualitative case study of a distributed ecological network, we investigate the conditions under which data are managed as a shared resource by local actors to ensure the long-term (re)usability of data. We contribute to CSCW by conceptualising data curation as a complex form of governance practice with multiple centres of decision-making, each of which operates with some degree of autonomy in data infrastructures. A polycentric governance lens on data infrastructures advances the CSCW conception of data curation as a collective governance practice that can cultivate a data democracy culture within and across organisations, empower individuals to be accountable for their data, and foster a mindset shift toward decentralised data governance.

Manuscript submission systems and metadata completeness in Crossref: Patterns and associations
The importance of open research information, particularly publication metadata, is widely recognised. Crossref is one of the most important infrastructures for registering open metadata as part of DOI record registration. It is widely known, however, that the metadata of many publications is far from complete, with many publishers making certain metadata openly available, but failing to do so for other metadata elements. Publishers’ ability to register this metadata with Crossref depends on their capacity to capture and retain this data in their production workflows. Manuscript submission systems are an important, yet largely overlooked, factor in the extent to which publishers make metadata available through Crossref. In this paper, we present the results of an analysis investigating the relation between the level of metadata that publishers deposit with Crossref and the submission systems that they deploy for their journals. We have looked at the 153 publishers with the largest amounts of publications in Crossref and concentrate on the four most commonly used systems: Editorial Manager, ScholarOne, Open Journal Systems (OJS) and eJournalPress. We show that some submission systems appear better suited to capturing certain metadata elements. However, there are always cases where publishers using the same system differ widely in the level of metadata they register, suggesting that technology is not the only prohibiting factor and other considerations are at play.
Doing Data Science on the Shoulders of Giants: The Value of Open Source Software for the Data Science Community
Open source software is ubiquitous throughout data science, and enables the work of nearly every data scientist in some way or another. Open source projects, however, are disproportionately maintained by a small number of individuals, some of whom are institutionally supported, but many of whom do this maintenance on a purely volunteer basis. The health of the data science ecosystem depends on the support of open source projects, on an individual and institutional level.

From Personal Data Server to Personal Metadata Server - Liccium
Liccium builds the fundamental infrastructure that enables creators and rightsholders to publish machine-readable declarations about their digital works that…
Knowledge sharing: Why smart creatives build in public
Knowledge sharing: Why smart creatives build in public
There are a lot of architectural bits, but if I had to pick one design feature it's Lexicons. Lexicons allow for new shared data types and structures in a way that are immediately available on network for any other service provider to adopt. Getting shared agreement in ActivityPub is hard.
Pedro Vezza
Why did you decide to bet on atproto over Mastodon or similar?
I've been thinking about the beauty of open data and how the AT Protocol and wider Atmosphere ecosystem has been recapturing that open data environment that once defined the web. It really does feel special. vale.rocks/posts/atproto-ethos #atproto #ATProtocol
The AT Protocol Harkens An Old Web Ethos
vale.rocksSomeone recently announced a “restaurant listings/menus on atproto so they can own their own data”, and as someone who used to do engineering for OpenTable, let me tell you that project is not solving a problem that restaurants actually have. Owning your own data is an anti-value prop for many orgs.
dame
hard pill to swallow for atproto developers/creators: 99% of potential users either do not care about, value, understand, or want to “own their own data” i see so many apps/projects lead with this “value prop”, but it’s not an important or meaningful consideration for most people