{"action":"created","issue":{"url":"https://api.github.com/repos/securitytxt/security-txt/issues/12","repository_url":"https://api.github.com/repos/securitytxt/security-txt","labels_url":"https://api.github.com/repos/securitytxt/security-txt/issues/12/labels{/name}","comments_url":"https://api.github.com/repos/securitytxt/security-txt/issues/12/comments","events_url":"https://api.github.com/repos/securitytxt/security-txt/issues/12/events","html_url":"https://github.com/securitytxt/security-txt/issues/12","id":250170769,"number":12,"title":"Use JSON?","user":{"login":"oreoshake","id":448516,"avatar_url":"https://avatars2.githubusercontent.com/u/448516?v=4","gravatar_id":"","url":"https://api.github.com/users/oreoshake","html_url":"https://github.com/oreoshake","followers_url":"https://api.github.com/users/oreoshake/followers","following_url":"https://api.github.com/users/oreoshake/following{/other_user}","gists_url":"https://api.github.com/users/oreoshake/gists{/gist_id}","starred_url":"https://api.github.com/users/oreoshake/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/oreoshake/subscriptions","organizations_url":"https://api.github.com/users/oreoshake/orgs","repos_url":"https://api.github.com/users/oreoshake/repos","events_url":"https://api.github.com/users/oreoshake/events{/privacy}","received_events_url":"https://api.github.com/users/oreoshake/received_events","type":"User","site_admin":true},"labels":[{"id":667522732,"url":"https://api.github.com/repos/securitytxt/security-txt/labels/question","name":"question","color":"cc317c","default":true}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":24,"created_at":"2017-08-14T22:21:12Z","updated_at":"2017-10-10T19:20:58Z","closed_at":null,"author_association":"NONE","body":"While generating, understanding, and parsing this format is not hard would you consider using JSON as a data format? When converted to a JSON object, it's still easy for a human to read and all computers can naturally digest/generate it."},"comment":{"url":"https://api.github.com/repos/securitytxt/security-txt/issues/comments/335579786","html_url":"https://github.com/securitytxt/security-txt/issues/12#issuecomment-335579786","issue_url":"https://api.github.com/repos/securitytxt/security-txt/issues/12","id":335579786,"user":{"login":"davidmays","id":1510140,"avatar_url":"https://avatars2.githubusercontent.com/u/1510140?v=4","gravatar_id":"","url":"https://api.github.com/users/davidmays","html_url":"https://github.com/davidmays","followers_url":"https://api.github.com/users/davidmays/followers","following_url":"https://api.github.com/users/davidmays/following{/other_user}","gists_url":"https://api.github.com/users/davidmays/gists{/gist_id}","starred_url":"https://api.github.com/users/davidmays/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/davidmays/subscriptions","organizations_url":"https://api.github.com/users/davidmays/orgs","repos_url":"https://api.github.com/users/davidmays/repos","events_url":"https://api.github.com/users/davidmays/events{/privacy}","received_events_url":"https://api.github.com/users/davidmays/received_events","type":"User","site_admin":false},"created_at":"2017-10-10T19:20:57Z","updated_at":"2017-10-10T19:20:57Z","author_association":"NONE","body":"I think the value of JSON is in providing an extensible structured data\nformat that is easily parseable by both machines (using standard libraries)\nand humans.\n\nThat said, I still believe semantic HTML has more utility than either plain\ntext or JSON, for both machine and human readability. Things like unfurling\nare already natively supported, as is search engine indexing in useful ways.\n\n\nOn Tue, Oct 10, 2017 at 12:42 PM, Scott Walsh <notifications@github.com>\nwrote:\n\n>\n>    - KVP is exactly what proposal embraces.\n>    - You can have granularity due to nesting, similar to the Location\n>    directive without having to cascade changes and manage multiple files. This\n>    eases the management burden to one location. YAML, TOML, and XML would all\n>    provide this as well.\n>    - When you would like to provide multiple values, you can use a list,\n>    rather than multiple directives, or end up in regex parsing hell.\n>    Processing a list of 1 or 1 million follow the exact same pattern.\n>    - Adoption. As much fun as writing parsers are, why do it again?\n>\n> Again, I feel that machines will read this file if the standard is\n> accepted at a ratio of 1000:1, if not more.\n>\n> If feels as if this has already been decided, so I'll focus my efforts\n> elsewhere.\n>\n> —\n> You are receiving this because you commented.\n> Reply to this email directly, view it on GitHub\n> <https://github.com/securitytxt/security-txt/issues/12#issuecomment-335569327>,\n> or mute the thread\n> <https://github.com/notifications/unsubscribe-auth/ABcK_Ajqs_p0YBIso6r6tMdbczmf2Zyjks5sq7qlgaJpZM4O2-GT>\n> .\n>\n"}}
{"actor":{"display_login":"davidmays"}}