From 43b7c41a19e118c77d22e89f0b9fccf4315ab9f4 Mon Sep 17 00:00:00 2001 From: Gray Brooks Date: Mon, 5 May 2014 17:08:05 -0400 Subject: [PATCH 1/2] adding a section to clarify capitalization --- schema.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/schema.md b/schema.md index 84f079c6..bd285201 100644 --- a/schema.md +++ b/schema.md @@ -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). From 4acaec70609ae9739508ad007b621eda87aef70c Mon Sep 17 00:00:00 2001 From: Gray Brooks Date: Mon, 5 May 2014 17:08:27 -0400 Subject: [PATCH 2/2] Update schema.md --- schema.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/schema.md b/schema.md index bd285201..ae6c594f 100644 --- a/schema.md +++ b/schema.md @@ -38,10 +38,10 @@ Where optional fields are included in a catalog file but are unpopulated, they m 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` +> 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).