.job

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.5M
total occurrences
93.6K
since 2019 (6.2%)
1992–2023
years active

Case variants in archive: .job (1.5M), .JOB (1.1K), .Job (145), .JOb (3) — 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… (5)

File formats, image formats, audio codecs and other non-PL entities that claim .job 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
Compass and Ruler Job Q105857423
file format
file formattext/xmlUse as new PL ↗
Labeler (v2.0) / Labels Unlimited (v1.0) Job Q105857384
file format
file formatapplication/octet-streamUse as new PL ↗
Labeler (v3.0) / Labels Unlimited (v2.0) Job Q105857350
file format
file formatapplication/octet-streamUse as new PL ↗

SWH-mined examples (1)

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.
pipeline.job · 256 B · seen 231× in SWH
predicted: unclassified via unknown-ext
swh:1:cnt:b9fb32334a8b4febeba40f056371cc3eff9eae8a;origin=https://github.com/rinkstiekema/table-structures;anchor=swh:1:rev:66088dd05f2f36477fb970c34d6a07e689544a5e;path=/pipeline/pipeline.job
Open in SWH · Raw bytes
Request more SWH-mined examples
If the examples above don't disambiguate what .job is, request a fresh mining run.
(or open the pre-filled issue directly)