Remove the uppercase field names

[JoshData]

On the schema page (http://project-open-data.github.io/schema/), why is every field listed with an uppercase "Field" name (e.g. "Release Date") and a lowercase "JSON" name (e.g. for Released Data, the corresponding JSON name is "issued")?

The only place the uppercase names are used seems to be be the Metadata page (http://project-open-data.github.io/metadata-resources/), where it is a link to the cross-walk table to the other vocabularies.

Do they have some other purpose? If they're not supposed to ever appear in any data file, they should be removed from the specification.

[jpmckinney]

It's common to give a brief human-readable label to a field. That is what appears in the "Field" column.

[JoshData]

But the JSON field name is human readable, so.....

[jpmckinney]

True, but that's not guaranteed to be the case. mbox, among others, is pretty meaningless.

[MarinaNitze]

Thanks for your feedback! We feel human-readable names are important here, especially when mapping across multiple schemas.