Skip to main content

Protected nanopublication

Nanopublications that stay on a local registry and never reach the public network: marking, routing, and expectations.

What a protected nanopublication is​

A protected nanopublication is one that stays on a local, private registry and never reaches the public network. It is meant for organisations that run their own nanopublication infrastructure and want to use it for content that is not for the world: internal records, drafts, data under restriction.

In every other respect it is an ordinary nanopublication — signed, immutable, with the same four parts — and it can be read, superseded and retracted within the instance that holds it.

Nanopublication · Open in Nanodash

How it is marked​

A nanopublication is protected when its publication info types the nanopublication itself as npx:ProtectedNanopub. This has to be a type of the nanopublication, not a "nanopublication type" annotation of the kind used for classifying content: registries check the former and ignore the latter, so a nanopublication that only looks protected would be sent to the public network.

Nanodash adds the marker through a checkbox in the publish form, offered only when the instance it runs on is a local one. Where a form is opened on a protected nanopublication, or uses a protected template, the box is ticked and cannot be cleared, so nothing protected can leak through a copy.

Nanopublication · Open in Nanodash

Where it goes​

A registry accepts protected nanopublications only if it is configured as a local instance, and says so in its status. Publishing tools check this per registry: a protected nanopublication is sent only to registries that report themselves local, and if none is available, publishing fails with a message saying so rather than quietly falling back to the public network. Public query services likewise refuse to load them.

Nanopublication · Open in Nanodash

What to expect​

Protected does not mean private within the instance: everyone with access to the local registry can read it, and the organisation running the instance can remove it — unlike on the public network, where nothing is ever removed. Whether new nanopublications are protected by default is a setting of the instance.

The public network and the local instance are separate worlds. A protected nanopublication can refer to public ones, but a public nanopublication that refers to a protected one carries a link nobody outside can follow, which is why a form with a protected source keeps the result protected too.

Nanopublication · Open in Nanodash

This page is a copy of the topic Protected nanopublication 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.