Barba-CV
Deterministic CV / resume data format
| Type | object |
|---|---|
| File match |
barba-cv.json
|
| Schema URL | https://catalog.lintel.tools/schemas/schemastore/barba-cv/latest.json |
| Source | https://raw.githubusercontent.com/Eurobotics-Association/barba-cv/main/schema/barba-cv.schema.json |
Validate with Lintel
npx @lintel/lintel check
Open-source deterministic JSON schema for structured CV data. Barba-CV v1.2 keeps the CV payload at root for backward compatibility while introducing a meta block and an extensions area.
Properties
Version of the Barba-CV payload format. Version 1 corresponded to raw Barba-CV JSON without formal schema metadata. Version 1.2 introduces this field, a meta block, and an extensions area.
Free-text professional summary or profile statement. May be empty or omitted.
Target roles or positioning statements describing the candidate's desired position or professional orientation. Often used as the headline of the CV.
Professional experience entries. May be empty or omitted.
Education entries. May be empty or omitted.
Certification entries. May be empty or omitted.
Languages known by the candidate. Language level remains flexible and human-readable.
Interests, hobbies, or other personal activities.
Structured project or achievement extracts derived from the CV. Replaces the legacy projects_achievements_extracts key.
13 nested properties
Unique identifier for the CV within processing pipelines or databases. Typically a UUID generated by the CV processing engine.
Human-readable title for the CV used for export, UI display, or filename generation.
Parser or mapping issues detected during extraction. In v1 this lived at root; in v1.2 it moves under meta.
Whether the JSON content reflects ATS-compatible post-processing rather than raw extraction only.
Engine or processor identifier that generated or revised the payload, e.g. barba_cv_engine_1.1.
Human-readable parse timestamp or ingestion timestamp. Left flexible to avoid rejecting operational data.
Original extracted text source when stored alongside the payload.
ATS-oriented revised text representation when available.
Original source format such as pdf, docx, html, or text.
Human-readable timestamp for database ingestion or downstream storage.
Human-readable timestamp indicating when vector embedding or downstream enrichment occurred.
Optional overall confidence score for AI extraction, between 0 and 1.