Re: What does a URL identify: pragmatic approach

None of what you say makes sense to me.

That is, I don't know the structure of the web site,
and I don't know the default document name,
or any of the names within your document,
and consequently I don't know what any of your URLs mean.

Shouldn't the URLs have more explicit names,
which directly indicate what type of info. they refer to?
How about an ontology for naming conventions?
Dick McCullough 
knowledge := man do identify od existent done
knowledge haspart proposition list

  ----- Original Message ----- 
  From: Brian McBride 
  Sent: Tuesday, January 28, 2003 11:44 AM
  Subject: What does a URL identify: pragmatic approach

  On the tag list there has been a long thread on naming and what URI 
  references identify.  I don't want to fan the flames on that thread or 
  burden the tag members with deleting more unwanted mail, but I did want to 
  record an approach I'm trying out.  I hope this doesn't generate too much 
  traffic here.

  If you point your browser at:

  you should see the RDFCore's last call issues document.

  When you do a GET on that URI, the server returns a representation of:

  because that is the default document for a directory.

  So my conceptual model is this: identifies rdfcore's 
  last call issues list. identifies a 
  particular issue in that list identifies 
  an xhtml document, a representation of which is returned when I do a GET on 
  the issues list.  This is a document which provides useful information 
  about that list which the server is configured to return when a GET on the 
  abstract concept is received. 
  identifies an element in that xhtml document as defined by the appropriate 
  mime-type. identifies the directory 
  which contains Overview.html.

  So pragmatically speaking, I seem to have different names for the different 
  things I want to name, and it just seems to hang together.
  I can make rdf statements about the issues list, individual issues, the 
  document and elements of the document and its clear which is which.

  Pragmatically speaking, is this a good model to follow?

  And architecturaly, I'm left wondering whether there is a useful 
  generalization built around the fact that many web servers allow GET's on 
  one URL to be mapped to a different URL.  What I have done here is to use 
  such a mapping to have the web server map from a concept (a last call 
  issue) to a document giving information about that concept.


Received on Tuesday, 28 January 2003 19:43:44 UTC