Skip to content
This repository was archived by the owner on Jun 18, 2024. It is now read-only.

Clarification that fields in the schema are case sensitive #305

Merged
merged 2 commits into from
May 5, 2014
Merged

Clarification that fields in the schema are case sensitive #305

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
43b7c41
adding a section to clarify capitalization
gbinal May 5, 2014
4acaec7
Update schema.md
gbinal May 5, 2014
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions schema.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36,6 +36,13 @@ The [Implementation Guidance](/implementation-guide/) available as a part of Pro

Where optional fields are included in a catalog file but are unpopulated, they may be represented by a `null` value. They should not be represented by an empty string (`""`).

The Project Open Data schema is case sensitive. The schema uses a camel case convention where the first letter of some words within a field are capitalized (usually all words but the first one). While it may seem subtle which characters are uppercase and lowercase, it is necessary to follow the exact same casing as defined in the schema documented here. For example:

> Correct: `contactPoint`
> Incorrect: `ContactPoint`
> Incorrect: `contactpoint`
> incorrect: `CONTACTPOINT`

Links to downloadable examples of metadata files developed in this and other formats in [the metadata resources](/metadata-resources/). Tools to help agencies produce and maintain their data inventories are [available on GitHub](http://www.github.com/project-open-data) and hosted at [Labs.Data.gov](http://labs.data.gov).


Expand Down