RE: Meaning of property "url"

"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] On Behalf Of Ed Summers
Sent: 23 October 2012 15:43
To: Cord Wiljes
Cc: 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> wrote:
> Hi Michael,
>
>> (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

Received on Tuesday, 23 October 2012 15:00:39 UTC