barnard59
barnard59 copied to clipboard
zazuko
An intuitive and flexible RDF pipeline solution designed to simplify and automate ETL processes for efficient data management.
Fix 304
should address #304. As discussed, the main idea is, in case there is a `sh:or` with all the alternatives having their own `sh:in`, to merge all the values into a...
As discussed, in all cases the `sh:in` gets separated between the `sh:or` alternative shapes. This would make it difficult for consumers to analyse the cube contents In the cases when...
# Ideas Some of these things might already exist or did exist in an older version of barnard59. Some might never happen. - [ ] #85 - [x] #93 -...
For #257 we'll implement a loader which handles values of type `code:SparqlQuery` It could be useful to allow custom loaders to be configured by pipeline authors in order to simplify...
I'd like SPARQL loaded from files, supporting `VALUES` ```turtle [ sparql:update ( [ a code:SparqlQuery ; code:link ; code:arguments [ code:name "foo" ; code:value "bar"^^code:VariableName ; ] ] )] ```...
> that would mean to use a generic http fetch instead of the barnard59-sparql operations? Because my understanding is that the 'construct' operation returns a stream of quads _Originally posted...
an experiment (still a draft) to overcome the issue described in https://github.com/zazuko/barnard59/pull/236. The new `check-class` command can check for a class constraint like the one in https://github.com/zazuko/cube-link/blob/main/constraint.ttl ```bash cat cube.ttl...
When installing, there are some deprecation warnings ``` npm WARN deprecated @opentelemetry/[email protected]: Package renamed to @opentelemetry/sdk-trace-node npm WARN deprecated @opentelemetry/[email protected]: Please use trace and metric specific exporters @opentelemetry/exporter-trace-otlp-http and @opentelemetry/exporter-metrics-otlp-http...