@mistersql @lettosprey My painful memory of that era – especially for anything semweb-related – was a thicket of ostensible standards whose architects were all so busy dreaming big that nobody had any time to work on actually testing them, maintaining examples, or seriously testing multiple implementation.

It was a formative moment both for strongly adopting the IETF's “running code” position and, especially, treating maintenance cost as one of the most important feedback signals.