Well, just no - this won’t fly, and the list of reasons is too long to write here. That said, there is a use case for serving authenticated content over plain HTTP - where the signature and metdata can be conveyed through a standardized HTTP header. This way, a lot of the content standardization bodies like W3C etc. won’t break.
If we trace back the origin, I would prefer to put more attribution to type theory, functional programming, and Haskell typeclasses. Perhaps a way to think of this is, what if COM was designed with our modern programming knowledge, together with knowledge in type theory and typeclasses.
Well, just no - this won’t fly, and the list of reasons is too long to write here. That said, there is a use case for serving authenticated content over plain HTTP - where the signature and metdata can be conveyed through a standardized HTTP header. This way, a lot of the content standardization bodies like W3C etc. won’t break.
Remember https://www.w3.org/Provider/Style/URI - it includes the scheme component.
Update: forgot that https://datatracker.ietf.org/doc/rfc9421/ is now a thing.
Microsoft called from 2000 and wanted their Component Object Model (COM) back. IUnknown sends her greetings.
If we trace back the origin, I would prefer to put more attribution to type theory, functional programming, and Haskell typeclasses. Perhaps a way to think of this is, what if COM was designed with our modern programming knowledge, together with knowledge in type theory and typeclasses.
Great article. Coincidentally, I put up YAAT - Yet Another ASCII Table yesterday (because asciitable.com sucks) at https://larsw.xyz/yaat/