<aside> <img src="https://doriantaylor.com/inequal-to" alt="https://doriantaylor.com/inequal-to" width="40px" />
Dorian Taylor is a self-taught practitioner who grew up in Canada in the dot-com 1.0 era. Just the right age at just the right time, he went from pushing pixels, to running servers, to programming infrastructure, to UX design, experiencing what it's like to build the Web from every angle while it was still possible to get one's arms around the entire thing. He now helps clients with strategic planning, developing situation awareness, and the occasional technical heavy lift.
</aside>
This 31 (sorry) minute video explains what I’m doing in terms of concrete problems I have been trying to solve for several years.
The authoritative location for content related to this project is the following link:
The “protocol artifact” is here, still undergoing major surgery:
GitHub - doriantaylor/rb-rdf-sak at going-all-the-way
The new plan is that the “protocol essay” shall be the motivation and rationale document, since it actually argues something instead of just telling you how to do stuff:
The original plan for the “protocol essay” was to write an implementation guide, which is naturally contingent on an implementation. The skeleton of that forthcoming document is here:
For a more technical audience, I wrote down a set of architectural principles: