{"action":"created","issue":{"url":"https://api.github.com/repos/w3c/dpub-pwp-ucr/issues/110","repository_url":"https://api.github.com/repos/w3c/dpub-pwp-ucr","labels_url":"https://api.github.com/repos/w3c/dpub-pwp-ucr/issues/110/labels{/name}","comments_url":"https://api.github.com/repos/w3c/dpub-pwp-ucr/issues/110/comments","events_url":"https://api.github.com/repos/w3c/dpub-pwp-ucr/issues/110/events","html_url":"https://github.com/w3c/dpub-pwp-ucr/issues/110","id":176805898,"number":110,"title":"3.3 Constituent Resources","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":31,"created_at":"2016-09-14T03:31:18Z","updated_at":"2016-09-30T16:55:57Z","closed_at":null,"body":"> Req. 16: The information regarding the constituent resources of a PWP must be easily discovered\r\n\r\nThe case for this requirement is extremely weak. \r\n\r\nIn particular, no clear justification is given for:  \r\n\r\n> It is therefore necessary for the reading system to have an easy access to the list of constituent resources, and some of their characteristics like their media types or sizes.\r\n\r\nIt just gives some hand-wavy non-justification in the sentence before, about things being \"prohibitive\". \r\n\r\nIt almost feels like this requirement has been snuck in to justify the inclusion of some manifest file format for the packaging format (which seems pretty clear is trying to  underpin/undermine? the requirements of this document).  "},"comment":{"url":"https://api.github.com/repos/w3c/dpub-pwp-ucr/issues/comments/250796382","html_url":"https://github.com/w3c/dpub-pwp-ucr/issues/110#issuecomment-250796382","issue_url":"https://api.github.com/repos/w3c/dpub-pwp-ucr/issues/110","id":250796382,"user":{"login":"lrosenthol","id":5074741,"avatar_url":"https://avatars.githubusercontent.com/u/5074741?v=3","gravatar_id":"","url":"https://api.github.com/users/lrosenthol","html_url":"https://github.com/lrosenthol","followers_url":"https://api.github.com/users/lrosenthol/followers","following_url":"https://api.github.com/users/lrosenthol/following{/other_user}","gists_url":"https://api.github.com/users/lrosenthol/gists{/gist_id}","starred_url":"https://api.github.com/users/lrosenthol/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/lrosenthol/subscriptions","organizations_url":"https://api.github.com/users/lrosenthol/orgs","repos_url":"https://api.github.com/users/lrosenthol/repos","events_url":"https://api.github.com/users/lrosenthol/events{/privacy}","received_events_url":"https://api.github.com/users/lrosenthol/received_events","type":"User","site_admin":false},"created_at":"2016-09-30T16:55:57Z","updated_at":"2016-09-30T16:55:57Z","body":"@HadrienGardeur - thanks for putting up the strawman of the two proposals, unfortunately neither one works as stated\r\n\r\n> a manifest format for publications that handles metadata, display mode and a list of resources to cache\r\n\r\nI believe there is full agreement that we need a way to handle metadata (for some definition thereof) **and** a list of resources used in the publication.  Whether these go in a \"manifest\" or even in the same place is quite up for debate. \r\n\r\nI don't even know what a 'display mode' is - and why that's something declarative.\r\n\r\n>a shared JS script among Web Publications that will get the list of resources from the manifest, cache them and handle network requests using Service Workers\r\n\r\nIf someone wants to write that - great!  However, I wouldn't consider that the only (or even best) direction for publication handling.  As previously mentioned, there are considerations in the use of Service Workers in a variety of valid use cases posed here - so they may turn out to not be the panacea that some believe.  (hopefully some of the problems could be fixed with adaptations to the SW spec..)\r\n\r\n"}}
{"actor":{"display_login":"lrosenthol"}}