On 09/21/2011 12:21 PM, Metadata Management Associates on Get Satisfaction! wrote:
> When we moved to a new ISP, despite pre-move testing, we broke some things.
> This one has finally been fixed.
> Thanks for bringing it to our attention.
thanks for fixing the dereferencing issue!
There is still a small hickup though: the VIAF data (e.g., ) uses
uppercase hostnames (RDVocab.info), while the vocabulary file at 
is lowercase (rdvocab.info).
@Pedants: should I tinker with the RDF and convert all hostnames
to lowercase? Or is that better fixed at the source?
On 21 Sep 2011, at 12:40, Andreas Harth wrote:
> There is still a small hickup though: the VIAF data (e.g., ) uses
> uppercase hostnames (RDVocab.info), while the vocabulary file at 
> is lowercase (rdvocab.info).
> @Pedants: should I tinker with the RDF and convert all hostnames
> to lowercase? Or is that better fixed at the source?
The working draft of the upcoming RDF 1.1 Concepts & Abstract Syntax spec  has some text that is relevant here. (I'm the editor of this document, so I'm doing my best to inject some extra pedantry straight into the spec.)
Interoperability problems can be avoided by minting only IRIs that are normalized according to Section 5 of [IRI]. Non-normalized forms that should be avoided include:
* Uppercase characters in scheme names and domain names
So I think there is a good case that an URI with uppercase characters in the hostname, like <http://RDVocab.info/…>, is bad practice and the hostname should be changed to lowercase. (Uppercase characters elsewhere in the URI are fine though.)
On 09/21/2011 05:08 PM, Jon Phipps wrote:
> re: "the hostname should be changed to lowercase."
> Which we did. So Andreas, it would be a good idea to change your references
> as well.
I thought maybe you know the VIAF guys (who, by the way, provide excellent
data). The VIAF guys use your vocabulary (with uppercase hostname, e.g. they
use  at ).
I'm filling in a contact form at  and let them know directly.
The VIAF guys fixed the export.