updates

20211104164651-input_data_properties.org

@@ -16,3 +16,18 @@ data?
 Is there a good language for describing these categories of data, can we better
 understand what differentiates them, and use that knowledge to build more
 consistent guidelines for UX and input handling?
+
+* Trimmable
+#+begin_notes
+Taken from https://experience.sap.com/fiori-design-web/leading-trailing-blank-removal/
+#+end_notes
+** Use field trimming if:
+- The leading or trailing white space is not needed for the business process.
+- The input fields have uniquely identifying business objects.
+- The input fields have a fixed field length.
+** Do not use field trimming if:
+- The use case explicitly requires leading/trailing white space. For example,
+  for formatted text such as chats, comments, descriptions, source code, or for
+  file names (according to the supported OS behavior).
+- For text areas where users would expect leading white space as a formatting
+  tool.