Re: def'n of resource?

Hi Sandro,
The editors have folded in all comments received in relation to the LD Glossary.  Please see latest version. [1] 

For Thursday's telecon, would you create a diff previously approved for publication (April) & the May 7th (current).  Also, need a new Overview.html file run through PubRules.  I'm done until we get further feedback.  Thanks for your help on this.
---

Regarding "Resource", I've simplified to include only one definition.  In keeping with my new mantra, "keep it simple", how does this this sit with you & others? 
89. Resource

In an RDF context, a resource can be anything that an RDF graph describes. A resource can be addressed by a Unified Resource Identifier (URI). 


Keep in mind that this LD Glossary is a starting point for those new to Linked Data.  We don't want to scare people, it is the 'welcome basket' not the definitive guide for the working LD expert (which is found elsewhere on the W3C site).

Cheers,
Bernadette

[1] https://dvcs.w3.org/hg/gld/raw-file/default/glossary/index.html

Sandro wrote:
>  I've thought about more than most people have thought about food


PS.  Clearly you haven't met my 15 year old son who pretty much only thinks about food ;-)


On May 7, 2013, at 7:15 PM, Sandro Hawke <sandro@w3.org> wrote:

> 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). 
> 
> ...
> 
> 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
>