{"action":"opened","issue":{"url":"https://api.github.com/repos/openspending/fiscal-data-package/issues/43","labels_url":"https://api.github.com/repos/openspending/fiscal-data-package/issues/43/labels{/name}","comments_url":"https://api.github.com/repos/openspending/fiscal-data-package/issues/43/comments","events_url":"https://api.github.com/repos/openspending/fiscal-data-package/issues/43/events","html_url":"https://github.com/openspending/fiscal-data-package/issues/43","id":108061826,"number":43,"title":"Nesting dimensions under mapping","user":{"login":"pwalsh","id":791678,"avatar_url":"https://avatars.githubusercontent.com/u/791678?v=3","gravatar_id":"","url":"https://api.github.com/users/pwalsh","html_url":"https://github.com/pwalsh","followers_url":"https://api.github.com/users/pwalsh/followers","following_url":"https://api.github.com/users/pwalsh/following{/other_user}","gists_url":"https://api.github.com/users/pwalsh/gists{/gist_id}","starred_url":"https://api.github.com/users/pwalsh/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/pwalsh/subscriptions","organizations_url":"https://api.github.com/users/pwalsh/orgs","repos_url":"https://api.github.com/users/pwalsh/repos","events_url":"https://api.github.com/users/pwalsh/events{/privacy}","received_events_url":"https://api.github.com/users/pwalsh/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-09-24T05:36:41Z","updated_at":"2015-09-24T05:36:41Z","closed_at":null,"body":"https://github.com/openspending/fiscal-data-package/blob/master/spec/index.md#details\r\n\r\nWe nest measures `mapping.measures`. I think we should do the same for dimensions: `mapping.dimensions`. \r\n\r\nIt is more consistent in terms of the spec, and means that code that works with the spec does not need to  special case \"measures\" in order to work out what under `mapping` is a dimension.\r\n\r\ncc @trickvi "}}