Re: Conforming is such sweet sorrow

>> Of course, I am assuming,
>>
>> awww:InformationResource owl:disjointWith awww:NonInformationResource.
>
> The AWWW does not talk about Non-information resources.
> You would have to define it is you wanted to use it in conversation.
Clearly, Pat is not an Information Resource.  AWWW doesn't not talk 
about Pat. Neither about genes, molecule, cars, hard copy books, etc., 
etc., how useful will the web be then?

My point of view is: AWWW only delivers information in documents. Any 
information about anything will do.
>> Because if it is not true, i.e., there is something that can be 
>> either IR or non-IR, then the definition of IR seems already 
>> irrelevant (at least if we don't find another 30x code for that mixed 
>> category with regard to httpRange-14).
>>
>> As everything in the web is a rdfs:Resource, either (1) or (2) seems 
>> running into a paradox.  (I am not a logician.  If I am wrong, please 
>> point it out for me.)
>
> 1 is false.
> 2 is not defined in the awww.
Will (2) ever be defined in the AWWW?  If not, people must be better 
safe than sorry to front every resource with a 303 because we can never 
be sure when and where his/her "document" will be judged as a 
FalseDocument.  Sure, hashing it everywhere *avoided* the question but 
it still doesn't answer the question - what is "information resource", 
yes? 

Doesn't that mean that the web will work just fine without answering the 
question of what is information resource? In other words, whether 
something is an information resource or not doesn't really matter to the 
web, right?

Then, why not simply changing our interpretation of the architecture of 
the web and make everyone's life easier, hash or slash, does it really 
matter at all?

Xiaoshu

Received on Sunday, 25 November 2007 21:41:14 UTC