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 kinda overload the semantics of code:imports but I find this quite understandable this way.
Such a loader could already be useful in conjunction with with the SHACL step. For example, here's how the b59-cubecheck-metadata pipeline would change
While the changes may not seem that dramatic, I find the usage much more idiomatic and obvious difference for the consumer is that a pipeline returns a stream and here we'd get a "read to use" dataset. A small difference maybe, but still an improvement IMO.
The text was updated successfully, but these errors were encountered:
In issue #31 we added a
p:FileContents
loader which reads a file as text and returns the contents.I propose a similar loader which would load, parse and return a dataset. Optionally with the
code:imports
resolved.I kinda overload the semantics of
code:imports
but I find this quite understandable this way.Such a loader could already be useful in conjunction with with the SHACL step. For example, here's how the
b59-cube
check-metadata
pipeline would changeWhile the changes may not seem that dramatic, I find the usage much more idiomatic and obvious difference for the consumer is that a pipeline returns a stream and here we'd get a "read to use" dataset. A small difference maybe, but still an improvement IMO.
The text was updated successfully, but these errors were encountered: