Re: [sensors] Conformance requirements for concrete specs

I'd say your "informal" option sounds good. That is, use RFC2119 terms
 everywhere and just wrap those blueprint reqs that need to be adapted
 by extension specs into Note/Example blocks to make them 
non-normative *in the Generic Sensor spec*. In addition, say in the 
prose clearly what authors are expected to do if they want to write an
 extensions spec for an AwesomeFutureSensor that conforms to the 
Generic Sensor API.

-- 
GitHub Notification of comment by anssiko
Please view or discuss this issue at 
https://github.com/w3c/sensors/issues/84#issuecomment-177918107 using 
your GitHub account

Received on Monday, 1 February 2016 11:11:22 UTC