Clemens Vasters clemensv

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 tro 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

Resolving Paradoxical Constraints in JSON Schema

Introduction

JSON Schema is a versatile tool for defining the structure of JSON data and ensuring its validation. However, as powerful as it is, complex scenarios can sometimes lead to paradoxical constraints, especially when used in combination with code generation tools. In this article, we'll take an in-depth look at one such paradox that emerged while defining message structures for various protocols and discuss a practical solution.

The Problem Statement

Imagine a system where messages are passed using different protocols, such as AMQP, HTTP, MQTT, Kafka, and CloudEvents. Each protocol has a distinct message structure but shares certain common attributes. These shared attributes are consolidated in a base message definition, called definition in our JSON Schema.

	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;

	I wrote the code, ChatGPT the text. I'll eventually write an actual article, but this will do:

	### Consuming and Creating (Structured, JSON) CloudEvents in Azure Stream Analytics

	Hey devs, today we're going to talk about working with structured JSON CloudEvents in Azure Stream Analytics. We'll be using some straightforward SQL-like queries to get this done, and I promise to keep the jargon to a minimum. Let's get started.

	#### Setting Up Your Event Stream

	We assume that the input is an Event Hub that multiplexes CloudEvents in structured JSON format.

	Erstelle eine neue Auto-Rundtour von 200km mit Startpunkt in Viersen mit dem Thema Wasserschlösser.

	Ermittle die Strassenadressen für jeden Wegpunkt. Gebe das Ergebnis als GPX XML Text aus, eingeschlossen von ```. Benutze Routenpunkte.

	Alle Erklärungen sollten in den Beschreibungselementen der Datei enthalten sein:
	In <name> benutze das Format {zielname}; {strasse} {hausnummer}; {postleitzahl} {ort}.
	Benutze eine aussagekräftige Beschreibung in <desc>.
	Gib die Zusammenfassung der Route in <metadata> aus.

	Antworte NUR mit dem XML Text. Achte auf die korrekten XML Namespaces.