Clemens Vasters clemensv

JSON Structure for OpenAPI 3.2

A Companion Specification

This is an unofficial companion specification. It is not published or endorsed by the OpenAPI Initiative or the JSON Structure project. It adds no fields to the OpenAPI Specification; it defines how JSON Structure is used within the Schema Object dialect mechanism that OpenAPI Specification 3.2.0 already provides. Read it alongside OAS 3.2.0, which remains authoritative for everything it does not modify.

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 RFC2119 RFC8174 when, and only when, they appear in all capitals, as shown here.

This document is licensed under [The Apache License, Version

Auffällige Follow-Muster auf Bluesky: Vier deutsche Accounts im Datenvergleich

Stand: Mai 2026 · Datenquelle: Bluesky-Firehose (letzte 7 Tage) + Bluesky-API · Methodik: siehe Abschnitt 8

For a bit of CNCF xRegistry magic:

curl -o docker-compose-gh.yml https://raw.githubusercontent.com/xregistry/xrproxy/main/docker-compose-gh.yml
docker compose -f docker-compose-gh.yml up

After a little while (give it a couple minutes to settle after the images have been pulled), you'll get a metadata viewer at http://localhost:8080/viewer and an xRegistry API endpoint at http://localhost:8080/registry

What are you looking at? The viewer shows our test registry at xregistry.soaphub.org with endpoints and messages and schemas, but it also shows other metadata that illustrates why we call the registry "extensible":

Unified Namespace and xRegistry at Contoso Autowerks

This article describes how Contoso Autowerks uses a Unified Namespace (UNS), captured formally in an CNCF xRegistry, to integrate its manufacturing systems.

Mind that this is a fictional example to illustrate the concepts of a Unified Namespace and how CNCF xRegistry can be used to capture the metadata of the namespace.

Contoso Autowerks Factory Layout & Work Cells

dump1090 Real-Time Signal Statistics

This project provides a web application for real-time monitoring of ADS-B messages using dump1090. The application consists of a FastAPI backend and a frontend that displays various statistics in real-time using Chart.js.

I don't have time to package this up at the moment.

Features

Message Rate Statistics: Computes and displays message rates over different intervals (5s, 15s, 30s, 60s, 300s).
Signal Strength Statistics: Computes and displays minimum, maximum, and average signal strength over 30 seconds.

Content was moved

Apache Avro Schema - Formal Specification

Abstract

This document provides a comprehensive specification of the schema definition system used by Apache Avro. It details the structure and syntax of Avro

"Plain JSON" encoding for Apache Avro

April 2024, by Clemens Vasters, Microsoft Corp.

Notational Conventions
Interoperability issues of the Avro JSON Encoding with common JSON usage
The "Plain JSON" encoding

The Apache Avro project defines a JSON Encoding, which is optimized for encoding data in JSON, but primarily aimed at exchanging data between implementations of

	Sub RevertSafeLinks()
	Dim objMail As MailItem
	Dim objInspector As Inspector
	Dim objInlineResponse As Object

	' Check for inline response first
	Set objInlineResponse = Application.ActiveExplorer.ActiveInlineResponse
	If Not objInlineResponse Is Nothing Then
	Set objMail = objInlineResponse
	ProcessMailItem objMail


	// This code was auto-generated by xRegistry CLI


	#nullable enable

	using System;
	using System.IO;
	using System.Text.RegularExpressions;
	using System.Threading.Tasks;