This text will hopefully be replaced by a useful answer soon.
This text will hopefully be replaced by a useful answer soon.
This text will hopefully be replaced by a useful answer soon.
This text will hopefully be replaced by a useful answer soon.
This text will hopefully be replaced by a useful answer soon.
A license is not technically mandatory, but the nanopublication network requires that published nanopublications be openly shareable and replicable, so any license that is declared should be compatible with that.
In practice, most nanopublications point to a permissive license via the dct:license predicate in their publication info — typically CC-BY 4.0 (https://creativecommons.org/licenses/by/4.0/) or CC0 (https://creativecommons.org/publicdomain/zero/1.0/).
Because the license is part of the signed, immutable nanopublication, it travels with the content and is verifiable by anyone who later retrieves it.
This text will hopefully be replaced by a useful answer soon.
The main entry point for finding nanopublications by criteria is Nanopub Query — a service that exposes published SPARQL query templates as REST API endpoints. Anyone can publish a new query as a nanopublication and immediately use it via the API; existing templates cover common needs such as finding nanopublications by author, type, topic, or content. For fully custom searches, direct SPARQL queries can also be issued against the type-specific or full nanopublication endpoints. For interactive use, Nanodash offers a Query tab that lets you browse and run all published query templates, and pre-built views are also available on user, space, and resource pages.
This text will hopefully be replaced by a useful answer soon.
This text will hopefully be replaced by a useful answer soon.
This text will hopefully be replaced by a useful answer soon.
This text will hopefully be replaced by a useful answer soon.
This text will hopefully be replaced by a useful answer soon.
This text will hopefully be replaced by a useful answer soon.
This text will hopefully be replaced by a useful answer soon.
This text will hopefully be replaced by a useful answer soon.
This text will hopefully be replaced by a useful answer soon.
This text will hopefully be replaced by a useful answer soon.
This text will hopefully be replaced by a useful answer soon.
This text will hopefully be replaced by a useful answer soon.
A nanopublication consists of three main parts: (1) an assertion, (2) information on the provenance of the assertion, (3) bibliographic metadata about the nanopublication itself. For further details, see https://nanopub.net/.
This text will hopefully be replaced by a useful answer soon.
This text will hopefully be replaced by a useful answer soon.
This text will hopefully be replaced by a useful answer soon.
This text will hopefully be replaced by a useful answer soon.
This text will hopefully be replaced by a useful answer soon.
This text will hopefully be replaced by a useful answer soon.
This text will hopefully be replaced by a useful answer soon.
This text will hopefully be replaced by a useful answer soon.
Anyone can create nanopublications. Technically, only a user identifier and an RSA key pair are needed. In practice, when using a tool like Nanodash, you don't have to deal with keys yourself — it generates and manages them on your behalf, and you simply sign in. Nanodash currently requires an ORCID, while the nanopublication format itself accepts any persistent user identifier; using ORCID is strongly recommended in any case, as it makes attribution interoperable across the scholarly ecosystem. If you publish locally (for example via the nanopub command-line tools), you do need to generate and manage your own key pair.