Re: Use of .well-known for CSV metadata: More harm than good

On 06/22/2015 06:19 AM, Ivan Herman wrote:
> Just a minor fact:
>
>> On 22 Jun 2015, at 05:08 , Mark Nottingham <[email protected]> wrote:
>>
> <snip>
>
>> You can specify a heuristic for the 404 to be interpreted on the
>> *client* side; it tells consumers that if there's a 404 without
>> freshness information, they can assume a specified default.
>
> The CSVW mechanism planned for the .well-known case includes this. If
> the .well-known file is not available, there is a default defined in
> the spec (which leads to CSV metadata files residing in the same
> directory as the original CSV file).

I think Mark was talking about specifying a default *caching* behavior 
for the client to assume, if there's a 404 without freshness 
information.  CSVW does not specify any default *caching* behavior for a 
404.

David Booth