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
When the names of the columns in the CSV data are compared with the names of the columns in the annotations what is the rule for determining if they are the same? For example, is equality based solely on the UTF-8 raw byte sequence or is some form of Unicode Normalization applied first and does case matter when making comparisons?
It is recommended that Unicode text not be normalized if it is already in a Unicode encoding. If text needs to be converted into Unicode, then a normalizing transcoder should be used and text be normalized into Unicode Normal Form C.
It is recommended that case sensitive matching be used when making comparisons.
The text was updated successfully, but these errors were encountered:
I believe this is partially fixed by #581 (namely around making the decoding into Unicode & normalization explicit), but also by the resolution #551 which defines the matching algorithm for column names/titles.
(Comment originally posted by Steven Atkin)
6.2 Example with single table and rich annotations
http://www.w3.org/TR/2015/WD-csv2json-20150416/#example-tree-ops-ext
When the names of the columns in the CSV data are compared with the names of the columns in the annotations what is the rule for determining if they are the same? For example, is equality based solely on the UTF-8 raw byte sequence or is some form of Unicode Normalization applied first and does case matter when making comparisons?
It is recommended that Unicode text not be normalized if it is already in a Unicode encoding. If text needs to be converted into Unicode, then a normalizing transcoder should be used and text be normalized into Unicode Normal Form C.
It is recommended that case sensitive matching be used when making comparisons.
The text was updated successfully, but these errors were encountered: