I did check out JSON resume, a bit later after I made this, but the schema that I'm using it's too far fetched from what JSON Resume uses, and with a few tweaks

I did check out JSON resume, a bit later after I made this, but the schema that I'm using it's too far fetched from what JSON Resume uses, and with a few tweaks, like adding an ID field, or adding heading tags (so that resume sections headings can be in any language of the user's choice). The JSON I've made is a bit more flexible that way, specific to the application. Maybe this could be the new standard? (hehe)