You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A decision to be made: whether {} wrappers that permit it should always or never be internally space padded; that is whether { should always or never be followed, and} should always or never be preceded, by a space . I am strongly in favor of always including such space characters, as I have never found them to decrease comprehension, and very often to increase it.
I find that sometimes including such padding, as here on the closing string } but not on the opening {I(E), significantly decreases comprehension, especially by readers who are not yet familiar with the overall subject matter.
(A similar question applies to <>, (), [], and any other similar wrapping punctuation.)
(Originally raised at https://github.com/w3c/rdf-semantics/pull/64/files#r1911053260)
A decision to be made: whether
. I am strongly in favor of always including such space characters, as I have never found them to decrease comprehension, and very often to increase it.
{}
wrappers that permit it should always or never be internally space padded; that is whether{
should always or never be followed, and}
should always or never be preceded, by a spaceI find that sometimes including such padding, as here on the closing
string }
but not on the opening{I(E)
, significantly decreases comprehension, especially by readers who are not yet familiar with the overall subject matter.(A similar question applies to
<>
,()
,[]
, and any other similar wrapping punctuation.)See https://github.com/w3c/rdf-semantics/blob/88152260cb19714c5c5ca206e709e8e46496928e/spec/index.html#L1181
The text was updated successfully, but these errors were encountered: