In working on #196, I checked all cases where the prefix-ns package was used and what the namespaces were taken from that package.
That resulted in the below list of prefixes and namespaces, that I cross-referenced with prefix.cc. Most are as expected, but some are not.
This is not unexpected as prefixes aren't meant to be truly unique. Would it be beneficial to write a PR for a Mocha test that checks the output of prefix-ns?
I made one but there's the issue that it would just check the hardcoded namespaces, where some are as-expected, some are not. A better solution to prevent something like #195 from happening again is to make a proper file that exports these prefixes, which are to be imported by the other JS files.
Would you be open for a PR doing just that -- or is there some use to prefix-ns that I missed?
Issue type: :question: Question
In working on #196, I checked all cases where the
prefix-ns
package was used and what the namespaces were taken from that package.That resulted in the below list of prefixes and namespaces, that I cross-referenced with prefix.cc. Most are as expected, but some are not.
This is not unexpected as prefixes aren't meant to be truly unique. Would it be beneficial to write a PR for a Mocha test that checks the output of
prefix-ns
?I made one but there's the issue that it would just check the hardcoded namespaces, where some are as-expected, some are not. A better solution to prevent something like #195 from happening again is to make a proper file that exports these prefixes, which are to be imported by the other JS files.
Would you be open for a PR doing just that -- or is there some use to
prefix-ns
that I missed?http://semweb.mmlab.be/ns/rml-compression#
http://www.w3.org/ns/csvw#
http://www.wiwiss.fu-berlin.de/suhl/bizer/D2RQ/0.1#
http://www.w3.org/ns/dcat#
http://purl.org/dc/terms/
http://example.org/
http://semweb.mmlab.be/ns/fnml#
https://w3id.org/function/ontology#
http://xmlns.com/foaf/0.1/
http://www.w3.org/ns/formats/
http://users.ugent.be/~bjdmeest/function/grel.ttl#
https://www.w3.org/2019/wot/hypermedia#
http://example.com/idlab/function/
https://w3id.org/idsa/core/
https://w3id.org/ldes#
http://semweb.mmlab.be/ns/ql#
http://www.w3.org/1999/02/22-rdf-syntax-ns#
http://www.w3.org/2000/01/rdf-schema#
http://semweb.mmlab.be/ns/rml#
http://semweb.mmlab.be/ns/rml-target#
http://www.w3.org/ns/r2rml#
http://www.w3.org/ns/sparql-service-description#
https://www.w3.org/2019/wot/td#
https://w3id.org/tree#
http://rdfs.org/ns/void#
https://www.w3.org/2019/wot/security#