URIs like http://rs.gbif.org/vocabulary/gbif/rank/domain were originally minted without the intention to make them resolve. Resolution was added later, but does not work in many cases.
For example, of the GBIF vocabularies the vegetation layer, taxonomic status, reference type, quantity type, preservation method, description type, dataset type, dataset subtype and agent role vocabulary all use a snake_case filename (vegetation_layer), but camelCase URI path fragments (vegetationLayer).
Further, where we have issued a new version of a vocabulary as a separate file, the URIs only resolve to the old version.
Fixing this might need some Apache configuration to be output by the build process, unless we want to go crazy with regular expressions.
URIs like http://rs.gbif.org/vocabulary/gbif/rank/domain were originally minted without the intention to make them resolve. Resolution was added later, but does not work in many cases.
For example, of the GBIF vocabularies the vegetation layer, taxonomic status, reference type, quantity type, preservation method, description type, dataset type, dataset subtype and agent role vocabulary all use a snake_case filename (vegetation_layer), but camelCase URI path fragments (vegetationLayer).
Further, where we have issued a new version of a vocabulary as a separate file, the URIs only resolve to the old version.
Fixing this might need some Apache configuration to be output by the build process, unless we want to go crazy with regular expressions.