Validation Results

5be525f73b7ca20004000014

https://gist.githubusercontent.com/IvanYashchuk/1d7e096590a3c23f08b129e5004bcc28/raw/191ff73f3cdc36b69f47c3e3f63eddbef1c5fe4e/1a_square_periodic_out.csv

Sorry, your CSV did not pass validation. Please review the errors and warnings below:

Total Rows Processed = 1345

Download Standardised CSV
1Errors 2Warnings 1Messages
Structure 0 1 1
Schema 0 0 0
Context 1 0 0

Your CSV file appears to only contain a single column. This may indicate that it is being incorrectly parsed. You can try resubmitting it using a different dialect.

1 Error, 2 Warnings

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

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: Check CSV parsing options

Your CSV file appears to only contain a single column. This may indicate that it is being incorrectly parsed.
We recommend using commas as delimiters and escaping values in columns where necessary.

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.