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

Find a clearer name for the sensor concept #162

Closed
pozdnyakov opened this issue Jan 27, 2017 · 6 comments
Closed

Find a clearer name for the sensor concept #162

pozdnyakov opened this issue Jan 27, 2017 · 6 comments
Milestone
Level 1

Comments

@pozdnyakov
Copy link

Latest reading https://w3c.github.io/sensors/#latest-reading is an implementation detail that should be marked as an internal slot and be mentioned at https://w3c.github.io/sensors/#sensor-internal-slots
@pozdnyakov pozdnyakov changed the title latest reading should be declarted as internal slot latest reading should be declarted as an internal slot Jan 27, 2017
@tobie
Copy link
Member

tobie commented Jan 27, 2017

Well, it's associated to the [=sensor=] object, which itself is an abstract concept and so doesn't have slots.

@tobie
Copy link
Member

tobie commented Jan 27, 2017

I frankly wish I could make it easier to distinguish between the abstract [=sensor=] concept, the {{Sensor}} interface and instances of {{Sensor}} sub-classes.

Would you have a suggestion?

@pozdnyakov
Copy link
Author

IMO that would be great too. I do not have any specific suggestions, maybe it's worth just mentioning it explicitly in the spec prose?

@tobie
Copy link
Member

tobie commented Jan 27, 2017

Sorry, mentioning what?

@pozdnyakov
Copy link
Author

The difference between [=sensor=] object as a concept (and which can represent a real HW sensor) and Sensor object as implementation of Sensor interface.. They both are called "Sensor", so I was confused and created this issue :) now I see which of them =latest reading= belongs to.
So it might be the case that I just should have read the spec more attentively from the beginning, If you think the existing description is clear enough feel free to close the issue.

@tobie
Copy link
Member

tobie commented Jan 27, 2017 •
edited
Loading

Seriously though, I get confused by my own prose regularly because of that issue.

  • [=sensor concept=] ?
  • [=underlying sensor=] ?
  • maybe even using [=concrete sensor=] would work.

@anssiko, @dontcallmedom, @rwaldron: thoughts?

@tobie tobie modified the milestone: Level 1 Jan 27, 2017
@tobie tobie changed the title latest reading should be declarted as an internal slot Find a clearer name for the sensor concept Feb 20, 2017
pozdnyakov pushed a commit to pozdnyakov/sensors that referenced this issue Sep 19, 2017
Redefine [=sensor=] concept
04cfc02 
This patch splits [=sensor=] concept into two concepts:
1. device sensor - refers a physical sensor instance on a device
2. platform sensor - refers a piece of platfrom API representing a device sensor

Fixes w3c#162
@pozdnyakov pozdnyakov mentioned this issue Sep 19, 2017
Merged
pozdnyakov pushed a commit to pozdnyakov/sensors that referenced this issue Sep 19, 2017
Redefine [=sensor=] concept
514dba9 
This patch splits [=sensor=] concept into two concepts:
1. device sensor - refers a physical sensor instance on a device
2. platform sensor - refers a piece of platfrom API representing a device sensor

Fixes w3c#162
pozdnyakov pushed a commit to pozdnyakov/sensors that referenced this issue Sep 20, 2017
Redefine [=sensor=] concept
f737caf 
This patch splits [=sensor=] concept into two concepts:
1. device sensor - refers a physical sensor instance on a device
2. platform sensor - refers a piece of platfrom API representing a device sensor

Fixes w3c#162
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
Level 1
Development

No branches or pull requests
2 participants
@tobie @pozdnyakov