From bf30fd9bd44d196b6e508964da76d3c294b93a44 Mon Sep 17 00:00:00 2001 From: Aljoscha Meyer Date: Tue, 16 Jan 2024 23:39:26 +0100 Subject: [PATCH] Reference me --- willowtest/specs/encodings.ts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/willowtest/specs/encodings.ts b/willowtest/specs/encodings.ts index 85a3596..f3d3c16 100644 --- a/willowtest/specs/encodings.ts +++ b/willowtest/specs/encodings.ts @@ -131,7 +131,7 @@ export const encodings: Expression = site_template({ pinformative( "A perhaps curious feature of the Willow data model is that its specifications rarely talk about encodings. ", - sidenote("We", ["Let’s be honest: ", em("Aljoscha")]), + sidenote("We", ["Let’s be honest: ", r("Aljoscha")]), " strongly believe that specifications should concern themselves with purely logical data types as long as possible, treating encodings as a minor and ultimately interchangeable detail. When specifications define concepts in terms of their encodings, results usually end up miserably underspecified (see ", link("JSON", "https://en.wikipedia.org/wiki/JSON#Interoperability"), ") or full of incidental complexity (see ", link("XML", "https://en.wikipedia.org/wiki/XML"), ").", ),