.me — addressing
Namespace
jabellae.cleaker.me
jabellae.local.cleaker
me://jabellae.cleaker.me/profile.nameA namespace names WHICH tree of meaning you're addressing. Path (me.whatever(what)) names WHERE in it. Two different questions, answered two different ways — see O(k) Semantic Kernel Architecture for the tree the namespace points at.
Grammar
| handle | the claimed identity within a root — jabellae |
| root | the namespace's own anchor — cleaker.me, local.cleaker, any <root> |
| handle.root | the composed namespace — jabellae.cleaker.me |
| path | local state within that tree — bookmarkable, shareable, survives a refresh |
import { composeNamespace, parseNamespaceExpression } from "cleaker";
composeNamespace("jabellae", "cleaker.me");
// -> "jabellae.cleaker.me"
parseNamespaceExpression("jabellae.cleaker.me");
// -> { handle: "jabellae", root: "cleaker.me", ... }Two ways to be addressed
| Mounted natively | the page IS a door of the namespace — window.location.origin and the namespace are the same thing. |
| Referenced from outside | any page can point INTO a namespace — a link, a QR, an NRP expression — without being its door. The namespace is resolved from identity, never guessed from wherever the page happens to be served. |
The second case is the normal one, not the exception — a namespace is not the URL bar. It is whatever the identity resolves to, wherever you're standing when you ask.