The location templates are complicated and, no matter what gets done, will not work for everyone.
For us location would have been better handled if, for each vc:location, a ~resource~ was created using, when possible, the vc:location/@refid.
You did something similar for this in at least one of the sample data sets (VRA-RDF-Project/data/sample/rdf/record1.rdf, where a location resource is rdf:nodeID="N285d0120e2844ba9824f27f46845f38f"). However we don’t see that the XSLT can actually output such a resource. Perhaps we overlooked that template?
The location templates are complicated and, no matter what gets done, will not work for everyone.
For us location would have been better handled if, for each vc:location, a ~resource~ was created using, when possible, the vc:location/@refid.
You did something similar for this in at least one of the sample data sets (VRA-RDF-Project/data/sample/rdf/record1.rdf, where a location resource is rdf:nodeID="N285d0120e2844ba9824f27f46845f38f"). However we don’t see that the XSLT can actually output such a resource. Perhaps we overlooked that template?