Information resources
http://www.semanlink.net/tag/information_resources
Documents tagged with Information resourcesHash URIs | W3C Blog
http://www.semanlink.net/doc/2020/11/hash_uris_%7C_w3c_blog
2020-11-07T11:15:13ZURLs in Data Primer
http://www.w3.org/TR/urls-in-data/
2013-07-11T15:45:15ZRe: Meaning of property "url" from Ed Summers on 2012-10-23 (public-vocabs@w3.org from October 2012)
http://lists.w3.org/Archives/Public/public-vocabs/2012Oct/0033.html
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 (Ed Summers)<br/>
So I'd not read too much into 'url'. It's somewhere you can put a Web
identifier for the thing being described. As conventions for this in
the Web standards community mature, we should be able to be more
precise on this. (DanBri)
2013-07-06T17:55:34ZImportant Change to HTTP semantics re. hashless URIs from Kingsley Idehen on 2013-03-24 (public-lod@w3.org from March 2013)
http://lists.w3.org/Archives/Public/public-lod/2013Mar/0115.html
2013-03-25T16:01:42ZUsing "Punning" to Answer httpRange-14 | Jeni's Musings
http://www.jenitennison.com/blog/node/170
2012-05-12T18:11:19ZTagIssue57Responses - W3C Wiki
http://www.w3.org/wiki/TagIssue57Responses
2012-04-13T17:30:48ZRe: See Other from Hugh Glaser
http://lists.w3.org/Archives/Public/public-lod/2012Mar/0339.html
2012-04-12T00:15:22ZRe: Change Proposal for HttpRange-14 from Jeni Tennison
http://lists.w3.org/Archives/Public/public-lod/2012Mar/0159.html
2012-04-11T17:11:59ZRe: Classification of ISSUE-57 change proposals - R Fielding
http://lists.w3.org/Archives/Public/www-tag/2012Mar/0220.html
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
2012-04-11T13:44:31ZISSUE-57: Mechanisms for obtaining information about the meaning of a given URI - Technical Architecture Group Tracker
http://www.w3.org/2001/tag/group/track/issues/57
2012-04-11T13:40:40ZRe: [Fwd: Reversing HTTP Range 14 and SemWeb Cool URIs decision]
http://lists.w3.org/Archives/Public/public-awwsw/2011Jan/0021.html
2012-04-11T13:40:09ZRe: Squaring the HTTP-range-14 circle
http://lists.w3.org/Archives/Public/public-lod/2011Jun/0186.html
The web of data will succeed *because* it conflates a thing and a web page about the thing.
[TimBL's answer](https://lists.w3.org/Archives/Public/public-lod/2011Jun/0262.html)
2011-12-17T15:38:05ZRepurposing the Hash Sign for the New Web
http://www.w3.org/2001/tag/2011/01/HashInURI-20110115
2011-08-11T17:36:45ZHash URIs | Jeni's Musings
http://www.jenitennison.com/blog/node/154
2011-08-11T11:30:17ZMaking AJAX Applications Crawlable - Google Code
http://code.google.com/intl/fr-FR/web/ajaxcrawling/docs/getting-started.html
2011-08-11T11:27:45ZProviding and discovering definitions of URIs
http://www.w3.org/2001/tag/awwsw/issue57/20110625/#id35291
2011-06-26T14:38:17ZhttpRange-14 Reflux - Danny Ayers : Raw Blog
http://dannyayers.com/2011/06/15/httpRange-14-Reflux
you can't squeeze a dog over the wire with HTTP, but that's just a limitation of the protocol
2011-06-15T17:46:03ZRe: Is 303 really necessary?
http://www.mail-archive.com/public-lod@w3.org/msg07196.html
2010-12-28T14:38:17ZIs 303 Really Necessary? - Internet Alchemy
http://iand.posterous.com/is-303-really-necessary
2010-11-11T15:08:16ZSemantic Web Semantics: Arcane, but Important » AI3:::Adaptive Information
http://www.mkbergman.com/?p=437
2008-04-15T15:24:02Zwiki to dbpedia with sparql
http://dbpedia.org/snorql/?query=SELECT+%3Fsubject+%3Fp%0D%0AWHERE+%7B%0D%0A++%7B+%3Fsubject+%3Fp+%3Chttp%3A%2F%2Fen.wikipedia.org%2Fwiki%2FWell-Tempered_Clavier%3E+%7D%0D%0A%7D
SELECT ?subject ?p
WHERE {
{ ?subject ?p http://en.wikipedia.org/wiki/Well-Tempered_Clavier }
}
2008-02-01T22:31:16ZAlternative to 303 response: Description-ID: header From: Tim Berners-Lee
http://lists.w3.org/Archives/Public/www-tag/2007Dec/0024.html
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.
2008-01-03T12:07:21ZURI Identity and Web Architecture Revisited
http://dfdf.inesc-id.pt/tr/web-arch
2007-11-20T21:36:46ZRe: More on distinguishing information resources from other resources Roy T. Fielding
http://lists.w3.org/Archives/Public/www-tag/2005Jun/0092.html
2007-11-20T21:32:46ZSPARQL query to find the dbPedia concept corresponding to a wikipedia page
http://dbpedia.org/snorql/?query=SELECT+%3Fsubject+%3Fp%0D%0AWHERE+%7B%0D%0A++%7B+%3Fsubject+%3Fp+%3Chttp%3A%2F%2Fde.wikipedia.org%2Fwiki%2FBerlin%3E+%7D%0D%0A%7D
SELECT ?s ?p
WHERE {
{ ?s ?p <http://en.wikipedia.org/wiki/Well_Tempered_Clavier> }
}
2007-10-13T00:28:42ZFrom Wikipedia URI-s to DBpedia URI… « Ivan’s blog
http://ivanherman.wordpress.com/2007/07/29/from-wikipedia-uri-s-to-dbpedia-uri%E2%80%A6/
2007-08-01T17:02:03Zdowhatimean.net » Content negotiation with hash URIs (long)
http://dowhatimean.net/2006/11/content-negotiation-with-hash-uris-long
2007-04-03T23:30:30ZCool URIs for the Semantic Web
http://www.dfki.uni-kl.de/~sauermann/2006/11/cooluris/
303 URIs and hash URIs
2007-04-03T23:26:43ZHTTP behaviour for SKOS Concepts from Miles, AJ \(Alistair\) on 2005-06-21 (public-esw-thes@w3.org from June 2005)
http://lists.w3.org/Archives/Public/public-esw-thes/2005Jun/0043
2007-01-03RE: [VM] content-dependent redirects in apache ... help! from Miles, AJ \(Alistair\) on 2005-10-03 (public-esw-thes@w3.org from October 2005)
http://lists.w3.org/Archives/Public/public-esw-thes/2005Oct/0006.html
2007-01-03[httpRange-14] Resolved from Roy T. Fielding on 2005-06-19 (www-tag@w3.org from June 2005)
http://lists.w3.org/Archives/Public/www-tag/2005Jun/0039.html
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.
2007-01-02What do HTTP URIs Identify? - Design Issues
http://www.w3.org/DesignIssues/HTTP-URI.html
"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)
2007-01-02TAG Issues List - httpRange-14: What is the range of the HTTP dereference function?
http://www.w3.org/2001/tag/issues.html#httpRange-14
2007-01-02Re: 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)
http://lists.w3.org/Archives/Public/semantic-web/2006Nov/0102.html
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.
2007-01-02A URI for your Favourite Pub: httpRange-14 Question from T.Heath on 2006-09-21 (semantic-web@w3.org from September 2006)
http://lists.w3.org/Archives/Public/semantic-web/2006Sep/0090.html
2007-01-02Best Practice Recipes for Publishing RDF Vocabularies
http://www.w3.org/TR/swbp-vocab-pub/
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.
2006-03-14