{"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":27,"created_at":"2016-09-14T03:31:18Z","updated_at":"2016-09-30T13:48:05Z","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/250748642","html_url":"https://github.com/w3c/dpub-pwp-ucr/issues/110#issuecomment-250748642","issue_url":"https://api.github.com/repos/w3c/dpub-pwp-ucr/issues/110","id":250748642,"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},"created_at":"2016-09-30T13:48:05Z","updated_at":"2016-09-30T13:48:05Z","body":"On Fri, Sep 30, 2016 at 11:10 PM, Hadrien Gardeur <notifications@github.com>\nwrote:\n\n> Which display modes do you have in mind? Something similar to the current\n> Web App Manifest?\n\n\nCorrect. Though there might be other means to invoke a display mode as\nneeded.\n\n\n> Also, part of saying \"I'm a publication, yo!\" is to provide metadata about\n> the publication.\n> So at a very minimum this is metadata + display mode.\n>\n\nSure. To be clear, the two need not reside in the same place.\n\n\n> Sure and a number of questions come up too, for instance:\n>\n>    - should the browser offer a default reading mode that will rely on\n>    service worker to cache resources of the publication ?\n>    - or is this strictly the responsibility of the publication ?\n>\n>  Where possible, always the responsibility of the publication.\n\n>\n>    - do we rely on the manifest to identify resources that should be\n>    cached ?\n>\n> No. That would duplicate what the cache API already does. That list could\njust be bundled with the service worker (a common practice today).\n\n>\n>\n> Payments API, etc. (\"You wanna buy the next chapter? of course you do!\")\n>\n> So the content is potentially behind a payment gateway, with some sort of\n> authentication requirement?\n>\n No, it's up to the author.\n\n> If so, is there a standard way to handle authentication and authorization?\n>\nSoon. Google for Credential Management API. I think there were videos shown\nat last Google I/O. Pretty amazing stuff... at the very least, good food\nfor thought there.\n\n\n> —\n> You are receiving this because you were mentioned.\n> Reply to this email directly, view it on GitHub\n> <https://github.com/w3c/dpub-pwp-ucr/issues/110#issuecomment-250740380>,\n> or mute the thread\n> <https://github.com/notifications/unsubscribe-auth/AA1HCpf3ttWEIGXDDFP4hlywGGwJPwd0ks5qvQpNgaJpZM4J8XbJ>\n> .\n>\n"}}
{"actor":{"display_login":"marcoscaceres"}}