{"action":"created","issue":{"url":"https://api.github.com/repos/w3c/csvw/issues/275","labels_url":"https://api.github.com/repos/w3c/csvw/issues/275/labels{/name}","comments_url":"https://api.github.com/repos/w3c/csvw/issues/275/comments","events_url":"https://api.github.com/repos/w3c/csvw/issues/275/events","html_url":"https://github.com/w3c/csvw/issues/275","id":59405047,"number":275,"title":"Conversion specifications in Model document","user":{"login":"JeniT","id":395050,"avatar_url":"https://avatars.githubusercontent.com/u/395050?v=3","gravatar_id":"","url":"https://api.github.com/users/JeniT","html_url":"https://github.com/JeniT","followers_url":"https://api.github.com/users/JeniT/followers","following_url":"https://api.github.com/users/JeniT/following{/other_user}","gists_url":"https://api.github.com/users/JeniT/gists{/gist_id}","starred_url":"https://api.github.com/users/JeniT/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/JeniT/subscriptions","organizations_url":"https://api.github.com/users/JeniT/orgs","repos_url":"https://api.github.com/users/JeniT/repos","events_url":"https://api.github.com/users/JeniT/events{/privacy}","received_events_url":"https://api.github.com/users/JeniT/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/w3c/csvw/labels/Metadata%20vocabulary%20document","name":"Metadata vocabulary document","color":"5319e7"},{"url":"https://api.github.com/repos/w3c/csvw/labels/Model%20Document","name":"Model Document","color":"cccccc"},{"url":"https://api.github.com/repos/w3c/csvw/labels/Requires%20telcon%20discussion/decision","name":"Requires telcon discussion/decision","color":"e11d21"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2015-03-01T16:48:41Z","updated_at":"2015-03-01T19:11:07Z","closed_at":null,"body":"The model document currently has a section on [conversion specifications](http://w3c.github.io/csvw/syntax/#converting-tables) which is intended to place constraints on the CSV-to-RDF, CSV-to-JSON and similar specifications for conversions. This is slightly confusing now that we've renamed the extensible (templating) mechanism [defined in the metadata document](http://w3c.github.io/csvw/metadata/#conversion-specifications) \"conversion specifications\" as well.\r\n\r\nI propose we call the ones in the metadata document \"Scripted Conversions\" to make it clear that these things are distinct?\r\n\r\nRelated, in the model document it says:\r\n\r\n> Conversion specifications should specify format-specific properties specifying external processing steps to provide more control to people defining conversions. If these are specified, the conversion specification must specify at what point in the processing this external processing takes place, and what it takes place on. Examples might be:\r\n> \r\n> * the URL of an XSLT file that is used to process XML after it is generated\r\n> * a string containing a SPARQL CONSTRUCT pattern that is executed on RDF after it is generated\r\n> * properties that contain definitions of Javascript callback functions that are used when processing particular columns or individual rows\r\n\r\nI propose that now we have the extensible/scripted/templated conversion specifications as defined in the metadata document, we remove this. "},"comment":{"url":"https://api.github.com/repos/w3c/csvw/issues/comments/76624712","html_url":"https://github.com/w3c/csvw/issues/275#issuecomment-76624712","issue_url":"https://api.github.com/repos/w3c/csvw/issues/275","id":76624712,"user":{"login":"6a6d74","id":2519144,"avatar_url":"https://avatars.githubusercontent.com/u/2519144?v=3","gravatar_id":"","url":"https://api.github.com/users/6a6d74","html_url":"https://github.com/6a6d74","followers_url":"https://api.github.com/users/6a6d74/followers","following_url":"https://api.github.com/users/6a6d74/following{/other_user}","gists_url":"https://api.github.com/users/6a6d74/gists{/gist_id}","starred_url":"https://api.github.com/users/6a6d74/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/6a6d74/subscriptions","organizations_url":"https://api.github.com/users/6a6d74/orgs","repos_url":"https://api.github.com/users/6a6d74/repos","events_url":"https://api.github.com/users/6a6d74/events{/privacy}","received_events_url":"https://api.github.com/users/6a6d74/received_events","type":"User","site_admin":false},"created_at":"2015-03-01T19:11:06Z","updated_at":"2015-03-01T19:11:06Z","body":"+1 from me too.\n\n> On 1 Mar 2015, at 19:08, Ivan Herman <notifications@github.com> wrote:\n> \n> \n> > On 01 Mar 2015, at 11:48 , Jeni Tennison <notifications@github.com> wrote:\n> > \n> > The model document currently has a section on conversion specifications which is intended to place constraints on the CSV-to-RDF, CSV-to-JSON and similar specifications for conversions. This is slightly confusing now that we've renamed the extensible (templating) mechanism defined in the metadata document \"conversion specifications\" as well.\n> > \n> > I propose we call the ones in the metadata document \"Scripted Conversions\" to make it clear that these things are distinct?\n> \n> Just to be picky:-) Implementation may choose to use a compiled program, originally written, say, in \"C\", which is usually not considered to be 'scripted'. What about something more neutral lie, say, 'external'? Alternatively, calling it \"transformation\"?\n> \n> > \n> > Related, in the model document it says:\n> > \n> > Conversion specifications should specify format-specific properties specifying external processing steps to provide more control to people defining conversions. If these are specified, the conversion specification must specify at what point in the processing this external processing takes place, and what it takes place on. Examples might be:\n> > \n> > • the URL of an XSLT file that is used to process XML after it is generated\n> > • a string containing a SPARQL CONSTRUCT pattern that is executed on RDF after it is generated\n> > • properties that contain definitions of Javascript callback functions that are used when processing particular columns or individual rows\n> > I propose that now we have the extensible/scripted/templated conversion specifications as defined in the metadata document, we remove this.\n> > \n> \n> +1\n> \n> Ivan\n> \n> > —\n> > Reply to this email directly or view it on GitHub.\n> > \n> \n> \n> ----\n> Ivan Herman, W3C\n> Digital Publishing Activity Lead\n> Home: http://www.w3.org/People/Ivan/\n> mobile: +31-641044153\n> ORCID ID: http://orcid.org/0000-0003-0782-2704\n> \n> \n> \n> \n> —\n> Reply to this email directly or view it on GitHub <https://github.com/w3c/csvw/issues/275#issuecomment-76624556>.\n> \n\n"}}