Well, educating us about this is a first step. It's certainly not the mainstream use:
Google searches for "resolve URI" and "resolve URL" return 4,700 and 3,500,000 pages. "dereference URI" and "dereference URL" return 800 and 1,300 pages.
--Michael
-------------------------------------------------------------------------- Michael Lee Database Programmer and Administrator Carolina Vegetation Survey http://cvs.bio.unc.edu/ michael.lee@unc.edu --------------------------------------------------------------------------
On Thu, Oct 14, 2010 at 8:51 AM, Bob Morris morris.bob@gmail.com wrote:
Is it too pedantic to wish that people would not use "resolve" when they mean "dereference"? The terms are distinguished in RFC 3986[1]: "URI "resolution" is the process of determining an access mechanism and the appropriate parameters necessary to dereference a URI; this resolution may require several iterations. To use that access mechanism to perform an action on the URI's resource is to "dereference" the URI." [1]
I bet the concensus answer to my question is "Yes". Sigh.
[1]http://www.rfc-editor.org/rfc/rfc3986.txt
Bob (The Pedant) Morris
-- Robert A. Morris Emeritus Professor of Computer Science UMASS-Boston 100 Morrissey Blvd Boston, MA 02125-3390 Associate, Harvard University Herbaria email: morris.bob@gmail.com web: http://bdei.cs.umb.edu/ web: http://etaxonomy.org/mw/FilteredPush http://www.cs.umb.edu/~ram http://www.cs.umb.edu/%7Eram phone (+1) 857 222 7992 (mobile) _______________________________________________ tdwg-content mailing list tdwg-content@lists.tdwg.org http://lists.tdwg.org/mailman/listinfo/tdwg-content