{"action":"opened","issue":{"url":"https://api.github.com/repos/ev3dev/ev3dev-lang/issues/51","labels_url":"https://api.github.com/repos/ev3dev/ev3dev-lang/issues/51/labels{/name}","comments_url":"https://api.github.com/repos/ev3dev/ev3dev-lang/issues/51/comments","events_url":"https://api.github.com/repos/ev3dev/ev3dev-lang/issues/51/events","html_url":"https://github.com/ev3dev/ev3dev-lang/issues/51","id":69060828,"number":51,"title":"Could we utilize the attribute documentation from the device driver repo?","user":{"login":"WasabiFan","id":3310349,"avatar_url":"https://avatars.githubusercontent.com/u/3310349?v=3","gravatar_id":"","url":"https://api.github.com/users/WasabiFan","html_url":"https://github.com/WasabiFan","followers_url":"https://api.github.com/users/WasabiFan/followers","following_url":"https://api.github.com/users/WasabiFan/following{/other_user}","gists_url":"https://api.github.com/users/WasabiFan/gists{/gist_id}","starred_url":"https://api.github.com/users/WasabiFan/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/WasabiFan/subscriptions","organizations_url":"https://api.github.com/users/WasabiFan/orgs","repos_url":"https://api.github.com/users/WasabiFan/repos","events_url":"https://api.github.com/users/WasabiFan/events{/privacy}","received_events_url":"https://api.github.com/users/WasabiFan/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-04-17T04:31:31Z","updated_at":"2015-04-17T04:31:31Z","closed_at":null,"body":"Currently, the ev3dev.org docs are generated based on data placed in the source files of the ev3dev drivers in the [lego-linux-drivers repo](https://github.com/ev3dev/lego-linux-drivers). The comments in the source files are translated into the documentation pages via @dlech's Python script.\r\n\r\nI was thinking that this is similar in concept to what we are doing with our own JSON spec system, only we manually update our spec based on those docs changes. I was wondering what the technical limitations would be for us to generate our spec off of the same source (the comments in those source files). Basically, my query comes down to this:\r\n- Is the data in those source files structured, or is it just a markdown list?\r\n- Is all the data that our system needs maintained in that source already (property name, type, accessibility)?\r\n\r\nMy hope would be that, if I could get my script to pull from that data, we wouldn't be left with nearly as many little discrepancies between the kernel functionality and what I put into the spec. "}}