{"action":"created","issue":{"url":"https://api.github.com/repos/w3c/csvw/issues/691","labels_url":"https://api.github.com/repos/w3c/csvw/issues/691/labels{/name}","comments_url":"https://api.github.com/repos/w3c/csvw/issues/691/comments","events_url":"https://api.github.com/repos/w3c/csvw/issues/691/events","html_url":"https://github.com/w3c/csvw/issues/691","id":95801104,"number":691,"title":"At Risk feature during CR: usage or not .well-known","user":{"login":"iherman","id":520723,"avatar_url":"https://avatars.githubusercontent.com/u/520723?v=3","gravatar_id":"","url":"https://api.github.com/users/iherman","html_url":"https://github.com/iherman","followers_url":"https://api.github.com/users/iherman/followers","following_url":"https://api.github.com/users/iherman/following{/other_user}","gists_url":"https://api.github.com/users/iherman/gists{/gist_id}","starred_url":"https://api.github.com/users/iherman/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/iherman/subscriptions","organizations_url":"https://api.github.com/users/iherman/orgs","repos_url":"https://api.github.com/users/iherman/repos","events_url":"https://api.github.com/users/iherman/events{/privacy}","received_events_url":"https://api.github.com/users/iherman/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/w3c/csvw/labels/For%20Proposed%20Rec","name":"For Proposed Rec","color":"006b75"},{"url":"https://api.github.com/repos/w3c/csvw/labels/NonWG","name":"NonWG","color":"fad8c7"}],"state":"open","locked":false,"assignee":null,"milestone":{"url":"https://api.github.com/repos/w3c/csvw/milestones/1","html_url":"https://github.com/w3c/csvw/milestones/Proposed%20Rec","labels_url":"https://api.github.com/repos/w3c/csvw/milestones/1/labels","id":1203242,"number":1,"title":"Proposed Rec","description":null,"creator":{"login":"iherman","id":520723,"avatar_url":"https://avatars.githubusercontent.com/u/520723?v=3","gravatar_id":"","url":"https://api.github.com/users/iherman","html_url":"https://github.com/iherman","followers_url":"https://api.github.com/users/iherman/followers","following_url":"https://api.github.com/users/iherman/following{/other_user}","gists_url":"https://api.github.com/users/iherman/gists{/gist_id}","starred_url":"https://api.github.com/users/iherman/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/iherman/subscriptions","organizations_url":"https://api.github.com/users/iherman/orgs","repos_url":"https://api.github.com/users/iherman/repos","events_url":"https://api.github.com/users/iherman/events{/privacy}","received_events_url":"https://api.github.com/users/iherman/received_events","type":"User","site_admin":false},"open_issues":7,"closed_issues":1,"state":"open","created_at":"2015-07-11T04:33:28Z","updated_at":"2015-09-23T14:47:54Z","due_on":null,"closed_at":null},"comments":2,"created_at":"2015-07-18T07:48:23Z","updated_at":"2015-09-26T23:55:36Z","closed_at":null,"body":"Just opening a separate issue related to the \"At Risk\" feature in current CR. It used to be issue #555 leading to the official CR draft, taking it a separate issue now on whether the feature is to be kept or not."},"comment":{"url":"https://api.github.com/repos/w3c/csvw/issues/comments/143506047","html_url":"https://github.com/w3c/csvw/issues/691#issuecomment-143506047","issue_url":"https://api.github.com/repos/w3c/csvw/issues/691","id":143506047,"user":{"login":"dbooth-boston","id":5123226,"avatar_url":"https://avatars.githubusercontent.com/u/5123226?v=3","gravatar_id":"","url":"https://api.github.com/users/dbooth-boston","html_url":"https://github.com/dbooth-boston","followers_url":"https://api.github.com/users/dbooth-boston/followers","following_url":"https://api.github.com/users/dbooth-boston/following{/other_user}","gists_url":"https://api.github.com/users/dbooth-boston/gists{/gist_id}","starred_url":"https://api.github.com/users/dbooth-boston/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dbooth-boston/subscriptions","organizations_url":"https://api.github.com/users/dbooth-boston/orgs","repos_url":"https://api.github.com/users/dbooth-boston/repos","events_url":"https://api.github.com/users/dbooth-boston/events{/privacy}","received_events_url":"https://api.github.com/users/dbooth-boston/received_events","type":"User","site_admin":false},"created_at":"2015-09-26T23:55:36Z","updated_at":"2015-09-26T23:55:36Z","body":"I believe the .well-known feature should be dropped from the\r\nCSVW specification -- or in the very least, users should be\r\n*discouraged* from using it -- for at least the following\r\nreasons:\r\n\r\n1. The RFC 5785 .well-known mechanism is inappropriate for\r\nthis use.  It is intended for **site-wide** policy data,\r\nand that is *not* the granularity of control that is needed\r\nor desired for file- or directory-specific CSV metadata.\r\n\r\n2. The .well-known feature is dangerous because a CSV author\r\nmay publish a CSV file on a large site that specifies\r\none metadata file pattern in its .well-known file (or\r\nhas no .well-known file), and later that .well-known\r\nfile may be changed by the site administrator, without\r\nthe CSV file owner's knowledge, to specify a different\r\npattern, thus causing CSVW processors to either not find\r\nthe metadata file or find a different metadata file than\r\nthe CSV author intended.  This scenario is described here:\r\nhttps://lists.w3.org/Archives/Public/www-tag/2015Jul/0007.html\r\n\r\n3. This use of .well-known violates the intent of RFC5785.\r\nSection 1.1 (Appropriate Use of Well-Known URIs) explicitly\r\nstates:\r\n\r\n   \"well-known URIs are not intended\r\n    for general information retrieval or establishment of large\r\n    URI namespaces on the Web.  Rather, they are designed to\r\n    facilitate discovery of information on a site **when it\r\n    isn't practical to use other mechanisms**\"   [my emphasis]\r\n\r\nBut in this case, it clearly *is* practical to use other\r\nmechanisms.  The CSVW spec already provides at least three\r\nalternate mechanisms for associating CSV metadata with CSV data:\r\n(a) a Link header, which can point from a CSV data URI to its\r\ncorresponding CSV metadata URI; (b) standard CSV metadata URI\r\npatterns; and (c) the ability to publicize non-standard URIs\r\nof CSV metadata documents that link to their corresponding CSV\r\ndata files.  (To clarify that last mechanism, one mode of use\r\nis for a user to start with a CSV data URI, and from that seek\r\nthe corresponding CSV metadata.  But another mode of use is\r\nfor a user to start with the CSV metadata URI, and from that\r\nlocate the corresponding CSV data.  To facilitate that mode\r\nof use, data publishers have the option of publicizing their\r\nCSV metadata URIs along with their CSV data, so that users\r\ncan easily find the CSV metadata.  Given the CSV metadata,\r\nCSVW processor can then automatically locate the corresponding\r\nCSV data, because the CSV metadata file explicitly links to\r\nits corresponding data file.)\r\n\r\n4. The CSVW working group's decision to include this feature\r\nwas based on deference to the TAG's advice, which which\r\nwas flawed based on incorrect assumptions.  As explained in\r\nsome detail in the threads below, the use of .well-known is\r\nNOT needed to avoid harmful URI squatting as the TAG had\r\nassumed when it considered this issue.  The fact that the\r\nTAG has not taken the time to correct that mistake is NOT\r\na good reason for the CSVW working group to perpetuate it.\r\nhttps://lists.w3.org/Archives/Public/www-tag/2015Jun/0011.html\r\nhttps://www.w3.org/Search/Mail/Public/search?keywords=booth&hdr-1-name=subject&hdr-1-query=.well-known&index-grp=Public_FULL&index-type=t&type-index=www-tag\r\nhttps://www.w3.org/Search/Mail/Public/search?keywords=booth&hdr-1-name=subject&hdr-1-query=.well-known&index-grp=Public_FULL&index-type=t&type-index=public-csv-wg\r\n\r\n5. When a poll was sent to public-csv-wg@w3.org asking about\r\npotential use of the .well-known feature, NOBODY indicated\r\nthat they needed and intended to use that feature.  We should\r\nnot include a feature with so little demonstrated need.\r\nhttps://lists.w3.org/Archives/Public/public-csv-wg/2015Jun/0085.html\r\n"}}