Given that an incorrect format / or there is an error with the schema format chosen, when a user tries to say, "Import Column Properties", they get an error (see screenshot below) to visit the frictionless schema.
At the time, given that the errors returned by frictionless were possibly difficult to interpret for a user, it was thought better to just give a link to frictionless and only report the error.
Following Issue #1039, it might be worth:
Since frictionless libraries have since made a number of changes, it may be worth re-visiting to see if the error messages from frictionless can be parsed in a way to provide a hint to where the error might be.
Knowing that there are certain expectations for the 'root'-level name (e.g., for "Import Column Properties" and that the format should be JSON, we can perhaps provide a couple more types of error messages, in attempt to cover most probable use cases for those unfamiliar with frictionless, to help with these hints.
Is there a use case for, a certain type of error (say the frictionless schema is 'mostly' correct), where the schema can still be imported (kindofa 'lenient' vs 'strict' option) to enable users to 'massage' the schema or for Data Curator to complete it using 'Guess'? Not sure this is practical, but just raised here in case a use case for this comes through.
Given that an incorrect format / or there is an error with the schema format chosen, when a user tries to say, "Import Column Properties", they get an error (see screenshot below) to visit the frictionless schema. At the time, given that the errors returned by frictionless were possibly difficult to interpret for a user, it was thought better to just give a link to frictionless and only report the error. Following Issue #1039, it might be worth: