Skip to content

Conversation

@adamml
Copy link

@adamml adamml commented Dec 14, 2015

In using the OM-JSON repo for soem work with the Ocean Acidification project we ran into some validation issues (using XMLSpy which seems pretty good for JSONSchema validation too),

Bug fixes included.

Also, we added properties for DOI and @context to Common.json. Use of @context has been added to all Schema.

There's an additional call-out in Obserrvation.json for the Ocean Acidification work which points to my repo,

adamml and others added 30 commits October 5, 2015 16:25
Initial commit of the Ocean Acidification fork of om-json.

Intention is to push this back to the master with a pull request when
ready.
No requires "id" and "methodology"
Removed the peterataylor repository references to fix the issues faced
by XMLSpy and Oasis. Will need to revert this prior to the pull request
being issued and will log as an issue.
Moved the Context.json file to ./json-ld for file structuring clarity
adamml and others added 16 commits October 19, 2015 16:06
- MonitoringFeature contain an incorrect link to geometryObject. This is
in Geometry.json, not Common.json
- MonitoringFeature lists id as required, but there is no definition
provided (does this duplicate the id definition in SamplingCollection,
or do we pull the definition out into Common and reference it from there
in both SamplingCollection and MonitoringFeature…
- SamplingCollection contains type class which is of type “enum”:
"type": {
"title": "type",
"description": "Identifies the type of object",
"type": "enum"
},
he reference example file filename contains a type
(Reference_Examle.json instead of Reference_Example.json)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant