Template as mechanism for CSV conversion.

(from the telecon - JeniT asked for this to be made more visible on the 
list)

Gregg has suggested that if all the conversions are based around the
template mechanism, then there could be one conversions document for all 
of RDF, JSON and XML.

That makes sense to me although I also think that someone arrives at the
doc wanting, say, the details of JSON conversion, having them all in one 
place makes for a less focused document.

e.g. RDF:
http://w3c.github.io/csvw/csv2rdf/#graph-template

The templating mechanism is text-based and does not require parsing of 
some variant of the output syntax ("variant" because of the need for 
template slots).  A processor may provide additional validation of the 
output but, at a minimum, it can generate output just by text processing 
(and potentially get illegal syntax due to the lightweight nature of the 
process).

A starting point for templates is URI Templates

   http://tools.ietf.org/html/rfc6570

although there needs to be escaping per syntax support.

(*nix) Shell parameter expansion is a similar mechanism.

http://www.gnu.org/software/bash/manual/bashref.html#Shell-Parameter-Expansion 
(not the array bits)

${parameter/pattern/string} is a regex replace, for example.

 Andy

Received on Wednesday, 14 May 2014 17:14:44 UTC