Make specs protocol-agnostic
Quote
we try first and foremost to make the tag except future proof. So they accept any protocol. Yeah. The problem with namespaces in the past with with with podcasting is they, they they tied themselves to a specific protocol
Episode 160: Forced Choice (episode page, opens in a new tab) 00:25:01 (play audio from this timestamp, opens in a new tab)
Speaker-labeled
Summary
Earlier podcast namespaces failed by tying themselves to one protocol. Tags should accept any protocol so you can rip and replace when the next big thing arrives.
Also said
Episode 128: Fully Fingered (episode page, opens in a new tab) 00:15:10 (play audio from this timestamp, opens in a new tab)
We should probably that we should probably make it more clear in the namespace documentation that those are examples. Not limitation.
Speaker-labeled
Episode 167: Deck Darlings (episode page, opens in a new tab) 01:18:14 (play audio from this timestamp, opens in a new tab)
what we're trying to do with these tags, we're trying to genericized them, to make them adaptable to what to be useful now for the protocols we have now and for the future, to Yes, and for future for the 25 years in the future,
Speaker-labeled