@prefix this: . @prefix sub: . @prefix xsd: . @prefix dcterms: . @prefix rdfs: . @prefix ns2: . @prefix ns1: . @prefix prov: . @prefix ns4: . @prefix ns3: . sub:Head { this: a ns1:Nanopublication; ns1:hasAssertion sub:assertion; ns1:hasProvenance sub:provenance; ns1:hasPublicationInfo sub:pubinfo . } sub:assertion { a ; dcterms:isPartOf ; rdfs:label "Who can create nanopublications?"; ns4:hasContent """

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.

""" . } sub:provenance { sub:assertion prov:wasAttributedTo . } sub:pubinfo { this: dcterms:created "2026-07-16T11:40:38Z"^^xsd:dateTime; dcterms:creator ; dcterms:license ; ns3:hasNanopubType ; ns3:introduces ; ns3:supersedes ; rdfs:label "FAQ: Who can create nanopublications?"; ns2:wasCreatedFromProvenanceTemplate ; ns2:wasCreatedFromPubinfoTemplate , , ; ns2:wasCreatedFromTemplate . sub:sig ns3:hasAlgorithm "RSA"; ns3:hasPublicKey "MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCwUtewGCpT5vIfXYE1bmf/Uqu1ojqnWdYxv+ySO80ul8Gu7m8KoyPAwuvaPj0lvPtHrg000qMmkxzKhYknEjq8v7EerxZNYp5B3/3+5ZpuWOYAs78UnQVjbHSmDdmryr4D4VvvNIiUmd0yxci47dTFUj4DvfHnGd6hVe5+goqdcwIDAQAB"; ns3:hasSignature "fhxd2nNLVUVPzMeBydygdLCIS5NyzMHK/TkfAxLHrvMBK3xFngE/YhjLwsNJnzivhJD4JrlYLthJqSPOHr/biPkHPvn+EU2CT+eAR1Y+atXJbTqIvQwLvU7LkaNsQAhssRbGC/yfLSI9094lA5v8gILZO8rc8XoZy6tMdocxrkk="; ns3:hasSignatureTarget this:; ns3:signedBy . }