You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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).
The text was updated successfully, but these errors were encountered:
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)
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).
The text was updated successfully, but these errors were encountered: