You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I only see the rdf data cube constraints coming from the spec implemented.
I expected to find some additional queries to test if the data comply to the additional constraints the swirrl processing pipelines impose such as the required use of qb:measureType even in the context of having just one measurement.
Have I overlooked something?
The text was updated successfully, but these errors were encountered:
@paulzh - Those validation queries are defined in the graphql-qb repository, currently on the issue_127 branch in the validation folder. See the Data validation section of the README in that branch.
I presume you're talking about table2qb input validation? Indeed we should add that - there's an issue for the codelist-pipeline but the others pipelines deserve validation too. I suspect we'd implement this by inspects the tabular inputs - e.g. comparing the column headings/ contents with the config - rather than the rdf outputs not least because you mightn't be able to even generate an output given invalid input.
Please note that the measure type is only required because we've not got around to implementing the multi-measure approach yet.
Hi,
I only see the rdf data cube constraints coming from the spec implemented.
I expected to find some additional queries to test if the data comply to the additional constraints the swirrl processing pipelines impose such as the required use of qb:measureType even in the context of having just one measurement.
Have I overlooked something?
The text was updated successfully, but these errors were encountered: