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

The Generic Sensors spec says N/A but other sensors in development depends on it #158

Open
kenchris opened this issue Jan 3, 2018 · 1 comment

Comments

@kenchris
Copy link

kenchris commented Jan 3, 2018

So Generic Sensors spec is thus also in development

@tidoust
Copy link
Member

tidoust commented Jan 9, 2018

I think we still need to improve how the framework processes implementation info. "N/A" is being used to mean:

  1. "Unknown": we don't have any info
  2. "Not applicable": the spec is not meant to be implemented directly, e.g. a Note, or a best practices doc.
  3. "Not supported". We know that the spec is not implemented in a user-agent.

The framework does not distinguish between these meanings at all. It actually does not even store the "Not supported" information that it gets from web platform sources for now.

In the case of the Generic Sensors spec, we don't have any info because status platforms do not report on that spec, but rather provide (sometimes incorrect - as reported in #160) info about concrete sensor specs.

We may hardcode some implementation info in the data file that describes Generic Sensor. Now, I confess I'm not entirely sure that info is really meaningul in practice: implementing the Generic Sensors spec per se does not mean much in isolation. It might be better to report something like "See more concrete sensor specs".

What would you rather see in the "Current implementation" column, @kenchris ?

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

No branches or pull requests

3 participants