Namespaces used: beneficial to test for?

[redmer]

Issue type: ❓ 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?

---

Prefix	Used in RML	Identical to Prefix.CC
comp	http://semweb.mmlab.be/ns/rml-compression#	✔
csvw	http://www.w3.org/ns/csvw#	✔
d2rq	http://www.wiwiss.fu-berlin.de/suhl/bizer/D2RQ/0.1#	✔
dcat	http://www.w3.org/ns/dcat#	✔
dcterms	http://purl.org/dc/terms/	✔
ex	http://example.org/	✔
fnml	http://semweb.mmlab.be/ns/fnml#	✔
fno	https://w3id.org/function/ontology#	✔
foaf	http://xmlns.com/foaf/0.1/	✔
formats	http://www.w3.org/ns/formats/	✔
grel	http://users.ugent.be/~bjdmeest/function/grel.ttl#	✔
hctl	https://www.w3.org/2019/wot/hypermedia#	✔
idlab-fn	http://example.com/idlab/function/	Not defined
idsa	https://w3id.org/idsa/core/	Not defined
ldes	https://w3id.org/ldes#	❌
ql	http://semweb.mmlab.be/ns/ql#	❌
rdf	http://www.w3.org/1999/02/22-rdf-syntax-ns#	✔
rdfs	http://www.w3.org/2000/01/rdf-schema#	✔
rml	http://semweb.mmlab.be/ns/rml#	❌
rmlt	http://semweb.mmlab.be/ns/rml-target#	✔
rr	http://www.w3.org/ns/r2rml#	✔
sd	http://www.w3.org/ns/sparql-service-description#	✔
td	https://www.w3.org/2019/wot/td#	✔
tree	https://w3id.org/tree#	✔
void	http://rdfs.org/ns/void#	✔
wotsec	https://www.w3.org/2019/wot/security#	✔

[redmer]

With the changes in v1.5.1, all four prefixes above resolve to the expected namespaces.