Can a CSV dialect be referenced by path-or-url? Implementor Guide wrongly suggest so
See original GitHub issueIn the Implementor Guide on dereferencing and descriptor validation it provides dialect
as an example of something to dereference but I can’t see in the data resource spec where a dialect
can be provided using a path or url.
Perhaps the text should be changed to…
Therefore implementors MUST
dereference such “referential” property values before attempting to validate a descriptor. At present, this requirement applies to the schema
property in the Tabular Data Resource.
Issue Analytics
- State:
- Created 6 years ago
- Comments:14 (14 by maintainers)
Top Results From Across the Web
csv — CSV File Reading and Writing — Python 3.11.1 ...
1 An optional dialect parameter can be given which is used to define a set of parameters specific to a particular CSV dialect....
Read more >CSV Dialect - Frictionless Standards
CSV Dialect defines a simple format to describe the various dialects of CSV files in a language agnostic manner. It aims to deal...
Read more >Using Dialects when reading and writing CSV in Python
When reading and writing CSV files in Python using the csv module, you can specify an optional dialect parameter with the reader and...
Read more >Introduction to CSV Dialects with the Python CSV Module
The CSV data format lets you exchange data between applications in an implementation-independent fashion. This tutorial describes the syntax ...
Read more >SQL*Plus User's Guide and Reference - Oracle Help Center
have familiarity with SQL, see the Oracle Database SQL Language Reference. ... You can use the MARKUP options to generate output in HTML...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I see. I’m happy for a PR to make this more explicit then. I think all the information is there, but agree it could be more explicit.
@Stephen-Gates i think there must be an error in the implementation guidelines (/cc @vitorbaptista ) as i don’t believe dialect was intended to be dereferencable.