{"action":"closed","issue":{"url":"https://api.github.com/repos/apiaryio/api-blueprint/issues/38","labels_url":"https://api.github.com/repos/apiaryio/api-blueprint/issues/38/labels{/name}","comments_url":"https://api.github.com/repos/apiaryio/api-blueprint/issues/38/comments","events_url":"https://api.github.com/repos/apiaryio/api-blueprint/issues/38/events","html_url":"https://github.com/apiaryio/api-blueprint/issues/38","id":21861776,"number":38,"title":"Support for Specific Metadata","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},"labels":[{"url":"https://api.github.com/repos/apiaryio/api-blueprint/labels/feature","name":"feature","color":"3C7ABD"}],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":16,"created_at":"2013-10-30T21:49:37Z","updated_at":"2015-12-01T12:52:47Z","closed_at":"2015-12-01T12:52:47Z","body":"Various toolings might have a need for a tooling-specific metadata at different point in blueprint. A solution would be to add a syntax construct that would be expected wherever a Markdown formatted discussion is expected and that would provide (potentially recursive) \"key: value\" notation. \r\n\r\nE.g.:\r\n\r\n```\r\n# API \r\nAPI Description\r\n\r\n+ Metadata\r\n    + Key: `Value`\r\n\r\n# Resource [/resource]\r\nResource Description \r\n\r\n+ Metadata\r\n    + Key: `Value`\r\n    + Key2:\r\n        + Key3: `Value`\r\n\r\n```\r\n\r\nWhich would be reflected in AST like\r\n\r\n```YAML\r\n_version: 1.0\r\nmetadata:\r\nname: API\r\ndescription: \"API Description\\n\\n\"\r\nmetadata:\r\n    key: Value\r\nresourceGroups:\r\n- name:\r\n  description:\r\n  metadata:\r\n  resources:\r\n  - name: Resource\r\n    description: \"Resource Description \\n\\n\"\r\n    metadata:\r\n        key: Value    \r\n        key2:\r\n            key3: Value \r\n    uriTemplate: /resource\r\n    model:\r\n    parameters:\r\n    headers:\r\n    actions:\r\n```"}}