AskDefine | Define purl

Dictionary Definition



1 gold or silver wire thread
2 a basic knitting stitch [syn: purl stitch]


1 flow in a circular current, of liquids [syn: eddy, whirlpool, swirl, whirl]
2 make a murmuring sound; "the water was purling"
3 knit with a purl stitch
4 edge or border with gold or silver embroidery
5 embroider with gold or silver thread

User Contributed Dictionary



Etymology 1

purfle. Venetian pirlo an embellishment where the woven threads are twisted together.


  1. A particular stitch in knitting.
    Knit one, purl two.
  2. the edge of lace trimmed with loops


to purl
  1. To decorate with fringe or embroidered edge
    Needlework purled with gold.
  2. (knitting) an inverted stitch producing ribbing etc

Etymology 2

from etyl enm pirle, Middle etyl it pirla


  1. a heavy or headlong fall, an upset


  1. to upset, to spin, capsize, fall heavily, fall headlong
    the huntsman was purled from his horse.
Related terms

Etymology 3

From purla


  1. to flow with murmuring sound in swirls and eddies

Etymology 4

Possibly from pearl like appearance of due to bubbles on surface of liquid.


  1. (archaic) formerly ale spiced with wormwood and sometimes warmed.
    A double mug of purle. (The Spectator No. 88.)

Extensive Definition

A persistent uniform resource locator (PURL) is a Uniform Resource Locator (URL) (i.e. location-based Uniform Resource Identifier or URI) that does not directly describe the location of the resource to be retrieved but instead describes an intermediate (more persistent) location which, when retrieved, results in redirection (e.g. via a 302 HTTP status code) to the current location of the final resource.
PURLs are an interim measure — while Uniform Resource Names (URNs) are being mainstreamed — to solve the problem of transitory URIs in location-based URI schemes like HTTP. Persistence problems are caused by the practical impossibility of every user having their own domain name, and the inconvenience and money involved in re-registering domain names, that results in WWW authors putting their documents in rather arbitrary locations of questionable persistence (i.e. wherever they can get the WWW space). Existing official PURLs (on Purl.Org) will probably be mapped to a URN namespace at a later date.

Principles of operation

The oldest PURL HTTP server can be reached as as well as,, and
PURLs are organized into "domains" like directory paths, e.g. /net/scape is the "subdomain" scape of "domain" net, and has itself "subdomains" like about. These "domains" are unrelated to Internet domains; their purpose is to define one or more "maintainers". The maintainers can grant write access to ALL or other registered users, e.g. "domain" net is open for ALL registered users.
The PURL server, or "resolver" in PURL terminology, first tries to match a request directly to a defined PURL. If the PURL exists the reply is a redirect to the last URL associated with it as specified by its maintainer. This can be another PURL, any http-URL, or, in fact, any URL. It's the job of the maintainer to guarantee that target URLs do in fact still exist.
Because PURLs are designed to be persistent deleting them is not supported. They can be disabled, e.g. was disabled; otherwise PURLs work like redirects.
If the resolver gets no direct match for a given PURL it tries to match it right to left by truncating components separated by "/" against "partial redirects". This is a special kind of /x/y/z/any/thing PURL, where /x/y/z/ is defined and created as partial redirect. If its target URL is /a/b/c/d/ the /x/y/z/any/thing request is redirected to /a/b/c/d/any/thing.
For partial redirects the longest match wins, which is just the same as "right to left", so if, for example, y /x/y/z/any/ is defined with target /foo/, then the redirect would go to /foo/thing instead of /a/b/c/d/any/thing. The URL of a partial redirect does not necessarily end with a slash "/". Other examples for the query /x/y/z/any/thing and partial redirect /x/y/z/any/:
  1. Target /a/b/c/some results in a redirection to /a/b/c/something.
  2. Target /a/b/c?bar= results in a redirection to /a/b/c?bar=thing.
As shown partial redirects simply replace the longest known left hand side match by the target. Because direct matches are evaluated first it's possible to have ordinary PURLs "within" partial redirects, e.g. /x/y/z/any/but/this could be redirected to /a/b/c/elsewhere without affecting other /x/y/z/any/ queries matched by a partial redirect.
It's also possible to have different PURLs for /x/y/z and /x/y/z/ (note trailing slash), where the latter would be typically a partial redirect. For an example compare /net/scape and /net/scape/.
Popular http-servers silently add a "missing" trailing slash to URLs or strip an extraneous trailing slash as needed, although specification RFC 3986 allows them to refer to different resources.
Many Mediawiki Wikis support PURLs in the net domain by shorthands like for as shown above, because purlnet is defined in a Meta Interwiki map.

Notable redirects

This is an incomplete list of partial redirects in the net domain. The various possible left hand sides like are represented by the Interwiki prefix purlnet:, and working right hand side examples are shown.
Google groups search limited to net abuse:Encyclopedia of Integer Sequences by A-number :Crude Google en to de translation of a given URL:Like en2de, all pairs for de/en/fr might "work":Google groups archive access by Message-ID:Abstract and keywords for RFC 4321:Letter database Unicode point u+FEFF
purl in German: Persistent Uniform Resource Locator
purl in Russian: PURL

Synonyms, Antonyms and Related Words

Privacy Policy, About Us, Terms and Conditions, Contact Us
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2
Material from Wikipedia, Wiktionary, Dict
Valid HTML 4.01 Strict, Valid CSS Level 2.1