Today, we distribute the stations list by using composer. Composer then would but a constraint that npm and nodejs are needed to convert the CSV file to JSONLD, which can then be used by various applications.
I would however change the bin/build.js file to generate a lot of files in a dist/ directory in different serializations (linked-csv, json-ld, ntriples, rdfxml, ...) which would be committed within this repository. This way, people can directly access the data without having to compile it everytime.
Today, we distribute the stations list by using composer. Composer then would but a constraint that npm and nodejs are needed to convert the CSV file to JSONLD, which can then be used by various applications.
I would however change the bin/build.js file to generate a lot of files in a
dist/directory in different serializations (linked-csv, json-ld, ntriples, rdfxml, ...) which would be committed within this repository. This way, people can directly access the data without having to compile it everytime.