On Fri, 9 Feb 2007 Booth, David (HP Software - Boston) wrote:
> I'm curious why you are treating this case so differently from the
> case of finding information about an information resource. I
> assume it is because with information resources you are only
> interested in information from that in
> From: Jonathan Rees [mailto:[EMAIL PROTECTED]
>
> Doing HTTP operations on an information resource, while abstractly
> similar to answering SPARQL queries relating to it (in either case you
> are learning something), seems to have a different feel given present
> technology. The protocol used
Doing HTTP operations on an information resource, while abstractly
similar to answering SPARQL queries relating to it (in either case you
are learning something), seems to have a different feel given present
technology. The protocol used is HTTP and the stuff you get has types
(e.g. image, PDF) t
> From: [EMAIL PROTECTED]
>
> >> In your view, how would one find
> >> information (or represent the information needed to find
> >> information) about a non-informationresource
>
> I think parallel querying of Sparql endpoints could be an
> interesting solution. . . . .
I'm curious why you ar
>> In your view, how would one find
>> information (or represent the information needed to find
>> information) about a non-informationresource
I think parallel querying of Sparql endpoints could be an interesting solution.
To get additional information about a non-information resource (say, a
