Closed cboettig closed 5 years ago
I would argue that with #219 we should be able to safely delete the redundant ter
definition? (Although I'm using it in one of the tests.)
The only reason not to would be if we suspected that some clients or users out there are creating metas using this prefix for the property or relation, and never bothered to add the namespace because they figured it's predefined already. Possible, but not very likely?
On the flip side, leaving it there doesn't hurt anything until someone wishes to add it as a prefix with their own URI. Not sure how likely that is either. Prefix.cc doesn't know about ter
.
Right, I think it would be better to delete it.
As part of the coming release?
See: https://github.com/ropensci/RNeXML/pull/153#discussion_r68511277
Updated by @hlapp:
nexml_namespaces
defines the DC Terms URI both under prefixesdcterms
(which is the one commonly used) andter
(which, to say the least, is not widely used).