De-referencing a GOM URIs results in a 404

[cportele]

Currently all the URIs like http://def.isotc211.org/iso19150/-2/2012/base#constraint result in a 404.

@BrodeurJS Will this change and is there a plan when this will happen?

[cportele]

This was discussed in a GOM meeting. It is unclear, when, if ever, the URIs will de-reference.

[hdelva]

Out of curiosity, are there any plans to fix this? http://def.isotc211.org/iso19150/-2/2012/base#constraint does not resolve, but http://def.isotc211.org/iso19150/-2/2012/base.rdf#constraint does. The latter is a different URI of course, but this does suggest that all the files are there, and it's just a matter of adding some content-type negotiation somewhere. I'm not an expert on Amazon Cloudfront, but I'd be surprised if they didn't support this.