Change series name and set clearer title - crispbyte.dev-content.git@e3cc679

commit: e3cc679
parent: 0761669
author: cheddar
date: 2025-04-18 17:38:39 +0200 CEST

Change series name and set clearer title

6 files changed, +7, -7

M content/blog/2024-01-07-01-SDBD.md

M content/blog/2024-01-07-02-Semantics.md

M content/blog/2024-01-07-03-Data_Format.md

M content/blog/2024-01-09-01-Building_A_Proof_of_Concept.md

M content/blog/2024-01-09-02-The_Heart_of_the_Code.md

M content/blog/2024-01-09-03-Improvements.md

M content/blog/2024-01-07-01-SDBD.md

+1, -1

1@@ -2,7 +2,7 @@
2 date: 2024-01-07
3 title: Let's Create a Data Format
4 series:
5-  name: SDBD - Creating a Data Format
6+  name: "SDBD: Creating a Data Format"
7   number: 1
8 ---
9 I have a problem. I want to be able to transfer self-contained binary data with metadata through a variety of protocols with no knowledge of the binary data's format or the protocol being used for transfer.

M content/blog/2024-01-07-02-Semantics.md

+1, -1

1@@ -2,7 +2,7 @@
2 date: 2024-01-07
3 title: Semantics of SDBD
4 series:
5-  name: SDBD - Creating a Data Format
6+  name: "SDBD: Creating a Data Format"
7   number: 2
8 ---
9 To really start bringing this new data format to life, we need to talk about what's in it. Establishing the semantics of a format gives us the terms and concepts we need to talk about the format abstractly before we get to any concrete details.

M content/blog/2024-01-07-03-Data_Format.md

+1, -1

1@@ -2,7 +2,7 @@
2 date: 2024-01-07
3 title: What Does SDBD Actually Look Like?
4 series:
5-  name: SDBD - Creating a Data Format
6+  name: "SDBD: Creating a Data Format"
7   number: 3
8 ---
9 To turn the semantics into a real file format, we need to define what they look like as actual data. How do you write an SDBD to a stream or a disk? How do we turn our HTTP-like semantics into a real document? That question almost answers itself. I'll keep stealing from HTTP.

M content/blog/2024-01-09-01-Building_A_Proof_of_Concept.md

+1, -1

1@@ -2,7 +2,7 @@
2 date: 2024-01-09
3 title: Building a Proof of Concept
4 series:
5-  name: SDBD - Creating a Data Format
6+  name: "SDBD: Creating a Data Format"
7   number: 4
8 ---
9 The format certainly looks sound. Could there be any surprises when we try to implement it? There's one way to find out. I'll write a Proof of Concept. Finally, we get to the code!

M content/blog/2024-01-09-02-The_Heart_of_the_Code.md

+1, -1

1@@ -2,7 +2,7 @@
2 date: 2024-01-09
3 title: The Heart of the Code
4 series:
5-  name: SDBD - Creating a Data Format
6+  name: "SDBD: Creating a Data Format"
7   number: 5
8 ---
9 To complete the proof of concept we need to implement `SDBD.ICodec`. This is what we're proving after all. The most complicated part will be the HPACK encoding. I'd rather not implement that myself, not for something basic. Fortunately there is a NuGet package that should do the trick. It's called simply `hpack`.

M content/blog/2024-01-09-03-Improvements.md

+2, -2

 1@@ -1,8 +1,8 @@
 2 ---
 3 date: 2024-01-09
 4-title: Improvements
 5+title: Improvements to SDBD
 6 series:
 7-  name: SDBD - Creating a Data Format
 8+  name: "SDBD: Creating a Data Format"
 9   number: 6
10 ---
11 ## Format