Person
Who you are on the network: your ORCID, your signing key, your introduction, and what approval means for you.
Who you are on the network
On the nanopublication network a person is identified by their ORCID, the identifier researchers use across publishers and funders. Nanodash logs you in through ORCID, and everything you publish names your ORCID as creator. Your page on Nanodash — reached from your name anywhere — lists your introductions, the spaces you belong to, and what you have published.
ORCID says who you are; it does not by itself let you publish. For that you need a signing key, and the network needs to know that the key is yours.
Your signing key
Every nanopublication is signed, so you need a key pair. Nanodash makes one for you on your profile page and keeps it with your account, so you can publish from any browser after logging in. If you also publish from the command line, that tool keeps its own key in a file on your computer.
The private half of a key never leaves the place it was made. The public half is published, in your introduction, so that anyone can check your signatures.
Your introduction
An introduction is a nanopublication that links a key to you: it names you, states your public key, and is signed with that very key. Nanodash creates and publishes it from your profile page when you make a key. It is the one nanopublication everything else depends on, since it is how the network learns which signatures are yours.
Each key gets its own introduction. A person with a key in Nanodash and another on their laptop has two introductions, and both keys count as them once approved.
Approval
A freshly introduced key is not trusted yet. Someone whom the network already trusts has to approve your introduction, by publishing a short nanopublication saying so — typically a colleague, a space admin, or whoever invited you. Nanodash offers this to them where your introduction is shown.
Until then you are pending: you can publish, and your nanopublications are stored, but wherever the network asks "who published this?" the answer is not yet you. Roles granted to you show up but do not take effect, and content restricted to members of a space does not include yours. Two things count already: declaring yourself an observer of a space, and choosing the views on your own page. Approval takes effect on the next completed trust round, which is a matter of minutes, occasionally longer.
Losing a key
A key in Nanodash stays with your account for as long as the instance exists. A command-line key is a file on your computer, and if that file is lost nobody can recover it. Nothing signed with a lost key can be superseded or retracted any more — those nanopublications stay as they are, and their content can only be replaced by new nanopublications made with a new key, which others will see as separate publications.
So keep a backup of a command-line key, and treat any key like a password: do not share it, and if it may have leaked, make a new one and stop using the old.
Several keys, one person
It is normal to have more than one key: one in Nanodash, one on each machine you script from, one for a bot you run. Each has its own introduction and its own approval, and all of them are yours. Roles in spaces are granted to you, not to a key, so they apply whichever key you sign with — as long as that key is approved.
Bots are the exception: a bot is its own agent with its own identity and roles, owned by you rather than being you.
This page is a copy of the topic Person 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.