.svg){kind=icon}
email
An open protocol enabling communication and interoperability between opaque agentic applications.
One of the biggest challenges in enterprise AI adoption is getting agents built on different frameworks and vendors to work together. That’s why we created an open Agent2Agent (A2A) protocol, a collaborative way to help agents across different ecosystems communicate with each other.
A framework for securing software update systems.
The Update Framework (TUF) maintains the security of software update systems, providing protection even against attackers that compromise the repository or signing keys. TUF provides a flexible framework and specification that developers can adopt into any software update system.
Related contents:
SimpleFIN (also SFIN) stands for Simple Financial Interchange and makes read-only financial interchange simple. It’s like RSS for financial information.
SimpleFIN is like a window on a safe: it lets people look at, but not touch your financial information. And you control who can look through the window!
The FinOps Open Cost and Usage Specification (FOCUS
) is an open-source specification that defines clear requirements for billing data generators to produce consistent cost and usage datasets.
Related contents:
We are uncovering a new way of building software by embracing AI, iteration, and human intuition.
The agents.json Specification is an open specification that formally describes contracts for API and agent interactions, built on top of the OpenAPI standard.
MessagePack is an extremely efficient object serialization library. It's like JSON, but very fast and small.
It's like JSON. but fast and small.
MessagePack is an efficient binary serialization format. It lets you exchange data among multiple languages like JSON. But it's faster and smaller. Small integers are encoded into a single byte, and typical short strings require only one extra byte in addition to the strings themselves.
Related contents:
Welcome to the open source Citation Style Language (CSL) project! Our goal is to facilitate scholarly publishing by automating the formatting of citations and bibliographies. We develop the Citation Style Language and maintain a crowdsourced repository with over 10,000 free CSL citation styles.
An open protocol to allow secure authorization in a simple and standard method from web, mobile and desktop applications.
Related contents:
I think all technical writers, at some point or another, feel the urge to base their work on something more systematic than “it’s just the way folks documented stuff since forever”. Toolkits and frameworks provide content types, which is immensely valuable when you know what you want to write, but starting from there is like buying a hammer without knowing that half of the work you’ll do is turning screws. As I find the lack of deeper conversation around this topic rather unsettling, I decided to contribute some verses.
Romantic Versioning Specification.
You are given a version number HUMAN . MAJOR . MINOR, increment the:
- HUMAN version when you make any conceptual change, major rewrite, major documentation change, or any other change which requires additional HUMAN involvement.
- MAJOR version when you make incompatible API changes,
- MINOR version when you add functionality in a backward-compatible manner or fix with backward-compatible bug fixes.
In an ideal world, I would wish SemVer to have 4 numbers: EPOCH.MAJOR.MINOR.PATCH. The EPOCH version is for those big announcements, while MAJOR is for technical incompatible API changes that might not be significant. This way, we can have a more granular way to communicate changes. Similarly, we also have Romantic Versioning that propose HUMAN.MAJOR.MINOR.
Architectural methodology for frontend projects.
Feature-Sliced Design (FSD) is an architectural methodology for scaffolding front-end applications. Simply put, it's a compilation of rules and conventions on organizing code. The main purpose of this methodology is to make the project more understandable and structured in the face of ever-changing business requirements.
Source: Architectures of modern Front-end applications @ BRACKETS' Medium.
This page describes the JSON Lines text format, also called newline-delimited JSON. JSON Lines is a convenient format for storing structured data that may be processed one record at a time. It works well with unix-style text processing tools and shell pipelines. It's a great format for log files. It's also a flexible format for passing messages between cooperating processes.
Protect Payment Data with Industry-driven Security Standards, Training, and Programs.
BSON, short for Binary JSON, is a binary-encoded serialization of JSON-like documents. Like JSON, BSON supports the embedding of documents and arrays within other documents and arrays. BSON also contains extensions that allow representation of data types that are not part of the JSON spec. For example, BSON has a Date type and a BinData type.
Plus Codes are like street addresses for people or places that don’t have one. Instead of addresses with street names and numbers, Plus Codes are based on latitude and longitude, and displayed as numbers and letters. With a Plus Code, people can receive deliveries, access emergency and social services, or just help other people find them.
Don’t let your friends dump git logs into changelogs.
A changelog is a file which contains a curated, chronologically ordered list of notable changes for each version of a project.
A new API for podcast synchronization.
The Open Podcast API is an initiative aiming to provide a feature-complete synchronization API specification for podcast (web) apps and user-focused servers.
TypeSchema is a JSON specification to describe data models.
TypeSchema is a JSON format to describe data models in a language neutral format. A TypeSchema specification can be easily transformed into code for almost any programming language. This helps to reuse core data models in different environments.