{"action":"closed","issue":{"url":"https://api.github.com/repos/frictionlessdata/data-quality-spec/issues/3","repository_url":"https://api.github.com/repos/frictionlessdata/data-quality-spec","labels_url":"https://api.github.com/repos/frictionlessdata/data-quality-spec/issues/3/labels{/name}","comments_url":"https://api.github.com/repos/frictionlessdata/data-quality-spec/issues/3/comments","events_url":"https://api.github.com/repos/frictionlessdata/data-quality-spec/issues/3/events","html_url":"https://github.com/frictionlessdata/data-quality-spec/issues/3","id":175680680,"number":3,"title":"Reason to use numeric keys and nesting?","user":{"login":"roll","id":557395,"avatar_url":"https://avatars.githubusercontent.com/u/557395?v=3","gravatar_id":"","url":"https://api.github.com/users/roll","html_url":"https://github.com/roll","followers_url":"https://api.github.com/users/roll/followers","following_url":"https://api.github.com/users/roll/following{/other_user}","gists_url":"https://api.github.com/users/roll/gists{/gist_id}","starred_url":"https://api.github.com/users/roll/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/roll/subscriptions","organizations_url":"https://api.github.com/users/roll/orgs","repos_url":"https://api.github.com/users/roll/repos","events_url":"https://api.github.com/users/roll/events{/privacy}","received_events_url":"https://api.github.com/users/roll/received_events","type":"User","site_admin":false},"labels":[{"id":409983668,"url":"https://api.github.com/repos/frictionlessdata/data-quality-spec/labels/question","name":"question","color":"cc317c","default":true},{"id":472533762,"url":"https://api.github.com/repos/frictionlessdata/data-quality-spec/labels/review","name":"review","color":"fbca04","default":false}],"state":"closed","locked":false,"assignee":{"login":"roll","id":557395,"avatar_url":"https://avatars.githubusercontent.com/u/557395?v=3","gravatar_id":"","url":"https://api.github.com/users/roll","html_url":"https://github.com/roll","followers_url":"https://api.github.com/users/roll/followers","following_url":"https://api.github.com/users/roll/following{/other_user}","gists_url":"https://api.github.com/users/roll/gists{/gist_id}","starred_url":"https://api.github.com/users/roll/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/roll/subscriptions","organizations_url":"https://api.github.com/users/roll/orgs","repos_url":"https://api.github.com/users/roll/repos","events_url":"https://api.github.com/users/roll/events{/privacy}","received_events_url":"https://api.github.com/users/roll/received_events","type":"User","site_admin":false},"assignees":[{"login":"roll","id":557395,"avatar_url":"https://avatars.githubusercontent.com/u/557395?v=3","gravatar_id":"","url":"https://api.github.com/users/roll","html_url":"https://github.com/roll","followers_url":"https://api.github.com/users/roll/followers","following_url":"https://api.github.com/users/roll/following{/other_user}","gists_url":"https://api.github.com/users/roll/gists{/gist_id}","starred_url":"https://api.github.com/users/roll/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/roll/subscriptions","organizations_url":"https://api.github.com/users/roll/orgs","repos_url":"https://api.github.com/users/roll/repos","events_url":"https://api.github.com/users/roll/events{/privacy}","received_events_url":"https://api.github.com/users/roll/received_events","type":"User","site_admin":false}],"milestone":null,"comments":5,"created_at":"2016-09-08T07:08:04Z","updated_at":"2016-11-02T09:12:37Z","closed_at":"2016-11-02T09:12:37Z","body":"@pwalsh \nI'm starting to work on goodtables.next more closely and this spec is a great source for me. But I have a few questions.\n\nFirst is why to use this numbered keys instead of unique identifier of error. I don't fully understand where this numbers could be used because showing to user things like `error: structure-3` in my opinion less usable then something like `error: structure-duplicate-row`. We have an experience working with linters and I suppose all don't like when they starting to answer to us with some strange numeric codes (ok if you have 200 different error it could be explained). \n\nSecond is `format/structure/schema` nesting. I see here also room for simplification. We have like around 30 errors I suppose we could to write it just is simplest dict form like:\n\n```\nunknown-format:\n    type: format\n    ...\nunknown-encoding:\n    type: format\n    ...\nblank-header:\n    type: structure\n    ...\nmissing-headers:\n    type: schema\n    ...\npattern-constraint:\n   type: schema\n```\n\nIt also allow to introduce some **unified language** between users and implementations e.g. there will be `check_missing_headers` or `checkPatternConstraint` (in js). Or in some validator - `validate(checks={'missing-headers': True})`.\n\nAlso do you plan tools could use this spec programaticaly? If yes then my comments are even more actual I suppose.\n"}}
{"actor":{"display_login":"roll"}}