@prefix this: <https://w3id.org/np/RASQQ4Sk7RgxRP_jipNI_n9MRhx3q2MwFVYWD4wodYBWA> .
@prefix sub: <https://w3id.org/np/RASQQ4Sk7RgxRP_jipNI_n9MRhx3q2MwFVYWD4wodYBWA/> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
@prefix dcterms: <http://purl.org/dc/terms/> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix ns2: <https://w3id.org/np/o/ntemplate/> .
@prefix ns1: <http://www.nanopub.org/nschema#> .
@prefix prov: <http://www.w3.org/ns/prov#> .
@prefix ns4: <https://w3id.org/kpxl/gen/terms/> .
@prefix ns3: <http://purl.org/nanopub/x/> .

sub:Head {
  this: a ns1:Nanopublication;
    ns1:hasAssertion sub:assertion;
    ns1:hasProvenance sub:provenance;
    ns1:hasPublicationInfo sub:pubinfo .
}

sub:assertion {
  <https://w3id.org/np/RA8uD02NHPQ6DnLEivkHmOntI3TBakjd3Acq65lHF_Dzo/faq-entry> a <http://schema.org/Question>;
    dcterms:isPartOf <https://w3id.org/spaces/nanopub/r/faq>;
    rdfs:label "Are nanopublications peer reviewed? If so, how?";
    ns4:hasContent """<p>Not in the traditional pre-publication sense: there is no gatekeeper who approves a nanopublication before it becomes visible. Anyone with an identity and key pair can publish. Instead of anonymous pre-publication review, the system relies on cryptographic attribution — every nanopublication is signed, so it is always clear who stands behind a claim, and that reputation travels with it.</p>

<p>Review and quality assessment happen after publication, and can themselves take the form of nanopublications: an assessment, endorsement, or dispute is published as a signed nanopublication referring to the one under review. This makes reviews transparent, attributable, and citable first-class citizens of the same ecosystem, rather than hidden reports. Communities can organize whatever review workflow they like on top of this — the nanopublication infrastructure supports such processes but does not prescribe one.</p>

<p>Consumers, in turn, never have to take the network as an undifferentiated whole: queries can filter by author, by community, or by trust relations, so each application can apply exactly the level of scrutiny its use case requires.</p>""" .
}

sub:provenance {
  sub:assertion prov:wasAttributedTo <https://orcid.org/0000-0002-1267-0234> .
}

sub:pubinfo {
  this: dcterms:created "2026-07-16T11:40:38Z"^^xsd:dateTime;
    dcterms:creator <https://orcid.org/0000-0002-1267-0234>;
    dcterms:license <https://creativecommons.org/licenses/by/4.0/>;
    ns3:hasNanopubType <http://schema.org/Question>;
    ns3:introduces <https://w3id.org/np/RA8uD02NHPQ6DnLEivkHmOntI3TBakjd3Acq65lHF_Dzo/faq-entry>;
    ns3:supersedes <https://w3id.org/np/RA-KJ6h_UlEcjgSmbANvvvxCoVfHncjg-G0GUxM8NdmfA>;
    rdfs:label "FAQ: Are nanopublications peer reviewed? If so, how?";
    ns2:wasCreatedFromProvenanceTemplate <https://w3id.org/np/RA7lSq6MuK_TIC6JMSHvLtee3lpLoZDOqLJCLXevnrPoU>;
    ns2:wasCreatedFromPubinfoTemplate <https://w3id.org/np/RACJ58Gvyn91LqCKIO9zu1eijDQIeEff28iyDrJgjSJF8>,
      <https://w3id.org/np/RAoTD7udB2KtUuOuAe74tJi1t3VzK0DyWS7rYVAq1GRvw>, <https://w3id.org/np/RAukAcWHRDlkqxk7H2XNSegc1WnHI569INvNr-xdptDGI>;
    ns2:wasCreatedFromTemplate <https://w3id.org/np/RAUneCxaT_JQhs4XK8yFhSm5JGmAMgn8k6zBkWB2pp3BI> .
  
  sub:sig ns3:hasAlgorithm "RSA";
    ns3:hasPublicKey "MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCwUtewGCpT5vIfXYE1bmf/Uqu1ojqnWdYxv+ySO80ul8Gu7m8KoyPAwuvaPj0lvPtHrg000qMmkxzKhYknEjq8v7EerxZNYp5B3/3+5ZpuWOYAs78UnQVjbHSmDdmryr4D4VvvNIiUmd0yxci47dTFUj4DvfHnGd6hVe5+goqdcwIDAQAB";
    ns3:hasSignature "jrZQSOB6LVDbfi9xNA+lhVNeYPdqQeYeyd6z0DDVt1zQCTkTYnzMw3oYG/kEH2Os5BVnQejKAiYMWtvES6iSbvk9t+mjnl4uvQocemJc35w1hNMGAIpUs9DeD/pABuOrGC1sgRLD4ZNXZcVR5JmMm2naqOqoFhTISIybpAoHhJs=";
    ns3:hasSignatureTarget this:;
    ns3:signedBy <https://orcid.org/0000-0002-1267-0234> .
}