mcleo-d
commented
3 years ago Hey @grovesy,
Should this issue be linked to the Support of Config Language outcome document and is this where the success criteria will be listed?
James.
Open grovesy opened 3 years ago
mcleo-d
commented
3 years ago Hey @grovesy,
Should this issue be linked to the Support of Config Language outcome document and is this where the success criteria will be listed?
James.
mcleo-d
commented
3 years ago @grovesy - I have updated the links in the main issue body to reflect the suggestion below.
Should this issue be linked to the Support of Config Language outcome document and is this where the success criteria will be listed?
Title
Parent: Datahub-DataHelix-Collaboration Outcome: Support of Config Language
Abstract
This outcome is to decide if we need a single, extensible specification language that can be used to drive an API and possibly a UI.
DataHelix has an already established 'JSON' spec for declaring data profiles - the purpose of this profile markup is to declare a high-level spec, which DataHelix's core engine can use to produce the synthetic set.