CSVW Support

[megin1989]

The following are my findings about CSVW(Please check the link below). Can you please tell me if they are correct or not?

https://docs.google.com/spreadsheets/d/1iPE-CpxW0YlNgFZCvJhwEsUgP2MfqzfBkXxgSgrvtFM/edit?usp=sharing

[megin1989]

Hello Would you kindly respond to my query?

[gkellogg]

A couple of points on this. CSVW came about before JSON-LD was a recommendation and a lot of the JSON used in the metadata was based on this, but with restrictions. Even though JSON-LD has many features, they can't all be used in a CSVW metadata file.

@context – this is limited to use only "http://www.w3.org/ns/csvw", but can optionaly also contain @language and/or @language. This allows the metadata to be properly interpreted as JSON-LD.

The others you may as "Supported" have definitions that can be found in http://www.w3.org/ns/csvw. This also includes some you have marked as "Not Supported":

• encoding – An atomic property that sets the encoding flag to the single provided string value, which MUST be a defined in [encoding]. The default is "utf-8".
• format – An atomic property that contains either a single string or an object that defines the format of a value of this type, used when parsing a string value as described in Parsing Cells in [tabular-data-model].

Note that the Working Group was closed in 2016, so responding to such issues is based on the (fading) memory of the original WG members and what personal time they have to spend researching such questions.