Add "Local Coordinate System" concept #340
Conversation
|
Or according to a |
index.bs
Outdated
| @@ -1409,6 +1431,8 @@ Gets the {{DOMException}} object passed to {{SensorErrorEventInit}}. | |||
|
|
|||
| 1. If |sensor_instance|.{{[[state]]}} is "activated", | |||
| 1. Let |readings| be the [=latest reading=] of |sensor_instance|'s related [=platform sensor=]. | |||
| 1. If the [=extension specification=] defines a [=local coordinate system=] for |sensor_instance|, | |||
| 1. Remap |readings| values to the [=local coordinate system=]. | |||
There was a problem hiding this comment.
Maybe make reference to coordinate system transformation (reference frame). There should be plenty of books, articles. For example:
The Foundations of Celestial Mechanics George W. Collins, II
2.4 Coordinate Transformations
pozdnyakov
force-pushed
the
coordinate_system
branch
from
f1f43e0
to
b3c9a14
Compare
|
@kenchris , @alexshalamov your comments are addressed, please take a look. |
index.bs
Outdated
| a <dfn export>local coordinate system</dfn> that represents | ||
| a reference frame for these [=sensor readings|readings=]. | ||
| A [=device sensor|sensor=] that provides such [=sensor readings|readings=] | ||
| is referred as <dfn export>spatial sensor</dfn>. |
index.bs
Outdated
| a [=local coordinate system=] for resolution. | ||
|
|
||
| The [=local coordinate system=] normally used in a mobile device is | ||
| a Cartesian coordinate system, which is defined relatively to the |
pozdnyakov
force-pushed
the
coordinate_system
branch
from
b3c9a14
to
10e78df
Compare
index.bs
Outdated
| A [=device sensor|sensor=] that provides such [=sensor readings|readings=] | ||
| is referred to as <dfn export>spatial sensor</dfn>. | ||
|
|
||
| Depending on the number of orthogonal axes in which the measurements |
There was a problem hiding this comment.
I find this part a bit hard to read... very long sentence with injected sentences, which then continues
There was a problem hiding this comment.
Wrapping it around makes it easier to read
A [=spatial sensor|sensor=] can be uniaxial, biaxial, or triaxial, depending on the number of orthogonal axes in which the measurements can be performed simultaneously by a [=spatial sensor=]
There was a problem hiding this comment.
A [=spatial sensor=] can be uniaxial, biaxial,
or triaxial, depending on the number of orthogonal axes in
which it can perform simultaneous measurements.
index.bs
Outdated
| [=spatial sensor|sensor=] can be <dfn>uniaxial</dfn>, <dfn>biaxial</dfn>, | ||
| or <dfn>triaxial</dfn>. | ||
|
|
||
| Scalar physical quantities (i.e. temperature) do not require |
There was a problem hiding this comment.
Why call them scalar... a x value is also a scalar
There was a problem hiding this comment.
In a way, they are just values relative to a fixed scale. It gets confusing when we start talking about relative humidity, which is humidity relative to the current temperature. Maybe we could make this more clear
There was a problem hiding this comment.
Actually what you want it "Non-relativistic scalars"
There was a problem hiding this comment.
Non-relativistic scalar physical quantities such as temperature, time and mass, do not require a [=local coordinate system=] for resolution. Other scalars may have standardized frames of reference, such as relative humidity, which is relative to the current temperature.
There was a problem hiding this comment.
x is a vector component in a Cartesian coordinate system, i.e. the vector physical quantity is measured.
Not sure why fixed scale is required, both temperature and relative humidity won't need a spatial coordinate system, isn't it?
This is required for fixing w3c#257
pozdnyakov
force-pushed
the
coordinate_system
branch
from
10e78df
to
67f96b1
Compare
| @@ -123,6 +123,17 @@ spec: webidl; type:dfn; text:identifier | |||
| "title": "Sensor Use Cases", | |||
| "date": "2017", | |||
| "status": "Note" | |||
| }, | |||
|
Thanks for review! |
This is required for fixing #257
Preview | Diff