11:36:17 <RRSAgent> RRSAgent has joined #csvw
11:36:17 <RRSAgent> logging to http://www.w3.org/2014/05/21-csvw-irc
11:36:19 <trackbot> RRSAgent, make logs public
11:36:19 <Zakim> Zakim has joined #csvw
11:36:21 <trackbot> Zakim, this will be CSVW
11:36:21 <Zakim> ok, trackbot; I see DATA_CSVWG()8:00AM scheduled to start in 24 minutes
11:36:22 <trackbot> Meeting: CSV on the Web Working Group Teleconference
11:36:22 <trackbot> Date: 21 May 2014
11:56:10 <danbri> agenda: https://www.w3.org/2013/csvw/wiki/Meeting_Agenda_2014-05-21
11:56:20 <danbri> scribe? :)
11:57:09 <Zakim> DATA_CSVWG()8:00AM has now started
11:57:16 <Zakim> +??P2
11:59:16 <ivan> zakim, dial ivan-voip
11:59:16 <Zakim> ok, ivan; the call is being made
11:59:17 <Zakim> +Ivan
11:59:49 <Zakim> +[IPcaller]
12:00:04 <AndyS> zakim, IPCaller is me
12:00:04 <Zakim> +AndyS; got it
12:00:52 <danbri> waiting for more people to join
12:01:01 <danbri> prev minutes: http://www.w3.org/2014/05/14-csvw-minutes.html
12:02:10 <Zakim> +ericstephan
12:02:16 <ericstephan> ericstephan has joined #csvw
12:03:41 <jtandy> jtandy has joined #csvw
12:04:27 <danbri> discussing whether we're quorate
12:04:28 <Zakim> + +44.207.800.aaaa
12:04:42 <ivan> zakim, aaaa is jtandy
12:04:42 <Zakim> +jtandy; got it
12:04:49 <jtandy> zakim, aaaa is me
12:04:49 <Zakim> sorry, jtandy, I do not recognize a party named 'aaaa'
12:05:13 <danbri> anyone else joining from irc?
12:05:16 <jtandy> zakim, +44.207.800.aaaa is me
12:05:16 <Zakim> sorry, jtandy, I do not recognize a party named '+44.207.800.aaaa'
12:05:30 <AndyS> http://doodle.com/wk24me9g99hku83s
12:05:37 <jtandy> zakim, aa is me
12:05:37 <Zakim> sorry, jtandy, I do not recognize a party named 'aa'
12:05:39 <danbri> zakim, +44.207.800.aaaa is jtandy
12:05:39 <Zakim> sorry, danbri, I do not recognize a party named '+44.207.800.aaaa'
12:05:44 <danbri> zakim, who is on the phone?
12:05:44 <Zakim> On the phone I see danbri, Ivan, AndyS, ericstephan, jtandy
12:05:48 <jumbrich> jumbrich has joined #csvw
12:06:01 <jtandy> zakim, mute me
12:06:01 <Zakim> jtandy should now be muted
12:07:09 <danbri> (discussion of http://doodle.com/wk24me9g99hku83s#table )
12:07:11 <DavideCeolin> DavideCeolin has joined #csvw
12:07:16 <AndyS> Stasinos says his "no" is until mid July only.
12:07:53 <danbri> action: dan check in with gregg, yakov to see how rigidly they are constrained in http://doodle.com/wk24me9g99hku83s#table
12:07:53 <trackbot> Created ACTION-16 - Check in with gregg, yakov to see how rigidly they are constrained in http://doodle.com/wk24me9g99hku83s#table [on Dan Brickley - due 2014-05-28].
12:08:06 <fonso> fonso has joined #csvw
12:08:07 <Zakim> +??P6
12:08:10 <jumbrich> zakim, ??P6 is me
12:08:10 <Zakim> +jumbrich; got it
12:08:21 <danbri> zakim, who is on the phone?
12:08:21 <Zakim> On the phone I see danbri, Ivan, AndyS, ericstephan, jtandy (muted), jumbrich
12:08:44 <Zakim> +??P7
12:08:49 <DavideCeolin> zakim, ??P7 is me
12:08:49 <Zakim> +DavideCeolin; got it
12:09:23 <danbri> 	•	Approve agenda and previous http://www.w3.org/2014/05/14-csvw-minutes.html
12:09:23 <danbri> 	•	http://w3c.github.io/csvw/syntax/ (Jeni)
12:09:23 <danbri> 	•	http://w3c.github.io/csvw/metadata/ (Rufus/Jeni)
12:09:23 <danbri> 	•	http://w3c.github.io/csvw/csv2rdf/ (Ivan/Gregg/Andy)
12:09:23 <danbri> 	•	http://w3c.github.io/csvw/use-cases-and-requirements/ (Jeremy/Davide/Eric)
12:09:55 <jtandy> zakim, unmute me
12:09:55 <Zakim> jtandy should no longer be muted
12:10:13 <jtandy> zakim, mute me
12:10:13 <Zakim> jtandy should now be muted
12:10:21 <danbri> scribe: danbri
12:10:29 <Zakim> + +1.410.764.aabb
12:10:38 <danbri> last weeks minutes?
12:10:40 <AndyS> +1 to the minutes
12:10:48 <danbri> approved.
12:11:14 <ivan> zakim, aabb is yakov
12:11:14 <Zakim> +yakov; got it
12:11:41 <danbri> topic: csv2rdf
12:11:55 <yakovsh> yakovsh has joined #csvw
12:11:57 <danbri> topic: use cases and requirements
12:12:02 <jtandy> zakim, unmute me
12:12:02 <Zakim> jtandy should no longer be muted
12:12:17 <danbri> jtandy: summarising, …
12:12:26 <danbri> jtandy: the right to left use case has had a bit of work on it this week
12:12:43 <danbri> ericstephan: thanks to yakovsh for helping with the hebrew text
12:12:53 <Zakim> +??P9
12:13:00 <fonso> zakim, ??P9 is me
12:13:00 <Zakim> +fonso; got it
12:13:10 <jtandy> zakim, mute me
12:13:10 <Zakim> jtandy should now be muted
12:13:12 <danbri> … we added a couple of things. First a ref to some languages e.g. japanese, mandarin, that represent vertically, as they don't follow the same r2l rules we've been documenting for arabic and hebrew
12:13:20 <danbri> secondly, i had images originally for all of the csv
12:13:33 <danbri> we put also the data into the doc
12:13:34 <jtandy> zakim, unmute me
12:13:34 <Zakim> jtandy should no longer be muted
12:13:43 <danbri> seems like we're getting diff results from diff browsers. jtandy?
12:14:11 <danbri> jtandy: i think that the difficulty i have, depending on which browser/application i use to look at orig data file, it tries to interpret r2l or l2r
12:14:16 <danbri> mozilla seems to do it reasonably
12:14:47 <danbri> is there any guidance that people who are good with RESpec can give w.r.t. using r2l or l2r, to make sure it prints correctly (or at least in a determined way)
12:14:54 <ericstephan> http://w3c.github.io/csvw/use-cases-and-requirements/index.html#UC-SupportingRightToLeftDirectionality
12:14:55 <danbri> ivan: not sure, but trying same file in Chome and Firefox
12:15:13 <danbri> jtandy: when i'm editing the source i use Oxygen XML, it puts everything backwards
12:15:27 <danbri> ivan: I think that's correct w.r.t. the source xml
12:15:40 <danbri> jtandy: yes, just confusing for some of us!
12:15:58 <danbri> ivan: point is, at the moment it works ok.
12:16:17 <danbri> jtandy: what woudl be helpful for eric finishing these - once the UC is in a state he's happy with, to get final review from a content expert
12:16:34 <danbri> ivan: we have a w3c team member who happens to be Egyptian, I could ask him to take a look
12:16:39 <yakovsh> yes
12:16:48 <danbri> …and Yakov checked the Hebrew part
12:16:52 <jtandy> zakim, mute me
12:16:52 <Zakim> jtandy should now be muted
12:17:14 <jtandy> zakim, unmute me
12:17:14 <Zakim> jtandy should no longer be muted
12:17:17 <danbri> eric: as i was including the data, … these are referencing csv files on a website, would it be useful to have someone make a local archive copy
12:17:17 <jtandy> q+
12:17:20 <danbri> (github?)
12:17:22 <danbri> queue?
12:17:29 <danbri> ivan: +1
12:17:47 <danbri> … add locally in w3c via github tree
12:18:03 <danbri> ack jtandy
12:18:28 <danbri> jtandy: that's what i've been using; embedding examples in the text of the html, but giving people the full csv file as well via local copy in github
12:18:46 <danbri> q?
12:19:02 <danbri> ivan: maybe good idea to have a small separate index page somewhere for these
12:20:07 <danbri> eric: could make sense for use case team to do this
12:20:19 <jtandy> zakim, mute me
12:20:19 <Zakim> jtandy should now be muted
12:20:38 <danbri> ivan: in the egyptian version, 3rd row, i see arabic in the left-most field for example
12:20:50 <ericstephan> ACTION:  have a small separate index page for csv use case sources
12:20:51 <trackbot> Error finding 'have'. You can review and register nicknames at <http://www.w3.org/2013/csvw/track/users>.
12:20:52 <danbri> … check later w/ shadi
12:21:07 <jtandy> zakim, unmute me
12:21:07 <Zakim> jtandy should no longer be muted
12:21:22 <danbri> ACTION:  ericstephan have a small separate index page for csv use case sources
12:21:22 <trackbot> Error finding ' ericstephan'. You can review and register nicknames at <http://www.w3.org/2013/csvw/track/users>.
12:21:33 <danbri> hm, ivan help?
12:21:34 <danbri> q?
12:22:09 <danbri> eric: reviewing of use cases
12:22:14 <ericstephan> http://w3c.github.io/csvw/use-cases-and-requirements/index.html
12:22:15 <danbri> … and the requirements
12:22:33 <danbri> jtandy: more comments on specific UCs
12:23:04 <danbri> … thanks to Ivan for intro with Liam, … 1st UC (dig. preservation) used XML as an interim step, so we are incorporating Liam's perspective there
12:23:23 <danbri> … also that there are people using xslt, it is good to ack their requirements - so we now have an csv2xml requirement
12:23:25 <Zakim> -jumbrich
12:23:44 <Zakim> +??P6
12:23:48 <danbri> …the use intro was with HL7, need to follow up on that.
12:23:49 <jumbrich> zakim, ??P6 is me
12:23:49 <Zakim> +jumbrich; got it
12:24:23 <danbri> jtandy: biodiversity UC requires some work from me to make it a more action-oriented story. I wanted to raise the review of requirements work that Davide is handling.
12:24:30 <ericstephan> https://www.w3.org/2013/csvw/wiki/Use_Cases_Check
12:25:04 <danbri> eric: regarding management of UCs, finalizing, we've have a number of recent updates, so i've made a wiki page for the contributors to have some kind of a review.
12:25:12 <danbri> … can comment here, verify links etc.
12:25:48 <danbri> … felt useful given that we have 22 UCs
12:26:05 <jtandy> zakim, mute me
12:26:05 <Zakim> jtandy should now be muted
12:26:31 <danbri> davide: no specifics to add
12:26:49 <danbri> danbri: relationship between this and the RDF mapping work?
12:26:57 <stasinos> stasinos has joined #csvw
12:27:06 <danbri> ivan: we did quite a lot of work, Andy and I, got to a point where we have a friendly disagreement, ...
12:27:14 <danbri> … a use case that should win here, and tell which is wrong/right.
12:27:23 <danbri> … we have defined a scheme for generating rdf
12:27:49 <danbri> the way it's done now. translating it to generating xml or json would be relatively easy; it is not particularly rdf or json-specific.
12:27:57 <danbri> it uses the metadata fields that are defined in the metadata doc
12:28:07 <danbri> systematically goes through each row and figures out what is needed per-row
12:28:18 <danbri> we discussed at some point ,that a purely mechanical mapping is not enough
12:28:33 <Zakim> +[IPcaller]
12:28:36 <danbri> e.g. regex conversions, simple replacement templates with field names, ...
12:28:48 <stasinos> zakim, [IPcaller] is me
12:28:48 <Zakim> +stasinos; got it
12:28:56 <danbri> ivan: q is whether this is enough or not? if not, what else should we do when converting?
12:29:12 <danbri> … one way is to say is that we as a group stop at this point, rely on some external processing, dependent on the format we use
12:29:19 <danbri> … rely on some xslt, sparql processing,
12:29:24 <danbri> [danbri: .js ? ]
12:29:49 <danbri> ivan: the other alternative (not mutally exclusive) is that we define a more complex templating language/mechanism which essentially …
12:30:15 <danbri> … uses a skeleton output, and in there you have macro-like / template-like things, which are in the simplest things, replacements. In more complex case, … [not sure yet]
12:30:26 <danbri> … a kind of template, shape language
12:30:27 <danbri> q+
12:30:44 <danbri> ivan: and so the q is whether we really need this kind of thing or not
12:31:06 <danbri> … when for example in oen of the use cases, … is the generated rdf a v simple one that can be mapped directly from the content. Or does it have a more complex shape?
12:31:22 <danbri> or is the use case handled by refering to a sparql engine, xslt, etc
12:31:28 <danbri> so let's try to ground this in use cases.
12:31:47 <danbri> how exactly the json or rdf or xml looks like once it is generated, and how far we have to go in the general standards
12:32:10 <danbri> andys: you characterised the algorithmic approach as the easiest way to get conversions defined
12:32:24 <danbri> … i'm not convinced that there is quite so much sharing between the different languages (rdf,xml,json)
12:32:35 <danbri> …and you need to combine various fragments appropriately per-syntax
12:33:04 <danbri> I don't see that we have examples where this simple, fairly mechanical conversion, is exactly what people will find acceptable/useful
12:33:10 <danbri> i'm not sure those people are programmers
12:33:26 <danbri> defining the shape of the rdf, should come from the publisher side, not be a task that the data consumer has to undertake
12:34:01 <danbri> what i've found looking at some conversions we've done - you have to sit down w/ the csv file. Even with such metadata as we spec, there's a lot of higher level info that you'll also want to expose to make the exercise worthwhile.
12:34:03 <danbri> q?
12:34:25 <danbri> andys: q for jeni, who said she had some requirements to share, which i've asked for
12:34:26 <jtandy> q+
12:34:27 <danbri> q-
12:34:35 <jtandy> zakim, unmute me
12:34:35 <Zakim> jtandy should no longer be muted
12:34:52 <danbri> jtandy: summarising what was being said there to check my u/standing:
12:35:05 <danbri> …that mechanistic row by row conversion, simply using info from the metadata vocab, no templating?
12:35:18 <danbri> ivan: not exactly. uses metadata, but can also add simple local templating
12:35:19 <danbri> q+
12:35:26 <danbri> ie. can add cell level templating
12:36:07 <danbri> q+ to mention https://developers.google.com/webmasters/business-location-pages/schema.org-examples
12:36:22 <danbri> andys: … one subject per row (no nested structures)
12:36:43 <danbri> jtandy: in order to get those nested structures, we'd need extra structure
12:36:49 <danbri> andys: but that's not our proposal
12:37:19 <danbri> jtandy: if i was to interpret inputs or requirements from my scientific colleagues; they're not programmers. data managers, data processing people.
12:37:35 <danbri> so the more hoops they must jump through, the more likely they'll do something … random
12:37:50 <danbri> so i'd like a mechanism that asks for a reasonable amount of thinking to be expressed as a template
12:38:04 <danbri> some people try to create conversions by rote, adapting previous examples
12:38:10 <danbri> ivan/andys: makes sense
12:38:21 <ericstephan> +1 Jtandy
12:38:28 <danbri> andys: the metadata only conversion could be defined by using the metadata available to auto-generate a template
12:38:34 <DavideCeolin> +1
12:38:38 <danbri> it would be great if that template could be exposed by the tools -> learning by seeing
12:38:46 <danbri> jtandy: concur
12:39:10 <danbri> andys: a bit worried the algorithmic approach might end up with capabilities that aren't possible in the template
12:39:10 <Zakim> -jumbrich
12:39:19 <danbri> … and the gap between a naive and complex conversion coudl be too large
12:39:33 <danbri> andys: concern we're creating large work items for the WG
12:39:38 <ericstephan> +q
12:39:39 <danbri> ivan: yup
12:39:42 <jtandy> zakim, mute me
12:39:42 <Zakim> jtandy should now be muted
12:39:51 <danbri> jtandy, is your q answered?
12:39:54 <danbri> ack jtandy
12:39:59 <danbri> mute jtandy
12:40:07 <danbri> zakim, mute jtandy
12:40:07 <Zakim> jtandy should now be muted
12:40:11 <Zakim> +??P6
12:40:15 <jumbrich> zakim, ??P6 is me
12:40:15 <Zakim> +jumbrich; got it
12:40:27 <danbri> ivan: jeni mentioned that working with templating languages,, always ended up needing conditionals
12:40:39 <danbri> … intellectually v challenging but a major undertaking
12:40:59 <danbri> andys: i don't know exactly what requirements she had, but could be simple or complex
12:41:15 <danbri> in terms of defining languages, helpful that peopel are pointing them out
12:41:21 <danbri> i did a quick survey of templating languages
12:41:27 <danbri> several specifically target HTML output
12:41:43 <danbri> (andys, url for your notes?)
12:41:47 <danbri> andys: there are also _lots_
12:41:57 <ericstephan> are we talking about templating languages or perhaps design patterns?
12:42:11 <danbri> q?
12:42:58 <yakovsh> q+
12:43:05 <danbri> ack danbri
12:43:05 <Zakim> danbri, you wanted to mention https://developers.google.com/webmasters/business-location-pages/schema.org-examples
12:44:53 <danbri> ack eric
12:45:04 <danbri> eric:are we talking about templating languages or perhaps design patterns?
12:46:12 <danbri> ivan: are you thinking about the UCs they have?
12:46:28 <danbri> eric: e.g. i'm starting to work with Bernadette, data best practices wg
12:46:38 <danbri> … how data lives on the web, how it is used, ...
12:46:49 <danbri> Bernadette brought up design patterns
12:46:59 <danbri> e.g. for table based data, csv.
12:47:24 <danbri> danbri: can you share some links?
12:47:26 <danbri> eric: yup, will do
12:47:45 <danbri> action: ericstephan share links for Best Practices WG discussion of design patterns
12:47:45 <trackbot> Created ACTION-18 - Share links for best practices wg discussion of design patterns [on Eric Stephan - due 2014-05-28].
12:47:52 <danbri> q?
12:48:01 <danbri> ack yakovsh
12:48:14 <danbri> yakovs: regarding templating languages, we should bear in mind security
12:48:23 <danbri> even xslt can make a huge mess
12:48:35 <danbri> (c.f. http://xkcd.com/327/ )
12:48:53 <danbri> yakovs: we should mention security considerations for untrusted templates
12:48:53 <danbri> +1
12:49:28 <danbri> yakovs: re overall discussion, … not us defining canonical transformations, we have certain guidelines/overview, these 3 things (rdf, xml, [json]) serve as examples of that
12:49:41 <danbri> … but they're not exclusive to having other targets
12:49:49 <ivan> q+
12:49:58 <danbri> andys: can you put this on the mailing lists?
12:49:59 <danbri> q?
12:50:30 <danbri> ack ivan
12:50:59 <danbri> ivan: my goal at least was that the algorithmic/mechanical description that i produced, should be essentially repeatable on some other language
12:51:02 <yakovsh> action: yakovsh share with the mailing lists the information about security aspects
12:51:03 <trackbot> Created ACTION-19 - Share with the mailing lists the information about security aspects [on Yakov Shafranovich - due 2014-05-28].
12:51:21 <danbri> … andy rightly notes that there will be specificities for json, xml, etc.; but there is a generic component
12:51:38 <danbri> ivan: that statement would also be true for a general templating mechanism as well
12:51:47 <yakovsh> action: yakovsh share with the mailing list thoughts on generic guidelines and templates serving as examples
12:51:47 <trackbot> Created ACTION-20 - Share with the mailing list thoughts on generic guidelines and templates serving as examples [on Yakov Shafranovich - due 2014-05-28].
12:52:23 <danbri> ivan: … not only format specific but syntax specific (a distinction that matters for RDF)
12:52:49 <danbri> ivan: regarding security, … mechanical part is not fully secure. If you allow regular expressions, … scope for trickiness.
12:53:00 <danbri> … so valid for both.
12:53:02 <jtandy> q+
12:53:08 <yakovsh> http://msdn.microsoft.com/en-us/magazine/ff646973.aspx
12:53:09 <danbri> ack jtandy
12:53:18 <jtandy> zakim, unmute me
12:53:18 <Zakim> jtandy was not muted, jtandy
12:53:23 <yakovsh> example of a regex ddos
12:53:23 <danbri> andys: xslt can call out to your file system, for example.
12:53:55 <danbri> jtandy: to ivan - you mentioned you don't like templates inlcuding specific syntaxes. But I find it hard to avoid wanting to say 'my rdf should look like this…'
12:54:04 <jtandy> q+
12:54:08 <danbri> ivan: the rdf case is different than json
12:54:14 <danbri> … json is defined and described as a syntax
12:54:33 <danbri> … rdf is defined as a set of triples with variety of serializations
12:54:54 <jtandy> zakim, unmute me
12:54:54 <Zakim> jtandy was not muted, jtandy
12:55:00 <danbri> q+ to ask if UCs distinguish wanting triples vs wanting specific representations of triples
12:55:29 <Zakim> -jumbrich
12:55:35 <danbri> ivan: extra difficulty, if you give a template in mockup turtle, but if you need output in json-ld, then that system has to be able to parse the turtle and serialize json-ld
12:55:43 <AndyS> q+
12:55:45 <Zakim> +??P6
12:55:48 <yakovsh> regarding security, i think there is a review process for w3c specs here although I am not familiar with it: http://www.w3.org/Security/wiki/IG/W3C_spec_review
12:55:50 <jumbrich> zakim, ??P6 is me
12:55:50 <Zakim> +jumbrich; got it
12:55:52 <danbri> ack andys
12:55:53 <jtandy> zakim, mute me
12:55:53 <Zakim> jtandy should now be muted
12:55:55 <danbri> q?
12:56:43 <danbri> ack jtandy
12:57:11 <danbri> jtandy: i got Ivan's point, ended up where andy was; that there are conversion tools.
12:57:27 <danbri> i expect format mismatch an unlikely problem
12:57:40 <danbri> andys: i'm hoping the template comes from the publisher, not only consumer
12:57:56 <danbri> e.g. temperature reading UC
12:57:58 <danbri> q-
12:58:46 <danbri> jtandy: allowing consumer to choose from templates
12:58:55 <danbri> danbri: Editors: what more do you need from WG members?
12:59:08 <danbri> ivan: at least personally, i'd like to see something more about templating languages
12:59:18 <danbri> that won't lead to 3 years R'n'D
12:59:21 <jtandy> zakim, unmute me
12:59:21 <Zakim> jtandy was not muted, jtandy
12:59:26 <danbri> q?
12:59:28 <jtandy> zakim, mute me
12:59:28 <Zakim> jtandy should now be muted
12:59:33 <danbri> andys: so gregg has written it up
12:59:35 <DavideCeolin> q+
12:59:47 <danbri> ack Davide
13:00:29 <danbri> andys: we need to ground decisions in expectations; discussions are amongst a small core of ppl who turn up for the calls. Significant issue that you can get so far down the road, and then getting diff reception from wider audience.
13:01:18 <danbri> davide: need more feedback/input
13:01:45 <jtandy> q+
13:01:51 <jtandy> zakim, unmute me
13:01:51 <Zakim> jtandy should no longer be muted
13:01:53 <danbri> ack jtandy
13:02:15 <danbri> NOTE: for next week's call, let's decide later this week what we're doing with timing. See mailing list for exact timing choice.
13:02:45 <jtandy> zakim, mute me
13:02:45 <Zakim> jtandy should now be muted
13:03:41 <ericstephan> Dropping off now, have a good week!  I am on travel next week.
13:03:43 <Zakim> -jtandy
13:03:47 <Zakim> -danbri
13:03:49 <Zakim> -Ivan
13:03:51 <Zakim> -ericstephan
13:03:52 <AndyS> ADJOURNED
13:03:52 <Zakim> -jumbrich
13:03:54 <Zakim> -DavideCeolin
13:03:58 <Zakim> -AndyS
13:03:59 <jumbrich> jumbrich has left #csvw
13:04:01 <Zakim> -fonso
13:04:07 <fonso> fonso has left #csvw
13:04:11 <Zakim> -stasinos
13:04:21 <Zakim> -yakov
13:04:22 <Zakim> DATA_CSVWG()8:00AM has ended
13:04:22 <Zakim> Attendees were danbri, Ivan, AndyS, ericstephan, +44.207.800.aaaa, jtandy, jumbrich, DavideCeolin, +1.410.764.aabb, yakov, fonso, stasinos
13:04:35 <danbri> AndyS, got a minute to talk more in irc re http://w3c.github.io/csvw/csv2rdf/ ?
13:04:36 <ivan> rrsagent, draft minutes
13:04:36 <RRSAgent> I have made the request to generate http://www.w3.org/2014/05/21-csvw-minutes.html ivan
13:04:57 <ivan> trackbot, end telcon
13:04:57 <trackbot> Zakim, list attendees
13:04:57 <Zakim> sorry, trackbot, I don't know what conference this is
13:05:00 <AndyS> A few minutes ...
13:05:05 <trackbot> RRSAgent, please draft minutes
13:05:05 <RRSAgent> I have made the request to generate http://www.w3.org/2014/05/21-csvw-minutes.html trackbot
13:05:06 <trackbot> RRSAgent, bye
13:05:06 <RRSAgent> I see 6 open action items saved in http://www.w3.org/2014/05/21-csvw-actions.rdf :
13:05:06 <RRSAgent> ACTION: dan check in with gregg, yakov to see how rigidly they are constrained in http://doodle.com/wk24me9g99hku83s#table [1]
13:05:06 <RRSAgent>   recorded in http://www.w3.org/2014/05/21-csvw-irc#T12-07-53
13:05:06 <RRSAgent> ACTION: have a small separate index page for csv use case sources [2]
13:05:06 <RRSAgent>   recorded in http://www.w3.org/2014/05/21-csvw-irc#T12-20-50
13:05:06 <RRSAgent> ACTION:  ericstephan have a small separate index page for csv use case sources [3]
13:05:06 <RRSAgent>   recorded in http://www.w3.org/2014/05/21-csvw-irc#T12-21-22
13:05:06 <RRSAgent> ACTION: ericstephan share links for Best Practices WG discussion of design patterns [4]
13:05:06 <RRSAgent>   recorded in http://www.w3.org/2014/05/21-csvw-irc#T12-47-45
13:05:06 <RRSAgent> ACTION: yakovsh share with the mailing lists the information about security aspects [5]
13:05:06 <RRSAgent>   recorded in http://www.w3.org/2014/05/21-csvw-irc#T12-51-02
13:05:06 <RRSAgent> ACTION: yakovsh share with the mailing list thoughts on generic guidelines and templates serving as examples [6]
13:05:06 <RRSAgent>   recorded in http://www.w3.org/2014/05/21-csvw-irc#T12-51-47
13:05:12 <AndyS> Do you want to call me on skype?