Create 1.0.0.schema.json

[srappel]

Addresses #41

Adds a JSON Schema file for Specification 1.0.0 which will help GeoBlacklight development better integrate OpenIndexMaps.

I had ChatGPT do a lot of the drafting, but it seems to validate fine. And despite saying that we have no required elements, I've included label, north, south, east, and west. Open to suggestions about this.

[srappel]

There's a general GeoJSON schema file here. We might want to take a look and compare.

[kgjenkins]

I'm not sure about requiring north/south/east/west elements.

For typical rectangle-based index maps, these values are redundant with the information found in the geometry.
For point-based index maps (like aerial photo centroids), there will be no NSEW elements.

Looking at the GBL code, I don't think GBL actually requires any elements except the geometry. However, basic functionality would require "label" (although GBL will handle null).

[srappel]

Thats a good point about the point features. And if GBL can handle null in the label field, then I think we can move forward with no required elements. Reminding myself this means we need to explicitly allow null for these elements.

[srappel]

At Geo4LibCamp we thought it would be useful to make the JSON Schema file a bit more restrictive about foreign member elements. Some fields like websiteUrl had been incorrectly entered as websiteURL which did not flag the validation but did break GeoBlacklight. That's what these last few commits are about.

[thatbudakguy]

@srappel is this ready to merge? we're wondering about how it is related to geoblacklight/geoblacklight#1346 and how geoblacklight could use this.

[srappel]

@thatbudakguy I think we were waiting on something about netlify? The schema work is done, I think the block was a website issue.