Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Origin mention in the Privacy and Security section #22

Closed
BigBlueHat opened this issue Sep 16, 2019 · 1 comment
Closed

Origin mention in the Privacy and Security section #22

BigBlueHat opened this issue Sep 16, 2019 · 1 comment

Comments

@BigBlueHat
Copy link
Member

In an audiobook manifest, all remote resources should share the same origin as the manifest file where possible.
https://www.w3.org/TR/audiobooks/#security-privacy

Not sure we should bring up "origin" without defining it, and not sure we should bring it up unless we plan to describe how (or if/when) UA's would be required to implement the Same-origin Policy--which is currently restricted to how desktop/mobile user-focused browsers work, and not often used as a constraint when dealing with APIs (which lean on other mechanisms of restriction).

@wareid wareid closed this as completed Sep 16, 2019
@iherman
Copy link
Member

iherman commented Sep 25, 2019

This issue was discussed in a meeting.

  • RESOLVED: Close Audiobooks Issue #22, remove the line from the specification and defer to more qualified groups.
  • ACTION: edit Audiobooks standard to remove line about the origin. (Wendy Reid)
View the transcript Wendy Reid: #22
Ralph Swick: [“be moved to” as in “raised as an issue for discussion in”]
Wendy Reid: there’s a mention of origin in the privacy and security section of audiobook
… (quoting from spec about where resources should be same-origin)
Benjamin Young: given what we just said about pub manifest
… mentioning it here is confusing
… we should take it out, or talk about how to handle a manifest
… so we should just delete the line
Wendy Reid: I’m happy to delete
Proposed resolution: Close Audiobooks Issue #22, remove the line from the specification and defer to more qualified groups. (Wendy Reid)
Benjamin Young: +1
Charles LaPierre: +1
Wendy Reid: +1
Brady Duga: +1
Benjamin Young: i want to add that there’s something we could call out
… that’s the use of base in @context
… you can say there’s a base of all the URLs in the JSON
… we could have a section that explains how to do that
… the advantage of @base in context is that your resource list uses fewer bytes
Resolution #6: Close Audiobooks Issue #22, remove the line from the specification and defer to more qualified groups.
Action #1: edit Audiobooks standard to remove line about the origin. (Wendy Reid)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants