Add explicit json types #146

[Ludee]

Summary of the discussion

The JSON schema spec allows some build in additional types.
Used options are:

• "date": 2018-11-13
• "date-time": 2018-11-13T20:20:39+00:00
• "uri": A universal resource identifier (URI), according to RFC3986.

Type of change (CHANGELOG.md)

Added

• Add explicit json types (#166)

Workflow checklist

Automation

Closes #146

PR-Assignee

• 🐙 Follow the workflow in CONTRIBUTING.md
• 📝 Update the CHANGELOG.md
• 📙 Update the documentation

Reviewer

• 🐙 Follow the Reviewer Guidelines
• 🐙 Provided feedback and show sufficient appreciation for the work done

[jh-RLI]

That's good. I think it's worth taking a second look. We should probably also add some regex for validation. Once we have implemented this in the Oemetabuilder, we can use the schema to validate the form inputs and provide feedback to the user about exactly which fields have not been filled in correctly. The format (type) is good regex, for example, would ensure that users use the format “topic.table_name” for the field “tables name” instead of “table name”.

However, this can happen in another PR and would not be a breaking change

[Ludee]

Thanks for the detailed review.

I agree that there can be more "pattern" fields in the schema.
This issue was only about the "types".