Am 08.02.2012 12:53, schrieb Karen Coyle:
> I actually wasn't thinking about readable v. opaque URIs, but that is
> one topic for best practices. In my experience, you get loud complaints
> with opaque URIs, but readable URIs are highly problematic.
> I was thinking about things like:
> - "cool" URIs - hash? or no?
> - PURLs v. agency domains
> - what should the URI resolve to?
> That kind of thing.
Does anyone know an answer to any of these questions? Therefore, I
think, no URI is better than no URI at all. Use brief and simple and
easily memorized codes for vocabularies like the terms in 337-338, and
use IDnumbers for names and subjects and titles.
Any implementation can easily relate them to all sorts of URIs that may
be in current use or follow best practice or resolve to something
useful for the purpose at hand. Verbal terms need changes and are
language-bound, URLs are perishable, only codes and numbers are robust,
easy to handle, and versatile.