BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//pretalx.surf.nl//pidfest-26-2026//talk//7PWT8A
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-pidfest-26-2026-7PWT8A@pretalx.surf.nl
DTSTART;TZID=CET:20261027T150000
DTEND;TZID=CET:20261027T154500
DESCRIPTION:You've assigned PIDs to your datasets\, your people\, your publ
 ications. But where did that data actually come from? The data acquisition
  layer\, the instruments\, sensors\, and control software that generate ra
 w measurements\, is almost always a blind spot in PID infrastructure. Open
  frameworks like PyLabRobot are tackling this from the software side\, bui
 lding the driver layer where instrument identity and configuration can fin
 ally be captured and stamped onto the data it produces. Come explore why D
 AQs are a missing link in connected knowledge\, where the real barriers ar
 e\, vendor lock-in\, no open drivers\, no persistent identity\, no metadat
 a that travels with the data\, and what PID-connected instrumentation coul
 d actually look like. Leave with a clearer sense of what it would take to 
 get there\, and who else is working on the same problem.
DTSTAMP:20260728T010135Z
LOCATION:LUMC03
SUMMARY:Your Data Starts at the Instrument: Why DAQs Need PIDs Too - Vincen
 t Boer\, de
URL:https://pretalx.surf.nl/pidfest-26-2026/talk/7PWT8A/
END:VEVENT
END:VCALENDAR