Validation Results

5bc0c33f94c89300040000a8

https://s1.bukalapak.com/loper/newsletters/csvs/000/009/185/original/Test_20newsletter_20team_20email_20pribadi.csv?1539357392

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

Total Rows Processed = 13

Download Standardised CSV
2Errors 2Warnings 2Messages
Structure 1 1 2
Schema 0 0 0
Context 1 1 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.

2 Errors, 2 Warnings

Context problem: Incorrect content type

Your CSV file is being delivered with an incorrect Content-Type of application/octet-stream.
We recommend that you configure your server to deliver CSV files with a Content-Type header of text/csv; charset=utf-8

Structural problem: Inconsistent Line Breaks

Your CSV has inconsistent line breaks (or your schema specified one line break style and the file uses another). You should make sure all line breaks are in the same form (i.e. CR-LF, or just LF). We recommend using CR-LF for maximum compatibility.

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.

Context problem: No encoding

The encoding of your CSV file is not being declared in the HTTP response.
We recommend that you configure your server to deliver CSV files with a Content-Type header of text/csv; charset=utf-8
If you are using a different encoding, then use an appropriate value for the charset parameter.

Structural problem: Assumed header

As there is no machine readable way to tell if your CSV has a header row, we have assumed that your CSV has one.

Structural problem: Non-standard Line Breaks on row 11

Your CSV appears to use 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.