[–] brown9-2 16y ago ↗ I was struck by the reference to RFC 2119The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119].http://tools.ietf.org/html/rfc2119I guess there really does need to be a standards specification for everything [–] nfnaaron 16y ago ↗ Of course. Standards, of all things, should be written in a standard way.And the standard way in which they're written should also be expressed in a standard way.
[–] nfnaaron 16y ago ↗ Of course. Standards, of all things, should be written in a standard way.And the standard way in which they're written should also be expressed in a standard way.
[–] Semiapies 16y ago ↗ A way to get conversations out of service "silos". Excellent.Cue 50 comments on how this is an evil attempt by Google to make money and monopolize everything.
4 comments
[ 2.4 ms ] story [ 15.2 ms ] threadThe key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119].
http://tools.ietf.org/html/rfc2119
I guess there really does need to be a standards specification for everything
And the standard way in which they're written should also be expressed in a standard way.
Cue 50 comments on how this is an evil attempt by Google to make money and monopolize everything.