Metadata Typing

[ric-evans]

• added schema/types.py containing metadata type hints
  • this can be used by clients (aka the indexer)
  • this could allow validation.py to validate metadata using introspection (future)
• moved validation.py to schema/validation.py

[dsschult]

Type information generally looks good. I guess one question is how to fit the rest of the columns in the metadata doc.

[dsschult]

Are we really using such a long name?

[ric-evans]

Yup, I think this is the longest name

[ric-evans]

Type information generally looks good. I guess one question is how to fit the rest of the columns in the metadata doc.

We can put each description as an inline comment. For whether the key is required, that would need to be an independent dict.

[ric-evans]

Type information generally looks good. I guess one question is how to fit the rest of the columns in the metadata doc.

We can put each description as an inline comment. For whether the key is required, that would need to be an independent dict.

We could really go all out and duplicate/migrate the Google Doc into a dict/yaml. But this is beyond the scope of this PR

[dsschult]

Type information generally looks good. I guess one question is how to fit the rest of the columns in the metadata doc.

We can put each description as an inline comment. For whether the key is required, that would need to be an independent dict.

We could really go all out and duplicate/migrate the Google Doc into a dict/yaml. But this is beyond the scope of this PR

Fair enough.

[ric-evans]

Type information generally looks good. I guess one question is how to fit the rest of the columns in the metadata doc.

We can put each description as an inline comment. For whether the key is required, that would need to be an independent dict.

We could really go all out and duplicate/migrate the Google Doc into a dict/yaml. But this is beyond the scope of this PR

Fair enough.

#81