- From: Dawson, Laura <Laura.Dawson@bowker.com>
- Date: Tue, 23 Oct 2012 11:23:25 -0400
- To: Michael Hopwood <michael@editeur.org>
- CC: Ed Summers <ehs@pobox.com>, Cord Wiljes <cwiljes@cit-ec.uni-bielefeld.de>, "public-vocabs@w3.org" <public-vocabs@w3.org>
- Message-ID: <C6ADFCD0-DCD6-4ACB-BEB2-738447834441@bowker.com>
Exactly. I thought the URI/URN/URL debate had been settled? ;) I'm so glad you cited the DOI; one of the many reasons I like it so much is that it turns a URI into a URL (if you want), and if the URL changes, the URI does not, necessarily. Which removes a lot of concern around numerical identifiers being actionable vs text-based identifiers (which are not at all reliable). On Oct 23, 2012, at 11:18 AM, Michael Hopwood <michael@editeur.org<mailto:michael@editeur.org>> wrote: Thankfully not, ISNI just identifies a “name” rather than a person. My point (way back when Cord cited it!) was 1. The URL means the ID is “taken” – specifically by the network location for whatever is there (it could change, hencehttp://www.doi.org/doi_handbook/3_Resolution.html#3.6) This is a slightly different point (in as much as a spate of emails has one)… 2. A URI is not a URL. I may well have several URIs but I have no URL and hope never to… Cheers, m From: Dawson, Laura [mailto:Laura.Dawson@bowker.com<http://bowker.com/>] Sent: 23 October 2012 16:08 To: Michael Hopwood Cc: Ed Summers; Cord Wiljes; public-vocabs@w3.org<mailto:public-vocabs@w3.org> Subject: Re: Meaning of property "url" Yeah, I think we just took a turn for the existential. This comes up a lot in ISNI discussions (are we our identifier?). Anyone read "True Names" by Vernor Vinge? On Oct 23, 2012, at 11:00 AM, Michael Hopwood <michael@editeur.org<mailto:michael@editeur.org>> wrote: "Any information that can be named... e.g... a person..." There may be some philosophical issues there; is a person "information"? Sure, an antelope in a zoo may be a document (http://pages.gseis.ucla.edu/faculty/maack/BrietPrePress.htm) but isn't this taking it a little far? ;) -----Original Message----- From: ed.summers@gmail.com<mailto:ed.summers@gmail.com> [mailto:ed.summers@gmail.com<http://gmail.com/>] On Behalf Of Ed Summers Sent: 23 October 2012 15:43 To: Cord Wiljes Cc: public-vocabs@w3.org<mailto:public-vocabs@w3.org> Subject: Re: Meaning of property "url" On Mon, Sep 10, 2012 at 7:27 AM, Cord Wiljes <cwiljes@cit-ec.uni-bielefeld.de<mailto:cwiljes@cit-ec.uni-bielefeld.de>> wrote: Hi Michael, (schema.org<http://schema.org/>'s "url" property) means something very specific: "this is the Web location of" _____ (where ______ is some network addressable digital file). That is what I thought, too. But the I wonder why: "url" is a property of class "Thing" (instead of just class "CreativeWork") there is no property "homepage" for class "Person" or "website" for class "Organization" The notion of a URI identifying a "file" is terribly antiquated. So many URIs identify resources that have representations (html) assembled on the fly as the result of queries to databases and whatnot. I prefer to think that url being a property of Thing was an intentional move, because the author chose to sidestep the httpRange-14 issue, and let URLs identify any type of resource, as is the case in Roy Fielding's description of resource: """ The key abstraction of information in REST is a resource. Any information that can be named can be a resource: a document or image, a temporal service (e.g. "today's weather in Los Angeles"), a collection of other resources, a non-virtual object (e.g. a person), and so on. [1] """ //Ed [1] http://www.ics.uci.edu/~fielding/pubs/dissertation/rest_arch_style.htm#sec_5_2_1_1 Laura Dawson Product Manager, Identifiers Bowker 908-219-0082 917-770-6641 laura.dawson@bowker.com<mailto:laura.dawson@bowker.com> Laura Dawson Product Manager, Identifiers Bowker 908-219-0082 917-770-6641 laura.dawson@bowker.com<mailto:laura.dawson@bowker.com>
Received on Tuesday, 23 October 2012 15:23:49 UTC