Add (minimal) metadata to schema #204

[MarkBiesheuvel]

There has been some discussion about adding a metadata section to the schema. So I have wrote this as a suggestion.

The desire to have a metadata section has been mentioned in different issues. What most of these have in common is that it needs to store information that is not related to the person of the resume, but to the document itself. For example a URL where the document is hosted or a version number of the document.

I thinks this type of information indeed warrants a new section, so I've added a single metadata object in the resume schema.

Since this is a section where different tools and programs might need different keys, I've allowed for additional properties. Since the issue specified a list of key/value pair, the additional properties are only allowed to be string and numbers, not arrays or objects.

Any feedback is welcome

[thomasdavis]

Great initiative!

Alright, we can use this as the base PR to merge in.

Here is the original discussion #204

Let's start with changing metadata to meta

[thomasdavis]

Let's just push get something simple through, the scope is pretty big. In essence, meta will just represent a formally documented place for third party vendors to appropriately dump anything they want.

[MarkBiesheuvel]

Alright, sounds good.
I've renamed metadata to meta and I've also fixed my indenting.

[stp-ip]

Awesome. Do we want to add version into this basic PR too? That would cover the most basic use from resumejson itself. Know where to get the document, when it was modified and at which version it seems to be.

[thomasdavis]

Let's leave version out until next PR.

[stp-ip]

Ok.

[thomasdavis]

Mostly because I am also unsure if we should document sub properties of meta in the schema. Generally the tools can take care of it, even the version.

[stp-ip]

I would say a standard version should be in. All tool related stuff should be documented to be inside of a namespace such as meta.awesomeeditor.key.

[thomasdavis]

+1 to that, another PR to add a nested version property. I will write up some documentation about vendors name spacing.