Resume date & label

[hankconn]

A given person might have multiple resumes, whether over time or different versions for different job titles / position sought. I would add a top level "resume_date" key and "resume_label" key.

[SethFalco]

Does this make much sense, though? 🤔
I'm not sure what your use-case is, but on the surface it sounds like it'd be easier to make 2 separate files?

i.e. engineer.resume.json for Software Engineer positions and writer.resume.json for Technical Writer positions.

It's worth noting, there is already a section to cover the date too:

"meta": {
  "type": "object",
  "description": "The schema version and any other tooling configuration lives here",
  "additionalProperties": true,
  "properties": {
    "canonical": {
      "type": "string",
      "description": "URL (as per RFC 3986) to latest version of this document",
      "format": "uri"
    },
    "version": {
      "type": "string",
      "description": "A version field which follows semver - e.g. v1.0.0"
    },
    "lastModified": {
      "type": "string",
      "description": "Using ISO 8601 with YYYY-MM-DDThh:mm:ss"
    }
  }
}

[thomasdavis]

Agree with Seth.

Users can manage that information with their own local setups.