Validation Results
https://gist.githubusercontent.com/sean-clayton/04ce5425c69e0a88c456e754cc0a3fb3/raw/d8ec771fbb78ee47f02ab774b288481870ab6e05/genesys-roll-spending.csv
Sorry, your CSV did not pass validation. Please review the errors and warnings below:
Total Rows Processed = 0
Download Standardised CSV| 2Errors | 1Warnings | |
|---|---|---|
| Structure | 1 | 0 |
| Schema | 0 | 0 |
| Context | 1 | 0 |
2 Errors, 1 Warning
Context problem: Incorrect content type
Your CSV file is being delivered with an incorrect Content-Type of text/plain; charset=utf-8.
We recommend that you configure your server to deliver CSV files with a Content-Type header of text/csv; charset=utf-8
Structural problem: Unexpected whitespace on row 2
t,Your current weapon gains the item quality "Limited Ammo 3" (CRB 88)
Quoted columns in the CSV should not have any leading or trailing whitespace.
Remove any spaces, tabs or other whitespace from either side of the delimiters in the row.
Dialect: Non standard dialect
Although your CSV validates, to make it as easy as possible for your data to be reused, we recommend using commas as delimiters, double quotes to enclose fields, and autodetecting line endings.
Structural problem: Non-standard Line Breaks on row 1
Your CSV appears to use LF line-breaks. While this will be fine in most cases, RFC 4180 specifies that
CSV files should use CR-LF (a carriage-return and line-feed pair, e.g. \r\n). This may be labelled as "Windows line endings" on some systems.
Next Steps
Publish and transform your data using DataGraft, either as enhanced CSV or Linked Data.