.nq

0 claimants 0 primary 0 secondary

SWH popularity

From the SWH-MSR-ARV dataset (Desmazières, Di Cosmo, Lorentz, MSR 2025; file nb_extensions_alphanum.csv) — one row per (ext, year) in the full SWH archive. Case-aggregated. citation.

1.6M
total occurrences
586.5K
since 2019 (36.0%)
2003–2023
years active

Case variants in archive: .nq (1.6M), .NQ (1) — aggregated above.

Help label this extension

No PL in our taxonomy claims this extension. If you know what it's used for, fill the form below. Vocabulary reference: docs/extension_labels.md.

— or, if the button is blocked, use the link just below:
(fill the form to enable this link)
What happens after I submit?
  1. A new GitHub issue is opened in this repo with your form contents in a structured YAML block and the label ext-review. Your GitHub login becomes the annotator; the issue's created_at is the submission timestamp.
  2. A curator script (tools/process_extension_labels.py) fetches all ext-review issues and writes their parsed contents into data/derived/extension_labels.csv with curator_status="new". Until this script runs, your submission lives only as the GitHub issue.
  3. Your submission shows up on the curator triage page (/review/curator/) under "new". Maintainers review the issue (comment, ask for clarification, accept or reject) and edit extension_labels.csv to set curator_status to accepted.
  4. For pl/<id> labels, build_pl_taxonomy.py promotes accepted labels into ext_claim.csv with source="manual_review:<your-login>" and strength="proposed". The next site rebuild then shows your claim on this extension's page and on the language's page.
  5. Friendly-name + reference-URL labels (e.g. binary:image for .png) are not promoted into ext_claim.csv (they aren't PL claims) but are surfaced on this page's "Prior labels" table so anyone landing here sees them next to the auto-detected category.

In short: submitting opens an issue (provenance), and a small ingestion pipeline turns issues into rows the site renders. The loop is currently manual (the curator script must be run by a maintainer); GitHub Actions could automate it on each new issue.

Wikidata says… (2)

File formats, image formats, audio codecs and other non-PL entities that claim .nq on Wikidata (property P1195) or in the Wikipedia infobox. Source: data/derived/external_extension_index.csv. Click Use as new PL on any row to open the Add-PL form pre-filled with that entry's name, Wikipedia/Wikidata URL, and this extension — one submission creates the PL + claim.
Right entry isn't listed? Add manually ↗
FormatClass (Wikidata P31)Suggested labelMIMENotesAction
N-Quads Q31398150
line-based, plain text format for encoding an RDF dataset
file formatapplication/n-quadsUse as new PL ↗
N-Triples Q44044
file format
file format; data serialization formatapplication/n-tripleswp-onlyUse as new PL ↗

SWH-mined examples (2)

Real archived programs with this extension, byte-verified against the SWH archive. Useful for deciding what this extension actually is when the attribution is uncertain.
og.nq · 32180 B · seen 28× in SWH
predicted: unclassified via unknown-ext
swh:1:cnt:c46470c0a394eb20818e1994b82e68a07d1ba574;origin=https://github.com/manomayam/rdf_vocabularies;anchor=swh:1:rev:402cd0dae5ffe983849629d5ef308b400a2b304a;path=/ontologies/og.nq
Open in SWH · Raw bytes
example.body.nq · 987 B · seen 16× in SWH
predicted: unclassified via unknown-ext
swh:1:cnt:98e0595f140b8cdf4aa3a283857f95988e0fd0b1;origin=https://github.com/cardano-foundation/CIPs;anchor=swh:1:rev:ea2e0e4de543060c48fd7f07efa9c3fa48ffd425;path=/CIP-0100/example.body.nq
Open in SWH · Raw bytes
Request more SWH-mined examples
If the examples above don't disambiguate what .nq is, request a fresh mining run.
(or open the pre-filled issue directly)