Dontopedia

issue 512

From Dontopedia, the open, paraconsistent wiki. (Last updated 2026-06-06.)

issue 512 has 35 facts recorded in Dontopedia across 5 references, with 6 live disagreements.

35 facts·24 predicates·5 sources·6 in dispute

Mostly:describes use case(4), proposes solution(3), has title(2)

Maturity scale raw canonical shape-checked rule-derived certified

Advocates foradvocatesFor

Inbound mentions (13)

Other subjects in dontopedia point AT this entity as a value. These are inverse relationships — e.g. "X motherOf this subject" — and answer questions the forward facts can't. Grouped by predicate.

advocatedByAdvocated by(1)

containsUrlContains Url(1)

hasCanonicalUrlHas Canonical Url(1)

hasFinalUrlHas Final Url(1)

hasRequestedUrlHas Requested Url(1)

hasUrlHas Url(1)

hostsIssueHosts Issue(1)

mentionedInIssueMentioned in Issue(1)

motivatesProposalMotivates Proposal(1)

presupposesExistenceOfPresupposes Existence of(1)

providesEvidenceOfProvides Evidence of(1)

specifiesUrlSpecifies Url(1)

subjectIsSubject Is(1)

Other facts (32)

The long tail: predicates that appear too rarely to warrant their own section. Filter or scroll to find a specific one. Each row links to its source.

32 facts
PredicateValueRef
Describes Use CaseEarly Career Role Use Case[5]
Describes Use CaseFreelance Consulting Use Case[5]
Describes Use CaseHistorical Education Use Case[5]
Describes Use CaseSensitive Role Use Case[5]
Proposes SolutionSchema Modification Proposal[5]
Proposes SolutionTheme Behavior Update[5]
Proposes SolutionDate Policy Field Proposal[5]
Has TitleMake startDate/endDate optional & support age-neutral resumes[1]
Has TitleMake startDate/endDate optional & support age-neutral resumes · Issue #512 · jsonresume/resume-schema · GitHub[3]
Describes Problemthemes display Invalid Date when dates omitted[2]
Describes Problemmany themes display "Invalid Date" or break when startDate/endDate omitted[3]
Issue Number512[3]
Issue Number512[5]
Rdf:typeGithub Issue[4]
Rdf:typeGit Hub Issue[5]
AddressesKey Problem in Json Resume Schema[1]
ReferencesJson Resume Schema[1]
Is in Context ofGithub[1]
TitledMake startDate/endDate optional & support age-neutral resumes[2]
Lists Use Casesearly career, freelance, old experience, sensitive roles[2]
Open Graph TitleMake startDate/endDate optional...[2]
Proposes Date Policy Fieldhidden, approximate, exact[2]
Proposes Marking OptionalstartDate endDate[2]
Framed As ProposalOptional Dates[3]
Belongs to RepoResume Schema Repo[3]
References RepoResume Schema Repo[3]
Possibly TruncatedDescription[3]
SupportsAge Neutral Resumes[3]
Part of RepositoryJsonresume Resume Schema[4]
Has TopicJson Resume Schema[5]
Addresses ProblemInvalid Date Display Problem[5]
Mentions Social IssueAge Discrimination[5]

Timeline

Timeline axis is valid_time — when each source says the fact was true in the world, not when Dontopedia learned about it. Retracted rows are kept for provenance; coloured stripes indicate the context kind.

addressesblah/jsonresume/part-6
ex:key-problem-in-json-resume-schema
hasTitleblah/jsonresume/part-6
Make startDate/endDate optional & support age-neutral resumes
referencesblah/jsonresume/part-6
ex:json-resume-schema
isInContextOfblah/jsonresume/part-6
ex:github
titledblah/jsonresume/part-1
Make startDate/endDate optional & support age-neutral resumes
describesProblemblah/jsonresume/part-1
themes display Invalid Date when dates omitted
listsUseCasesblah/jsonresume/part-1
early career, freelance, old experience, sensitive roles
openGraphTitleblah/jsonresume/part-1
Make startDate/endDate optional...
proposesDatePolicyFieldblah/jsonresume/part-1
hidden, approximate, exact
proposesMarkingOptionalblah/jsonresume/part-1
startDate endDate
framedAsProposalblah/jsonresume/part-5
ex:optional-dates
describesProblemblah/jsonresume/part-5
many themes display "Invalid Date" or break when startDate/endDate omitted
hasTitleblah/jsonresume/part-5
Make startDate/endDate optional & support age-neutral resumes · Issue #512 · jsonresume/resume-schema · GitHub
belongsToRepoblah/jsonresume/part-5
ex:resume-schema-repo
issueNumberblah/jsonresume/part-5
512
advocatesForblah/jsonresume/part-5
ex:optional-dates
referencesRepoblah/jsonresume/part-5
ex:resume-schema-repo
possiblyTruncatedblah/jsonresume/part-5
ex:description
supportsblah/jsonresume/part-5
ex:age-neutral-resumes
typeblah/jsonresume/3
ex:GithubIssue
labelblah/jsonresume/3
issue 512
partOfRepositoryblah/jsonresume/3
ex:jsonresume-resume-schema
typeblah/jsonresume/6
ex:GitHubIssue
labelblah/jsonresume/6
"Make startDate/endDate optional & support age-neutral resumes"
issueNumberblah/jsonresume/6
512
hasTopicblah/jsonresume/6
ex:json-resume-schema
addressesProblemblah/jsonresume/6
ex:invalid-date-display-problem
mentionsSocialIssueblah/jsonresume/6
ex:age-discrimination
proposesSolutionblah/jsonresume/6
ex:schema-modification-proposal
proposesSolutionblah/jsonresume/6
ex:theme-behavior-update
proposesSolutionblah/jsonresume/6
ex:date-policy-field-proposal
describesUseCaseblah/jsonresume/6
ex:early-career-role-use-case
describesUseCaseblah/jsonresume/6
ex:freelance-consulting-use-case
describesUseCaseblah/jsonresume/6
ex:historical-education-use-case
describesUseCaseblah/jsonresume/6
ex:sensitive-role-use-case

References (5)

5 references
  1. [1]Part 64 facts
    ctx:discord/blah/jsonresume/part-6
  2. [2]Part 16 facts
    ctx:discord/blah/jsonresume/part-1
  3. [3]Part 59 facts
    ctx:discord/blah/jsonresume/part-5
  4. [4]33 facts
    ctx:discord/blah/jsonresume/3
    • full textjsonresume-3
      text/plain3 KBdoc:agent/jsonresume-3/10681bb6-9917-4834-a4c5-651a4ef9258d
      Show excerpt
      [2025-12-10 22:10] ajaxdavis: can now use keyboard to jump between nodes, and "m" to mark as read [2025-12-11 23:46] traves_theberge: https://x.com/tom_doerr/status/1999055162090852792?s=46 [2025-12-13 01:26] omega [bot]: Sounds like there'
  5. [5]613 facts
    ctx:discord/blah/jsonresume/6

See also

Keep researching

Missing something or suspicious of what's here? Kick off a research session — a Claude agent will investigate, cite its sources, and file new facts into a dedicated context you can review before accepting into the shared view.