{"action":"created","issue":{"url":"https://api.github.com/repos/apiaryio/api-blueprint-ast/issues/35","labels_url":"https://api.github.com/repos/apiaryio/api-blueprint-ast/issues/35/labels{/name}","comments_url":"https://api.github.com/repos/apiaryio/api-blueprint-ast/issues/35/comments","events_url":"https://api.github.com/repos/apiaryio/api-blueprint-ast/issues/35/events","html_url":"https://github.com/apiaryio/api-blueprint-ast/issues/35","id":72946460,"number":35,"title":"`element` causing confusion","user":{"login":"pzurek","id":10070,"avatar_url":"https://avatars.githubusercontent.com/u/10070?v=3","gravatar_id":"","url":"https://api.github.com/users/pzurek","html_url":"https://github.com/pzurek","followers_url":"https://api.github.com/users/pzurek/followers","following_url":"https://api.github.com/users/pzurek/following{/other_user}","gists_url":"https://api.github.com/users/pzurek/gists{/gist_id}","starred_url":"https://api.github.com/users/pzurek/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/pzurek/subscriptions","organizations_url":"https://api.github.com/users/pzurek/orgs","repos_url":"https://api.github.com/users/pzurek/repos","events_url":"https://api.github.com/users/pzurek/events{/privacy}","received_events_url":"https://api.github.com/users/pzurek/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/apiaryio/api-blueprint-ast/labels/question","name":"question","color":"cc317c"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":6,"created_at":"2015-05-04T07:39:46Z","updated_at":"2015-05-21T00:30:43Z","closed_at":null,"body":"Hey guys,\r\n\r\nThis is more of a suggestion or rfc rather than an issue. I have started working on a tool (or a series of tools if all goes well) that use the AST (from drafter.js) to do some interesting things.\r\nWhen trying to understand the structure of the AST I found the duality of the term `element` really confusing and I think it could be easily fixed.\r\nSo first of all one of objects of the AST is called Element, and then secondly that objects includes a property called `element` describing the type of the element. I think it would be much more descriptive if the property was actually called `type` bringing this in line with general programming nomenclature.\r\nIf that was the case, my Go code instead of this:\r\n\r\n```go\r\ntype Element struct {\r\n\tElement string `json:\"element\"`\r\n\t...\r\n}\r\n```\r\n\r\nwould look like that:\r\n\r\n```go\r\ntype Element struct {\r\n\tType string `json:\"type\"`\r\n\t...\r\n}\r\n```\r\n\r\nThis feels so much cleaner and more descriptive to me.\r\n\r\nWhat do you think?"},"comment":{"url":"https://api.github.com/repos/apiaryio/api-blueprint-ast/issues/comments/104081125","html_url":"https://github.com/apiaryio/api-blueprint-ast/issues/35#issuecomment-104081125","issue_url":"https://api.github.com/repos/apiaryio/api-blueprint-ast/issues/35","id":104081125,"user":{"login":"zdne","id":613617,"avatar_url":"https://avatars.githubusercontent.com/u/613617?v=3","gravatar_id":"","url":"https://api.github.com/users/zdne","html_url":"https://github.com/zdne","followers_url":"https://api.github.com/users/zdne/followers","following_url":"https://api.github.com/users/zdne/following{/other_user}","gists_url":"https://api.github.com/users/zdne/gists{/gist_id}","starred_url":"https://api.github.com/users/zdne/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/zdne/subscriptions","organizations_url":"https://api.github.com/users/zdne/orgs","repos_url":"https://api.github.com/users/zdne/repos","events_url":"https://api.github.com/users/zdne/events{/privacy}","received_events_url":"https://api.github.com/users/zdne/received_events","type":"User","site_admin":false},"created_at":"2015-05-21T00:30:43Z","updated_at":"2015-05-21T00:30:43Z","body":"Either way we can ask @smizell directly for the reasoning. Also consider the compact notation which is essentially a tuple. "}}