Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • XML namespaces use URIs as identifiers – Uniform Resource Identifiers. URIs need not actually be resolvable to anything. Even if a URI starts with the “http:” scheme, that means nothing more than that HTTP ownership rules apply; it does not mean there has to be a page there if you actually try to dereference the URI. (HTTP ownership rules are that whoever owns the DNS for the host part of the HTTP URI can mint new HTTP URIs with that host part.)

    There used to be a distinction such that URIs which can be resolved were called URLs (Uniform Resource Locators) and those which could not were called URNs (Uniform Resource Names). However, this distinction turned out to be nonsensical – there is no qualitative difference [walsh.name] – and has long since been dropped, and along with it, the terms “URL” and “URN”. Only the “URI” term exists in official Internet jargon now.

    • I think you missed the main point of the post. The PURL, as in Persistent URL, didn't exist.

      I know the difference between a URL and a URI. The fact that a URI didn't resolve didn't prompt the post. The fact that it used a supposedly persistent address did ;)