OEMetadata as frictionless datapackage extension

Description of the issue

We build on top of frictionless datapackage JSON schema based approach and inherit a lot of properties and the base structure they offer. Frictionless offers a extension system which uses he profile concept.

https://datapackage.org/standard/extensions/#extension

Oemetadata is mostly compliant with frictionless out of the box, even thought we introduced several new properties. Nevertheless, some things will break the compatibility between the two profiles, for example we offer a larger variety of data types to describe the data model.

Ideas of solution

Consider creating a proper frictionless data package extension profile.

Workflow checklist

• I am aware of the workflow in CONTRIBUTING.md