You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: shows/apidays-paris/index.md
+24-11Lines changed: 24 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,11 +16,12 @@ December 11, 2025
16
16
<!-- _class: image -->
17
17

18
18
19
-
<!-- Feels like coming home, little recap
19
+
<!--
20
+
- Feels like coming home, little recap
20
21
- Api journy started in 2013, second api days Paris
21
-
- June 2018: openapi mandatory
22
22
- Step 1: standardize the way we describe APIs: OpenAPI Specification
23
-
-->
23
+
- June 2018: openapi mandatory
24
+
-->
24
25
25
26
## Italy
26
27
<!-- _class: image -->
@@ -51,7 +52,7 @@ December 11, 2025
51
52

52
53
53
54
## IT acceleration in The Netherlands
54
-
55
+
<!-- and the second reason... -->
55
56
- Serious incidents with local copies
56
57
- "Data at the source" principle
57
58
- Prevent local copies
@@ -66,7 +67,7 @@ December 11, 2025
66
67
- "Data at the source" principle
67
68
- Prevent local copies
68
69
- Digital Autonomy top priority in EU
69
-
- Dutch National Digital Strategy launched last july
70
+
- Dutch National Digital Strategy launched last July
70
71
71
72
## The new API Register
72
73
<!-- _class: title -->
@@ -106,7 +107,7 @@ December 11, 2025
106
107
- We can’t centralize legislation, but we can centralize the way gov APIs should work
107
108
- Discussions about versioning, pagination. Body or header links? Toss a coin.
108
109
- Dont care HOW but that we do it all the SAME.
109
-
- Mandatory standard
110
+
- Mandatory standard alongside the OpenAPI Specification
110
111
-->
111
112
112
113
## API Design Rules (ADR)
@@ -201,10 +202,10 @@ rules:
201
202

202
203
203
204
## Versioning and statuses
204
-
<!-- DX low when you have to parse runtime headers; what about closed apis? Perhaps we'll do it both, but urge to fix this in openapi, along with the version! -->
205
+
<!-- DX low when you have to parse runtime headers; what about closed apis? Perhaps we'll do it both, but urge to fix this in openapi, along with the version! Have a look at the SIG -->
205
206
206
207
- Exploit `info.version` for current semver of the API
207
-
- RFC 9745 not suitable; solution at runtime
208
+
- RFC 9745 (`Deprecation` and `Sunset` headers) not suitable; solution at runtime
208
209
- We work OpenAPI-first (design-time)
209
210
- Workaround: custom extensions
210
211
@@ -285,7 +286,7 @@ info:
285
286
## Reusable ADR schemas and components
286
287
<!-- schema register (based on DVLA presentation last year) -->
287
288
- @TODO: JSON Schema register
288
-
- @TODO: Update standard to OAS 3.1 or 3.2
289
+
- @TODO: Update standard to OAS 3.1
289
290
290
291
## Tools API
291
292
@@ -303,7 +304,8 @@ info:
303
304
## Publiccode.yml
304
305
305
306
- OAS for OSS projects in the public sector
306
-
- Collab EU, italy, brussels
307
+
- Collab EU, Italy, Brussels
308
+
- Sync with European Open Source Portal
307
309
308
310
## OSS-docs generator
309
311
<!-- _class: image -->
@@ -317,8 +319,19 @@ info:
317
319
318
320
- Stable and compliant landscape
319
321
- Notifications (RSS?)
320
-
- Schema register
322
+
- JSON Schema register
323
+
- Launching customer of code.overheid.nl (code.gov.nl)
324
+
- Tooling improvements
325
+
- Upgrade standard to OAS 3.1 or, hopefully, 3.2
326
+
327
+
## Next steps
328
+
329
+
- Stable and compliant landscape
330
+
- Notifications (RSS?)
331
+
- JSON Schema register
321
332
- Launching customer of code.overheid.nl (code.gov.nl)
0 commit comments