Skip to main content

Space

Collaborative units on the network: creating a space, its admins and roles, sub-spaces, maintained resources, and what its page shows.

What a space is​

A space is a collaborative unit: a group, a project, an organisation, an event, a community. It has a page of its own, a set of people with roles in it, and things it maintains — vocabularies, documentation, collections. Most of what happens on Nanodash happens inside some space.

A space is defined by a nanopublication, like everything else, and so is every membership, role and resource attached to it. What you see on a space page is the sum of those nanopublications, filtered by who was entitled to publish each of them.

Nanopublication · Open in Nanodash

Creating a space​

A space is created with the "Defining a space" form. It asks for a name and a description, the kind of space — alliance, community, division, group, organization, outlet or program — and at least one admin. The space gets an address under https://w3id.org/spaces/, chosen when it is created, and that address is its permanent identity even when the definition is later revised.

The nanopublication that first defines a space is called its root definition. The admins it names are the space's founders, and everything else about the space traces its authority back to them.

Nanopublication · Open in Nanodash

Admins​

Admins own a space. They can revise its definition, attach roles to it, grant any role to anyone, declare what the space maintains, and decide what appears on its page. The admins named in the root definition are trusted by construction; a further admin can be added later, but only by an existing admin.

The founding admins cannot be removed, not even by themselves, so a space can never end up with nobody in charge. An admin added later can be removed by another admin, or step down.

Nanopublication · Open in Nanodash

Roles and members​

Everyone else in a space holds a role. Roles come in three tiers below admin: maintainer, member and observer. The tiers form a ladder — each may grant roles below its own. An admin may grant any role, a maintainer may grant member and observer roles, a member may grant observer roles. Observer is the one role people may take for themselves, by declaring their interest in a space.

Which roles exist in a space is up to its admins, who attach role definitions such as "team member" or "helper" to it. A role definition says which tier it belongs to and which statement expresses the grant. Granting is then a single nanopublication: this space has this person in this role.

Nanopublication · Open in Nanodash

When a membership takes effect​

A grant counts only if the person who published it was entitled to. The network checks this against the signing key: the key must belong to someone who, at that moment, holds a high enough role in the space. Grants that fail this test are stored but ignored — the space page does not show them, and the person does not get the access that goes with the role.

A newcomer's key is not trusted immediately. Until their introduction has been approved by someone already trusted, they appear as pending: their role is visible, but nothing they publish is yet counted, and content gated to members of the space does not include theirs. Approval takes effect when the network next recomputes its trust state, which can be a matter of minutes or longer.

Nanopublication · Open in Nanodash

Leaving and removing​

A role is taken away by publishing a revocation: a nanopublication naming the space, the person and the role. Anyone may revoke a role held by someone below their own tier, and anyone may revoke their own. Revoking does not undo the original grant nanopublication; it overrides it, and a later grant restores the role again.

The founding admins are the exception: their role cannot be revoked at all.

Nanopublication · Open in Nanodash

Sub-spaces​

A space can be part of another: a working group within a project, a project within an organisation. This is declared with gen:isSubSpaceOf, either in the space's own definition or as a separate nanopublication. The link counts only when an admin of each space stands behind it — one person who is admin of both, or a declaration from each side — so no space can attach itself to another uninvited.

Sub-spaces are shown on the parent's page and the parent on the sub-space's page, but membership does not flow between them: being a member of the parent says nothing about the sub-space, and the other way round.

Nanopublication · Open in Nanodash

Maintained resources​

A space can declare that it maintains a resource: a vocabulary, a documentation collection, a dataset, a template. The declaration is made by an admin and gives the resource a page of its own, hosted within the space. A resource may declare a namespace, a URI prefix under which the things belonging to it are minted; such things then get pages as parts of the resource.

Membership of the space decides who counts as a maintainer of the resource. Where a resource's content is edited collaboratively — this documentation is an example — it is typically the members of the maintaining space whose contributions are shown.

Nanopublication · Open in Nanodash

What appears on a space page​

A space page is made up of views: lists, tables and texts, each backed by a query over the network. Some views come with every space. Others are attached by the space's admins or maintainers, either one by one or as a preset, a bundle of views and roles that gives a space a ready-made layout. Attaching and removing views is itself done through nanopublications, and the newest decision wins.

Many views offer actions — a button to add a member, post a message, propose a term. Which actions a visitor sees depends on the role they hold in the space.

Nanopublication · Open in Nanodash

Things a space governs​

A space can take charge of a shared definition — a template, a view — so that any of its members may publish the next version, rather than only the person who published the last one. Each version names the space with gen:governedBy, and an admin lists the template or view as a maintained resource of the space. From then on the current version is the newest one published by a member of the space.

A governed version whose template or view the space does not maintain yet appears on the space's About tab marked "not listed yet", with an action to list it. This is how a community keeps its shared tools current over time, without depending on any one person's signing key.

Nanopublication · Open in Nanodash

Finding spaces​

A space is usually found by following links: every person's page shows the spaces they belong to, every space page shows its sub-spaces and the resources it maintains, and every resource page names the space that maintains it. The Nanopub Query service also publishes a plain list of all spaces known to the network, for software and for anyone who wants an overview.

Nanopublication · Open in Nanodash

This page is a copy of the topic Space of the Nanopublication Docs. Each paragraph is a nanopublication. In Nanodash you also find their examples, related paragraphs, and version history, and members of the nanopub space can edit them there.