search

w3c / tvcontrol-api

TV Control API specification - https://w3c.github.io/tvcontrol-api/
10 stars 11 forks source link

Specify storage scope for recordings #15

Open chrisn opened 7 years ago

chrisn commented 7 years ago

The TVManager interface includes methods for scheduling, enumerating, and removing recordings, but the specification does not state how the storage for recordings is to be scoped. Other web APIs that store data (e.g., local storage) apply a per-origin scope.

As currently written, the TV Control API specification leaves the decision open to interpretation, which could mean that recordings are available to any web application regardless of origin. Is this the intended behaviour? How should recordings be scoped?

stevem-tw commented 7 years ago

I think if we specify anything other than per-origin, we run the risk of either impacting user privacy or over-complicating the required behaviour (and probably having some unintended consequences that we will regret).

Per-origin scope is consistent with other web APIs, and so I would suggest we keep that consistency.