BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//pretalx.eh23.easterhegg.eu//eh23//talk//EZPSUN
BEGIN:VTIMEZONE
TZID:CET
BEGIN:STANDARD
DTSTART:20001029T040000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10
TZNAME:CET
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20000326T030000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=3
TZNAME:CEST
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:pretalx-eh23-EZPSUN@pretalx.eh23.easterhegg.eu
DTSTART;TZID=CET:20260403T183000
DTEND;TZID=CET:20260403T190000
DESCRIPTION:Cory Doctorow argues that fighting the Enshittification of the 
 world involves making data and software more interoperable\, in order to r
 educe switching costs from centralized Big-Tech platforms. But even making
  data formats interoperable that are based on open standards is often easi
 er said than done. For instance\, the YAML 1.2 spec is very complex for hu
 mans to understand\, and many YAML parsers aren't fully spec-compliant eit
 her. And does your Nix tree-sitter grammar cause weird editor behavior too
 ?\n\nWe argue that we need a more concise and ergonomic way to express all
  the different syntaxes and data models of textual and binary data formats
 . A way that makes it easier to reason and talk about them\, and maybe com
 e up with your own when in need. And of course to transparently convert be
 tween them for better interoperability based on your specific needs. Most 
 existing approaches are implementation-defined (e.g. Pandoc's abstract con
 text representation lives in Haskell code files) or otherwise tied to an e
 cosystem (e.g. JSON schema). Can we properly unify them somehow? Without c
 ausing the standards proliferation effect known from the famous XKCD comic
  [ https://xkcd.com/927/ ]?\n\nIn this talk\, we propose an approach to in
 teroperability that conceptually resembles the ideas behind LSP and LLVM: 
 Instead of writing many ad-hoc compatibility layers for individual pairs o
 r small groups of formats\, we give each and every textual and binary form
 at a concise schema that bidirectionally maps it to a canonical AST repres
 entation. Now every ecosystem only needs to implement a single metamodel a
 nd schema parser to support all formats that have a schema available. View
 ing textual and binary formats as mere representations of a canonical AST 
 also makes it easy to create syntax extensions\, preprocessors or a fully 
 custom syntax in a language-independent way. Syntax does not matter - maki
 ng all formats interoperable via canonical AST representations does. Let's
  do it!\n\nSession materials will be available here: https://eh23.schmynta
 x.net/
DTSTAMP:20260404T022023Z
LOCATION:The Rabbit Hole
SUMMARY:Let's Make All Data Interoperable: Unifying Standards without the X
 KCD Effect - schmyntax
URL:https://pretalx.eh23.easterhegg.eu/eh23/talk/EZPSUN/
END:VEVENT
END:VCALENDAR