{"action":"created","issue":{"url":"https://api.github.com/repos/w3c/dpub-pwp-ucr/issues/124","repository_url":"https://api.github.com/repos/w3c/dpub-pwp-ucr","labels_url":"https://api.github.com/repos/w3c/dpub-pwp-ucr/issues/124/labels{/name}","comments_url":"https://api.github.com/repos/w3c/dpub-pwp-ucr/issues/124/comments","events_url":"https://api.github.com/repos/w3c/dpub-pwp-ucr/issues/124/events","html_url":"https://github.com/w3c/dpub-pwp-ucr/issues/124","id":179661458,"number":124,"title":"6.2 Streamlining a PWP","user":{"login":"marcoscaceres","id":870154,"avatar_url":"https://avatars.githubusercontent.com/u/870154?v=3","gravatar_id":"","url":"https://api.github.com/users/marcoscaceres","html_url":"https://github.com/marcoscaceres","followers_url":"https://api.github.com/users/marcoscaceres/followers","following_url":"https://api.github.com/users/marcoscaceres/following{/other_user}","gists_url":"https://api.github.com/users/marcoscaceres/gists{/gist_id}","starred_url":"https://api.github.com/users/marcoscaceres/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/marcoscaceres/subscriptions","organizations_url":"https://api.github.com/users/marcoscaceres/orgs","repos_url":"https://api.github.com/users/marcoscaceres/repos","events_url":"https://api.github.com/users/marcoscaceres/events{/privacy}","received_events_url":"https://api.github.com/users/marcoscaceres/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2016-09-28T01:49:23Z","updated_at":"2016-09-28T09:07:36Z","closed_at":null,"body":"\r\n> Req. 26: Manifest should make it possible to provide a streamlined access to disjoint parts of the publication.\r\n\r\nI don't see why a manifest would have anything at all to do with this. Sure, one could do this via a manifest, but that's the requirement is not dependent on a manifest.  "},"comment":{"url":"https://api.github.com/repos/w3c/dpub-pwp-ucr/issues/comments/250112946","html_url":"https://github.com/w3c/dpub-pwp-ucr/issues/124#issuecomment-250112946","issue_url":"https://api.github.com/repos/w3c/dpub-pwp-ucr/issues/124","id":250112946,"user":{"login":"iherman","id":520723,"avatar_url":"https://avatars.githubusercontent.com/u/520723?v=3","gravatar_id":"","url":"https://api.github.com/users/iherman","html_url":"https://github.com/iherman","followers_url":"https://api.github.com/users/iherman/followers","following_url":"https://api.github.com/users/iherman/following{/other_user}","gists_url":"https://api.github.com/users/iherman/gists{/gist_id}","starred_url":"https://api.github.com/users/iherman/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/iherman/subscriptions","organizations_url":"https://api.github.com/users/iherman/orgs","repos_url":"https://api.github.com/users/iherman/repos","events_url":"https://api.github.com/users/iherman/events{/privacy}","received_events_url":"https://api.github.com/users/iherman/received_events","type":"User","site_admin":false},"created_at":"2016-09-28T09:07:36Z","updated_at":"2016-09-28T09:07:36Z","body":"\n> On 28 Sep 2016, at 03:52, Marcos Cáceres <notifications@github.com> wrote:\n> \n> In fact, the examples for this section show that this use case is not dependent on the manifest (or even any metadata) at all.\n> \n> Also \"The App Package must...\"? That's a new one :) But seriously, how the application manifests its ToC, etc. is application dependent and not dependent on \"metadata\".\n> \n\nFirst of all, we are back to the terminology issue; the use case do not say that it must be part of the manifest file itself. See also my remark on the usage of the term metadata… we have to agree on a neutral term.\n\nThe only thing this use case says is that there may be more than one ToC-s, and not only one default reading order, and it is up to the user to choose among those. I do not see the problem with that.\n\n\n\n"}}
{"actor":{"display_login":"iherman"}}