Information resources

Important Change to HTTP semantics re. hashless URIs from Kingsley Idehen on 2013-03-24 (public-lod@w3.org from March 2013)

2013-03-25T16:01:42Z

Using "Punning" to Answer httpRange-14 | Jeni's Musings

2012-05-12T18:11:19Z

TagIssue57Responses - W3C Wiki

2012-04-13T17:30:48Z

Re: See Other from Hugh Glaser

2012-04-12T00:15:22Z

Re: Change Proposal for HttpRange-14 from Jeni Tennison

2012-04-11T17:11:59Z

Re: Classification of ISSUE-57 change proposals - R Fielding

2012-04-11T13:44:31Z

httpRange-14 says that if the resource owner cares to make a distinction, here is how they can make that distinction. It does not say the distinction is necessary. The assumption that 200 implies IR is pure speculation

ISSUE-57: Mechanisms for obtaining information about the meaning of a given URI - Technical Architecture Group Tracker

2012-04-11T13:40:40Z

Re: [Fwd: Reversing HTTP Range 14 and SemWeb Cool URIs decision]

2012-04-11T13:40:09Z

Re: Squaring the HTTP-range-14 circle

2011-12-17T15:38:05Z

The web of data will succeed *because* it conflates a thing and a web page about the thing.

Repurposing the Hash Sign for the New Web

2011-08-11T17:36:45Z

Hash URIs | Jeni's Musings

2011-08-11T11:30:17Z

Making AJAX Applications Crawlable - Google Code

2011-08-11T11:27:45Z

Providing and discovering definitions of URIs

2011-06-26T14:38:17Z

httpRange-14 Reflux - Danny Ayers : Raw Blog

2011-06-15T17:46:03Z

you can't squeeze a dog over the wire with HTTP, but that's just a limitation of the protocol

Re: Is 303 really necessary?

2010-12-28T14:38:17Z

Is 303 Really Necessary? - Internet Alchemy

2010-11-11T15:08:16Z

Semantic Web Semantics: Arcane, but Important » AI3:::Adaptive Information

2008-04-15T15:24:02Z

wiki to dbpedia with sparql

2008-02-01T22:31:16Z

SELECT ?subject ?p WHERE { { ?subject ?p http://en.wikipedia.org/wiki/Well-Tempered_Clavier } }

Alternative to 303 response: Description-ID: header From: Tim Berners-Lee

2008-01-03T12:07:21Z

I did wonder about the following: in the case when the URI is not of document, when currently we use 303, then the server can return a document *about* it with an extra header to explain to the browser that it is actually giving you a description of it not the content of it.

URI Identity and Web Architecture Revisited

2007-11-20T21:36:46Z

Re: More on distinguishing information resources from other resources Roy T. Fielding

2007-11-20T21:32:46Z

SPARQL query to find the dbPedia concept corresponding to a wikipedia page

2007-10-13T00:28:42Z

SELECT ?s ?p WHERE { { ?s ?p } }

From Wikipedia URI-s to DBpedia URI… « Ivan’s blog

2007-08-01T17:02:03Z

dowhatimean.net » Content negotiation with hash URIs (long)

2007-04-03T23:30:30Z

Cool URIs for the Semantic Web

2007-04-03T23:26:43Z

303 URIs and hash URIs

HTTP behaviour for SKOS Concepts from Miles, AJ \(Alistair\) on 2005-06-21 (public-esw-thes@w3.org from June 2005)

2007-01-03

RE: [VM] content-dependent redirects in apache ... help! from Miles, AJ \(Alistair\) on 2005-10-03 (public-esw-thes@w3.org from October 2005)

2007-01-03

[httpRange-14] Resolved from Roy T. Fielding on 2005-06-19 (www-tag@w3.org from June 2005)

2007-01-02

we provide advice to the community that they may mint "http" URIs for any resource provided that they follow this simple rule for the sake of removing ambiguity: a) If an "http" resource responds to a GET request with a 2xx response, then the resource identified by that URI is an information resource; b) If an "http" resource responds to a GET request with a 303 (See Other) response, then the resource identified by that URI could be any resource; c) If an "http" resource responds to a GET request with a 4xx (error) response, then the nature of the resource is unknown.

Re: AW: Content negotiation flamewar (was: Re: "Hash URIs" and content negotiation) from Richard Cyganiak on 2006-11-13 (semantic-web@w3.org from November 2006)

2007-01-02

If foo is another kind of resources (e.g. a person), then you *must* do a 303 redirect to the location where a description of foo is available. You can 303-redirect to different locations based on accept headers. Post-httpRange-14, the only way to serve a description of a non-information resource without a second request is to use hash URIs.

What do HTTP URIs Identify? - Design Issues

2007-01-02

"This was a result of my being in a minority with this opinion on the Technical Architecture Group, and yet finding it the only one I could accept. This is related to TAG issue HTTPRange-14." (TBL)

TAG Issues List - httpRange-14: What is the range of the HTTP dereference function?

2007-01-02

A URI for your Favourite Pub: httpRange-14 Question from T.Heath on 2006-09-21 (semantic-web@w3.org from September 2006)

2007-01-02

Best Practice Recipes for Publishing RDF Vocabularies

2006-03-14

This document describes best practice recipes for publishing an RDFS or OWL vocabulary or ontology on the Web. The features of each recipe are clearly described, so that vocabulary or ontology creators may choose the recipe best suited to the needs of their particular situations. Each recipe contains an example configuration for use with an Apache HTTP server, although the principles involved may be adapted to other environments. The recipes are all designed to be consistent with the architecture of the Web as currently specified.