1] Component Name: Blink>DeviceOrientation

Guideline 1 (Clarity): Component name should be descriptive

Using the name from the W3C spec.
https://www.w3.org/TR/orientation-event/


Guideline 2 (Permanence): Component names should describe features

Using the name from the W3C spec.
https://www.w3.org/TR/orientation-event/


Guideline 3 (Specific): Components are meant to explicitly track functional
work areas.

Yes.

Guideline 4 (Discoverable/ Predictable): Components should be parented
where people would logically expect to find them 

Web APIs go in Blink


2] Parent Component: Blink

3] Description of Component: ______

Issues related to the DeviceOrientation Event API https://www.w3.org/TR/orientation-event/

4] Admin/ Owner: ______

If groups work, please:
device-dev@chromium.org

If not, then:
reillyg@chromium.org,
dougt@chromium.org,
scheib@chromium.org,
mcasas@chromium.org,
timvolodine@chromium.org,

5] Please specify what triage practices will be followed for the component
(i.e. what team will do it and how frequently).

Device API team triages, all of blink is moving to 1 week SLA.