Technical Design

This page is aimed at the programmers in the audience. It aggregates all of the pages relating to how we are going to build this thing -- everything from high-level architecture to fine details of the design.

Architecture

The Querki Architecture is big and a tad complex. I'll attempt to lay out the various elements here.

• Statefulness, and why I've embraced it for now.
• Actors and Immutability, which is key to understand what's going on and why it works.
• Spaces and Space States -- the key data structures.
• Things and Models -- our equivalent of Objects and Classes.
• Properties, and the way they cut across a Space.
• Types and Collections -- the sorts of values you can put in a Property.
• Object IDs and Namespaces.
• Apps and Inheritance.
• The QText wiki language that users will be writing their text in.
• QL, the Querki Query Language.
• The Database Design that we'll be representing all of this in.
• Authentication, and integration with outside identity systems.
• Access Control, and the Veil of Privacy.
• Comments and Conversations, a subject always dear to my heart.

Other Subjects

• The Release Procedure.
• We will need some ongoing discussion about Mobile use of Querki.
• Import and Export.
• Open Source Credits.
• I have a sub-page for Technical Musings. None of that is hard-and-fast -- it's basically my notepad.
• Technical Requirements.