Copyright © 2014 W3C ® (MIT, ERCIM, Keio, Beihang)
http://www.w3.org/2014/Talks/1028-CSVW-IH/
... "table level" templates
{{#rows}}
... "row level" templates
{{/rows}}
{{#rows}} and {{/rows}} is understood to be repeated for all rows{{name}}
{{name.filter1.filter2(arg1,arg2)...}}
{{name}}
{{name}} is a table level metadata key whose value is a string, replace it with the value{{name}}
{{name}} is a column name in the metadata document, replace it with the value of the corresponding cell{{name.filter1.filter2(arg1,arg2)...}}
{{name}} as definedfilter1 which is supposed to produce a string valuearg1, arg2 are strings, not templatesundefined, which means breaking the chain with an empty resultupper lower row_number replace(regexp, value) concat(str)
preconcat(str) URI_encode datatype language parsed_cell ...
@prefix : <http://example.org/{{@id}}#> .
{{#rows}}
{ "row" : "{{.row_number}}",
"GID" : "{{GID.number}}",
"On Street" : "{{on-street}}"
},
{{/rows}}
:Inventory%20Date
"{{inv-date.parse_cell}}"
{{inv-date.datatype.preconcat("^^xsd:")}};
jQuery extension that:
"templates" key in the metadata$("div.json").each(function(index) {
...
var request = {url: dataset_url, format: "JSON"};
$.getCSV(request)
.done( function(csv_data) {
...
key1/key2[] :{{on-street.capitalize}} "value" ;
But no new features should be added, unless it is really necessary!