Re: Towards a precise, reliable definition of "information resource"

Hello Patrick,

This doesn't seem entirely consistent with:

From:  
http://lists.w3.org/Archives/Public/public-webarch-comments/2004OctDec/0097.html

> I am not satisfied with this outcome, but I also do not intend to 
> consume more of my own time in this matter. My concerns are a matter 
> of public record. I leave it to the TAG to decide whether to reflect 
> any of the actual progress made in online discussions in the actual 
> text of AWWW, or to leave the issue unresolved.

or more recently (abeit with stated preconditions)  from 
http://lists.w3.org/Archives/Public/public-webarch-comments/2004OctDec/0097.html

> The inclusion of the definition of "information resource" (albeit 
> imperfect) is reasonable, as the mere presence of a definition of such 
> a class of resources does not, or at least should not, imply that the 
> range of resources which http: URIs (or any other form of URI) can 
> identify is constrained solely to such a class of "information 
> resources". (though, IMO, the definition could be completely omitted 
> without AWWW incuring any notable loss of utility or coherence)

This thread has grown long, folks are tired and need space to think (for 
themselves). Please let them have it.

Thanks,

Stuart
--


Patrick.Stickler@nokia.com wrote:

>Leaving all issues about the necessity, utility, and
>significance of defining a class of "information resources"
>aside, I recommend to the TAG that it adopt a similar
>approach as employed by RDF Core WG regarding the use of 
>test cases to facilitate capturing concensus, by constructing
>two lists: one that contains examples of resources that are 
>agreed to be information resources, and one that contains
>examples of resources that are agreed not to be information
>resources.
>
>I think a total of 20-25 resources per list should be sufficient.
>
>The definition of the class "information resource" would
>then be expressed/refined so that all agree that it reflects 
>precisely the partitioning of those two lists.
>
>Those two lists could (or should) be included in whatever
>document officially presents that definition (not necessarily,
>even if likely, AWWW) to reinforce the meaning of the
>definition.
>
>Furthermore, each resource in those two lists could be linked
>to discussion about why it is or is not an information resource.
> 
>Thus, if someone wonders if some resource is an information 
>resource, and they are not sure based on the text of the
>definition, they can look at those two lists and see which
>resources in those two lists most closely correspond to the 
>resource in question and perhaps deduce a reasonably reliable 
>answer to their question by such a comparison.
>
>Regards,
>
>Patrick
>
>
>--
>
>Patrick Stickler
>Nokia, Finland
>patrick.stickler@nokia.com
> 
>
>  
>

Received on Thursday, 21 October 2004 13:12:24 UTC