Re: Use of .well-known for CSV metadata: More harm than good
Ivan Herman <[email protected]> Mon, 22 Jun 2015 12:19:58 +0200
| Newsgroups | gmane.org.w3c.tag |
|---|---|
| Message-ID | <[email protected]> |
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). Ivan ---- Ivan Herman, W3C Digital Publishing Activity Lead Home: http://www.w3.org/People/Ivan/ mobile: +31-641044153 ORCID ID: http://orcid.org/0000-0003-0782-2704
signature.asc
(application/pgp-signature, 203 B)
-----BEGIN PGP SIGNATURE----- Comment: GPGTools - http://gpgtools.org iEYEARECAAYFAlWH4U4ACgkQdR3hQzQ/Gj0nogCgrMUiZzCEL3H0wENEXVuZs9Xw pOgAn3dgAdcP3LiHrPbDXM1/iKtWXGXw =gtDp -----END PGP SIGNATURE-----