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
We need a simple way to populate the knowledge base with documentation of data resources (sources and sinks). Below is a suggested YAML format for documenting a set of resources in a single YAML document. The idea is to create a Python API and a tool that takes this YAML and a base IRI as input and populate the knowledge base with the documented data resources.
The keyword partial_pipelines is too implementation specific. I would prefer data_resources.
---
version: 1.0partial_pipelines: # Find a better name. `data_resources` would be ideal, except that it may create confusion with the `dataresource` strategy below.TEM-BF-image1: # This name will be prepended a `base_iri` when creating an IRI for the data resource in the knowledge base.dataresource:
downloadURL: http://...mediaType: text/csv...parse:
parserType: dlite-parse...mapping:
mappingType: mappingsprefixes:
...triples:
...TEM-BF-image2:
dataresource:
...parse:
...mappings:
...my-data-sink:
mappings:
...generate:
...dataresource:
downloadURL: http://...mediaType: text/csv```
The text was updated successfully, but these errors were encountered:
We need a simple way to populate the knowledge base with documentation of data resources (sources and sinks). Below is a suggested YAML format for documenting a set of resources in a single YAML document. The idea is to create a Python API and a tool that takes this YAML and a base IRI as input and populate the knowledge base with the documented data resources.
The keyword
partial_pipelines
is too implementation specific. I would preferdata_resources
.The text was updated successfully, but these errors were encountered: