1] Component Name: Blink>NFC

Guideline 1 (Clarity): Component name should be descriptive beyond the core
project team

Using the term from https://w3c.github.io/web-nfc/

Guideline 2 (Permanence): Component names should describe features/
functions and not team names, code locations, etc..., which are more
subject to change and make the hierarchy less predictable for people
triaging issues.

Using the term from https://w3c.github.io/web-nfc/

Guideline 3 (Specific): Components are meant to explicitly track functional
work areas.  If you are trying to track a Proj(ect) or an on-going effort
(e.g. Hotlist-Conops), please instead request a label for a (Proj- or
Hotlist-)

Web NFC is a functional area.

Guideline 4 (Discoverable/ Predictable): Components should be parented
where people would logically expect to find them (i.e. follow product
decomposition when naming versus team decomposition)

Web APIs go in Blink>.

2] Parent Component (e.g. Blink, UI>Browser, etc...): Blink

3] Description of Component: Issues related to the Web NFC API https://w3c.github.io/web-nfc/

4] Admin/ Owner: device-dev@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.