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
I like those worded in an imperative style like "xx should be yyy" , over those worded in the "how to" style. I think the latter kind should be rewritten to the former kind.
e.g. "How to describe relative positions" could be " Relative positions should be expressed in a machine-interpretable or human readable manner"
The text was updated successfully, but these errors were encountered:
BP3: General linking > @6a6d74 to come up with a name
BP4: Use spatial data encodings that match your target audience > Suggested to @BillSwirrl
BP6: Multiple geometries > @andrea-perego to come up with a name
BP9: It's difficult to think of a good name... "Use relative positioning" (current name) sounds like you should always do relative positioning, which is not what we mean. My best attempt is "Use relative positioning for describing the position of spatial things relative to another" > @lieberjosh to come up with something
"Best Practice 11: Describe properties that change over time" is also problematic. What about "Provide information on the life cycle of spatial things"?
In her email Kerry notes:
I like those worded in an imperative style like "xx should be yyy" , over those worded in the "how to" style. I think the latter kind should be rewritten to the former kind.
e.g. "How to describe relative positions" could be " Relative positions should be expressed in a machine-interpretable or human readable manner"
The text was updated successfully, but these errors were encountered: