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.

Sign up for GitHub

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

Jump to bottom

Resource Model: TV #2

Open
jjmilburn opened this issue Oct 1, 2020 · 0 comments
Open

Resource Model: TV #2

jjmilburn opened this issue Oct 1, 2020 · 0 comments
Labels
resource model wanted Request for industry insight on how to model a given resource type

Comments

@jjmilburn
Copy link
Contributor

jjmilburn commented Oct 1, 2020 •
edited
Loading

What elements should a TV resource type expose, and should any be writable/updatable?

Some thoughts:

  • Input source
  • Minutes 'watched' in last day
  • Minutes per channel or source?
  • Current brightness/contrast settings
  • Current preprogrammed channel list
  • Number of over-the-air channels currently 'detectable' (some indication of antenna positioning?)

Possibly, this could be broken into multiple resource types ('channel lists' and setting-related resources, vs more fundamental characteristics of the TV)
@jjmilburn jjmilburn added the resource model wanted Request for industry insight on how to model a given resource type label Oct 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
resource model wanted Request for industry insight on how to model a given resource type
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jjmilburn