@prefix this: . @prefix sub: . @prefix schema: . @prefix gen: . @prefix np: . @prefix dct: . @prefix nt: . @prefix npx: . @prefix xsd: . @prefix rdfs: . @prefix orcid: . @prefix prov: . sub:Head { this: a np:Nanopublication; np:hasAssertion sub:assertion; np:hasProvenance sub:provenance; np:hasPublicationInfo sub:pubinfo . } sub:assertion { a schema:Question; dct:isPartOf ; rdfs:label "Who can create nanopublications?"; gen: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:wasDerivedFrom . } sub:pubinfo { this: dct:created "2026-05-09T21:20:34Z"^^xsd:dateTime; dct:creator orcid:0000-0002-1267-0234; dct:license ; npx:introduces ; rdfs:label "FAQ: Who can create nanopublications?"; nt:wasCreatedFromProvenanceTemplate ; nt:wasCreatedFromPubinfoTemplate , , ; nt:wasCreatedFromTemplate . sub:sig npx:hasAlgorithm "RSA"; npx:hasPublicKey "MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCwUtewGCpT5vIfXYE1bmf/Uqu1ojqnWdYxv+ySO80ul8Gu7m8KoyPAwuvaPj0lvPtHrg000qMmkxzKhYknEjq8v7EerxZNYp5B3/3+5ZpuWOYAs78UnQVjbHSmDdmryr4D4VvvNIiUmd0yxci47dTFUj4DvfHnGd6hVe5+goqdcwIDAQAB"; npx:hasSignature "mSgc1hnluglovn24anuFvXXQ85zALY3nh7B9GWk3bmK66HE3HenpmodYnC8q9DFgombwTB054SKuG6l5GmPbjomKE2qD8kpDSQl5WZJPZPgfreSw887wLRnUoLKhR86FgYxgrqmQLs8jMI5xrCXfD09R916x+QtcQjl0lm7oOOU="; npx:hasSignatureTarget this:; npx:signedBy orcid:0000-0002-1267-0234 . }