- From: Sandro Hawke <sandro@w3.org>
- Date: Tue, 07 May 2013 19:15:39 -0400
- To: Public GLD WG <public-gld-wg@w3.org>
- Message-ID: <51898B1B.5010706@w3.org>
Bernadette and I were working on actually publishing the Glossary, which
the group approved for publication, and I noticed a little problem:
86. Resource
A resource is anything that can be addressed by a Unified Resource
Identifier (URI)
<file:///home/sandro/Repos/gld/glossary/diff.html#uniform-resource-identifiers>.
...
93. Resource
A resource is a network data object or service that can be
identified by an HTTP URI. Resources may be available in multiple
representations (e.g. multiple languages, data formats, size, and
resolutions) or vary in other ways. See details from RFC 2616bis for
details on Uniform Resource Identifiers. See details from RFC
2616bis for details on Uniform Resource Identifiers.
The definition of Resource is something I've thought about more than
most people have thought about food. I suggest we call the second one
"Web Resource", and explain, like this:
*Resource*
(Not to be confused with _Web Resource_) An entity. Saying that
something is a resource says nothing at all about it, because by the
definition of the term, everything is a resource. For more
details see Uniform Resource Identifier (URI): Generic Syntax (RFC
3986) [1] and Resource Description Framework (RDF) 1.1 Concepts [2].
*Web Resource*
Anything which is addressed by a URL; roughly speaking, a web page.
Examples include: an HTML web page, an image offered by a web
server, or a dataset available for access at some URL. A resource
may change its state over time and have different representations of
the same state. For example, a webcam might offer both JPEG and PNG
versions of its current image, at the same URL, using content
negotiation, or an RDF database might be accessed at one URL using
multiple syntaxes, such as RDFa, JSON-LD, and Turtle. For more
details see Hypertext Transfer Protocol -- HTTP/1.1 [3]
Sometimes Web Resources are just called "Resources". In some
contexts, this can cause unnecessary confusion. The difference is
related to the distinction between URLs (which identify Web
Resources) and URIs (which identify Resources in general), as
discussed in http://tools.ietf.org/html/rfc3305#page-3
[1] http://tools.ietf.org/html/rfc3986
[2] http://www.w3.org/TR/rdf11-concepts/#resources-and-statements
[3]
http://www.w3.org/Protocols/HTTP/1.1/rfc2616bis/draft-lafon-rfc2616bis-04.html#intro.terminology
I hope that works for folks. Bernadette made some other changes, so
we're going to ask the WG for approval again before publishing. I'll be
sending along a pointer to the new version and the diffs once I have it
passing pubrules.
-- Sandro
Received on Tuesday, 7 May 2013 23:15:47 UTC