12:31:51 <RRSAgent> RRSAgent has joined #csvw
12:31:51 <RRSAgent> logging to http://www.w3.org/2014/03/19-csvw-irc
12:31:53 <trackbot> RRSAgent, make logs public
12:31:53 <Zakim> Zakim has joined #csvw
12:31:55 <trackbot> Zakim, this will be CSVW
12:31:55 <Zakim> ok, trackbot; I see DATA_CSVWG()9:00AM scheduled to start in 29 minutes
12:31:56 <trackbot> Meeting: CSV on the Web Working Group Teleconference
12:31:56 <trackbot> Date: 19 March 2014
12:47:57 <danbri> maybe interesting here: Musicbrainz sql to rdf mappings, https://github.com/LinkedBrainz/MusicBrainz-R2RML/blob/master/mappings/artist.ttl
12:49:17 <MathewThomas> MathewThomas has joined #csvw
12:49:36 <timfinin> timfinin has joined #csvw
12:52:33 <gkellogg> gkellogg has joined #csvw
12:54:53 <tfinin> tfinin has joined #csvw
12:58:27 <Zakim> DATA_CSVWG()9:00AM has now started
12:58:34 <Zakim> + +1.937.207.aaaa
12:58:59 <yakovsh> yakovsh has joined #csvw
12:59:17 <DavideCeolin> DavideCeolin has joined #csvw
12:59:27 <Zakim> + +1.443.650.aabb
13:00:17 <yakovsh> +1.443.650.aabb is me
13:00:25 <yakovsh> zakim, +1.443.650.aabb is me
13:00:25 <Zakim> +yakovsh; got it
13:00:37 <Zakim> +??P11
13:00:57 <Zakim> +??P10
13:00:59 <Zakim> +[IPcaller]
13:01:02 <gkellogg> zakim, I am ??P10
13:01:02 <Zakim> +gkellogg; got it
13:01:11 <ivan> zakim, dial ivan-voip
13:01:11 <Zakim> ok, ivan; the call is being made
13:01:13 <Zakim> +Ivan
13:01:34 <danbri> not sure, why?
13:01:41 <ivan> zakim, who is here?
13:01:41 <Zakim> On the phone I see +1.937.207.aaaa, yakovsh, danbri, gkellogg, JeniT, Ivan
13:01:43 <Zakim> On IRC I see DavideCeolin, yakovsh, tfinin, gkellogg, MathewThomas, Zakim, RRSAgent, ivan, AndyS, danbri, JeniT, fresco_, trackbot
13:01:51 <Zakim> +[IPcaller]
13:01:55 <Zakim> + +1.410.461.aacc
13:01:57 <AndyS> zakim, ipcaller is me
13:01:57 <Zakim> +AndyS; got it
13:02:05 <ericstephan> ericstephan has joined #csvw
13:02:15 <ivan> zakim, aaaa is MathewThomas
13:02:16 <Zakim> +MathewThomas; got it
13:02:18 <Zakim> +??P15
13:02:23 <danbri> any scribe volunteer?
13:02:33 <DavideCeolin> zakim, ??P15 is me
13:02:33 <Zakim> +DavideCeolin; got it
13:02:34 <ivan> zakim, aacc is tfinin
13:02:34 <Zakim> +tfinin; got it
13:02:45 <ivan> zakim, who is here?
13:02:45 <Zakim> On the phone I see MathewThomas, yakovsh, danbri, gkellogg, JeniT, Ivan, AndyS, tfinin, DavideCeolin
13:02:47 <Zakim> On IRC I see ericstephan, DavideCeolin, yakovsh, tfinin, gkellogg, MathewThomas, Zakim, RRSAgent, ivan, AndyS, danbri, JeniT, fresco_, trackbot
13:03:20 <Zakim> + +1.509.554.aadd
13:03:37 <ivan> zakim, aadd is ericstephan
13:03:37 <Zakim> +ericstephan; got it
13:03:39 <Zakim> +[IPcaller]
13:03:45 <andimou> andimou has joined #csvw
13:04:15 <ivan> zakim, who is noisy?
13:04:25 <Zakim> ivan, listening for 10 seconds I heard sound from the following: yakovsh (4%)
13:04:38 <danbri> topic: review last week's minutes
13:05:11 <JeniT> ScribeNick: JeniT
13:05:16 <JeniT> Scribe: Jeni
13:05:18 <JeniT> Chair: Dan
13:05:24 <danbri> http://www.w3.org/2014/03/05-csvw-minutes.html
13:05:28 <Zakim> +[Ugent]
13:05:32 <JeniT> Agenda: https://www.w3.org/2013/csvw/wiki/Meeting_Agenda_2014-03-19
13:06:15 <ivan> zakim, Ugent is andimou
13:06:15 <Zakim> +andimou; got it
13:06:20 <JeniT> RESOLUTION: Minutes accepted
13:06:21 <danbri> resolved: minutes are a fair record
13:06:24 <AndyS> That was March 5
13:06:31 <AndyS> http://www.w3.org/2014/03/12-csvw-minutes.html
13:06:41 <danbri> http://www.w3.org/2014/03/12-csvw-minutes.html
13:07:12 <JeniT> Topic: Model for Tabular Data & Metadata on the Web
13:07:34 <danbri> 'this morning i went through the actions from last week's call
13:07:44 <danbri> basically to add in a section that talks about the various methods of locating metadata
13:07:47 <danbri> about a csv file.
13:07:50 <danbri> that section is now …
13:07:51 <JeniT> http://w3c.github.io/csvw/syntax/#metadata
13:07:53 <danbri> <- here
13:08:19 <danbri> 'it's very sparse, but with lots of issues highlighting places where more discussion/ work needed to resolve the details. but fine for FPWD.
13:08:42 <ivan> q+
13:08:53 <danbri> danbri: are you proposing that we publish this?
13:09:17 <danbri> jeni: it looks ready. changed short name as req'd. refined abstract. i think addresses concerns from ivan/ralph discussion.
13:09:19 <danbri> q?
13:09:21 <danbri> ack ivan
13:09:41 <danbri> ivan: to be precise, ralph didn't object as such; i was trying to anticipate possible issues. i think it's fine.
13:09:53 <JeniT> ivan: we had some discussion about adding text to the status section
13:09:55 <danbri> … we had some discussion re adding text to SOTD
13:10:10 <JeniT> ... which we could add to make it clear what's happening in relation to IETF
13:10:33 <danbri> jeni: fine adding text that dan suggested
13:10:58 <JeniT> AndyS: suggest using 'tabular-data-model' rather than 'tabular-model' to make distinct from eg HTML
13:11:14 <JeniT> JeniT: happy to make that change
13:11:51 <danbri> ivan: let's concentrate on data rather than html tables
13:11:55 <JeniT> danbri: we might extend to HTML tables at some point
13:12:18 <JeniT> danbri: propose we publish as FPWD
13:12:53 <ivan> PROPOSED: the tabular data model should be published as FPWD as 'tabular-data-model'
13:12:59 <JeniT> +1
13:12:59 <ericstephan> +1
13:13:01 <AndyS> +1
13:13:01 <gkellogg> +1
13:13:02 <ivan> +1
13:13:03 <danbri> +1
13:13:09 <yakovsh> +1
13:13:19 <DavideCeolin> +1
13:13:25 <tfinin> +1
13:13:32 <fresco> +1
13:13:35 <danbri> +1 from Jeremy
13:13:38 <ivan> RESOLVED: the tabular data model should be published as FPWD as 'tabular-data-model'
13:13:43 <MathewThomas> +1
13:13:46 <andimou> +1
13:14:02 <JeniT> Topic: Use Cases Document
13:14:38 <JeniT> DavideCeolin: I just sent an email about the issue about XML conversion
13:14:53 <danbri> http://w3c.github.io/csvw/use-cases-and-requirements/
13:15:04 <JeniT> ... I added that issue, so as far as I'm concerned it's fine
13:15:20 <JeniT> danbri: we can always make another WD, do we have to resolve this before we publish?
13:15:29 <JeniT> ericstephan: we've put all the use cases together: 18 use cases
13:15:41 <JeniT> ... if there isn't a use case that you submitted, it might have been combined with another
13:15:49 <JeniT> ... we have a number of requirements too
13:15:58 <JeniT> ... but I believe we should be good to go for FPWD
13:16:08 <JeniT> danbri: consensus from the editors
13:16:28 <JeniT> ... is short name fixed?
13:16:28 <ivan> PROPOSED: the use case document should be published as FPWD as 'csvw-ucr'
13:16:35 <ivan> +1
13:16:36 <JeniT> +1
13:16:36 <danbri> +1
13:16:39 <ericstephan> +1
13:16:39 <yakovsh> +1
13:16:40 <AndyS> +1
13:16:41 <danbri> +1 relayed from Jeremy
13:16:48 <fresco> +1
13:16:52 <tfinin> +1
13:17:02 <gkellogg> +1
13:17:09 <andimou> +1
13:17:22 <AndyS> TR/csvw-use-cases-and-reqs/
13:18:03 <JeniT> AndyS: 'csvw-ucr' is not what's in the document
13:18:15 <AndyS> Changing to shorter is fine.
13:18:16 <JeniT> ivan: yes, I propose changing to 'csvw-ucr' as it's short
13:18:27 <ivan> RESOLVED: the use case document should be published as FPWD as 'csvw-ucr'
13:19:01 <danbri> …
13:19:03 <JeniT> ivan: there is a bit of approval
13:19:16 <JeniT> s/approval/a process/
13:19:32 <JeniT> ... danbri & JeniT will have to make the request for these short names
13:19:42 <JeniT> ... point to the editor drafts & say what they do
13:19:46 <JeniT> ... it won't be out of the blue
13:20:39 <danbri> ivan: no formal template, but not a big deal. can cc chairs.
13:20:46 <JeniT> ivan: in parallel I'll contact web master
13:20:48 <danbri> … i can contact webmaster as a placeholder
13:21:03 <JeniT> ... I've already started checking the documents; I'll merge changes etc
13:21:31 <JeniT> ... I propose publishing 27th March
13:21:51 <JeniT> danbri: ok, we'll get the request out
13:22:03 <JeniT> ... when do we lose you?
13:22:22 <JeniT> ivan: early April, hence trying to publication before then
13:22:51 <JeniT> danbri: what about minutes publishing?
13:23:05 <JeniT> ivan: I'll take care of it, but probably with some delay
13:23:54 <JeniT> Topic: Subgroups on Conversions
13:24:06 <danbri> "Sub-groups to explore RDF/JSON/XML mapping systems (that address our use cases)"
13:24:23 <JeniT> https://www.w3.org/2013/csvw/wiki/Conversions
13:24:28 <danbri> jeni: dan and i propose subgroups on particular conversions, for rdf and json; and if a requirement, for xml as well.
13:24:35 <danbri> see wiki page ^—
13:24:58 <danbri> each group would look at what info is needed to convert something in tabular data model + annotations, into xyz format
13:25:12 <danbri> zakim, who is talking?
13:25:22 <Zakim> danbri, listening for 10 seconds I heard sound from the following: yakovsh (10%), gkellogg (4%), danbri (28%), JeniT (42%), tfinin (4%)
13:25:39 <danbri> "idea is … if each group does this semi-independently, as a whole group we can look at overlaps
13:25:55 <danbri> e.g. if each group needs to know about datatypes for particular values, we can resolve what that looks like for whole group.
13:26:04 <danbri> "is this a reasonable way forward?"
13:26:05 <danbri> q?
13:26:05 <ivan> q+
13:26:09 <AndyS> q+ to ask about a "direct mapping" style
13:26:12 <danbri> ack ivan
13:26:30 <JeniT> ivan: I'm worried about strictly separating the various conversions
13:26:40 <JeniT> ... we discussed that the JSON and RDF conversions may be part of the same thing
13:26:45 <JeniT> ... ie using JSON-LD
13:26:57 <JeniT> ... I'm worried that if we strictly separate them, we'd remove a possible synergy
13:26:58 <danbri> q+ to suggest that someone can simultaneously work on json and rdf
13:27:26 <gkellogg> The same could be said about XML, if RDF/XML is a reasonable way to publish XML
13:27:36 <danbri> jeni: i'm strongly of opinion that we should not aim for those synergies too early
13:27:47 <AndyS> I was going to join both because ... err ... will need both.
13:27:53 <danbri> we shouldln't prematurely assume that json users want json-ld too early. we might miss something.
13:28:19 <danbri> it's fine for the rdf group to think about how that might be done using XML, json(-ld), RDFa, etc.
13:28:47 <danbri> …but i want to make sure that we don't force people who are primarily interested in the browser to go through an unwanted rdf step
13:28:53 <danbri> ack andys
13:28:53 <Zakim> AndyS, you wanted to ask about a "direct mapping" style
13:29:16 <JeniT> AndyS: a common framework is to think of CSV as a big array of fields
13:29:31 <JeniT> ... if that's how people are used to using it in the browser, the JSON conversion should factor that in
13:29:48 <JeniT> ... we're looking very much at the annotated version of the data model
13:29:55 <JeniT> ... I was wondering about the direct mapping, without annotations
13:30:24 <yakovsh> q+
13:30:28 <danbri> jeni: I think in all the cases we should be looking at a conversion, … a default conversion unguided by annotations; and that the annotations then are tweaks over the top
13:30:56 <danbri> ack danbri
13:30:56 <Zakim> danbri, you wanted to suggest that someone can simultaneously work on json and rdf
13:31:09 <JeniT> AndyS: ok, we do have to factor in the direct mapping
13:31:29 <JeniT> danbri: we should avoid being tribal here, eg words like 'RDF people' or 'XML people'
13:31:46 <JeniT> ... this group is full of pragmatists who use a bunch of technologies
13:31:56 <AndyS> PS We did briefly mention doing RDF via the abstract data model.  Should all work out with direct to JSON-DL.
13:32:16 <JeniT> ... ivan's concerns that we fork too early won't apply because we'll all be watching the mailing list
13:32:27 <JeniT> ... we shouldn't rule out JSON-LD, but we shouldn't assume it
13:32:33 <danbri> q?
13:32:36 <JeniT> ... the use cases should keep us on track
13:32:39 <gkellogg> q+
13:32:46 <danbri> ack yakovsh
13:32:55 <ivan> ack yakovsh
13:33:01 <JeniT> yakovsh: I agree with danbri that groups with subgroups tend to fracture
13:33:17 <JeniT> ... also, are the conversions well-defined formats?
13:33:23 <JeniT> ... do all three need their own media types?
13:33:39 <JeniT> danbri: I don't think we need media types necessarily
13:33:54 <JeniT> ... the RDF group in particular, don't need them
13:34:11 <JeniT> yakovsh: there are JSON & XML media types that are separate
13:34:45 <danbri> jeni: yes, as discussed on the list, depends on how the conversion is done, e.g. you could map into JSON that explicitly says 'there is a table with these columns', …
13:34:51 <danbri> … json properties for table/column/row
13:35:01 <danbri> … which could be an explicit media type for tabular data in json
13:35:14 <danbri> (and same in xml, <row>, <column>, <field>, ...)
13:35:18 <ivan> q+
13:35:28 <danbri> ….but i think more likely our mappings will be based on particular csv original documents
13:35:51 <danbri> q+ to ask if we should be targetting existing XML and JSON idioms (e.g. SportsML for a sports CSV)
13:35:59 <danbri> ack gkellogg
13:36:18 <JeniT> gkellogg: I'd suggest that a direct mapping to JSON, based on column headings is compatible with JSON-LD
13:36:31 <JeniT> ... with zero edits, plus the context
13:36:42 <JeniT> ... doesn't mean it solves every desire to convert the data
13:36:53 <JeniT> ... I think a direct mapping plus a JSON-LD context does quite a lot
13:36:59 <JeniT> ... and obviously gets us part way to RDF
13:37:01 <danbri> ack ivan
13:37:17 <JeniT> ivan: one more question from yakovsh was about well-defined format
13:37:35 <JeniT> ... we need to do more than an example, but a clear formal specification of a mapping
13:37:39 <JeniT> ... a clear standard mapping definition
13:37:56 <JeniT> ... also I wanted to add: I haven't looked at the details of the use cases in terms of these mappings
13:38:08 <JeniT> ... but it would be good to look at the practice on how the mapping to JSON happens in those examples
13:38:15 <JeniT> ... what is the usage of that in the real world
13:38:29 <JeniT> ... and adding use cases on the conversion side rather than the structure of the CSV file
13:38:35 <JeniT> ... those use cases & requirements might be useful
13:38:42 <danbri> q?
13:38:46 <JeniT> ... there's no point having a specification that's completely different from what's done out there
13:38:46 <danbri> ack danbri
13:38:46 <Zakim> danbri, you wanted to ask if we should be targetting existing XML and JSON idioms (e.g. SportsML for a sports CSV)
13:39:10 <danbri> eg. ical https://tools.ietf.org/html/rfc6321
13:39:14 <JeniT> danbri: as we map into particular XML languages etc: should we have a goal of mapping into fixed formats?
13:39:22 <yakovsh> open document xml
13:39:23 <JeniT> ... eg ical, SportsML
13:39:32 <JeniT> ... in XML we might use XSLT to map into one of these formats
13:39:42 <JeniT> ... but is that our aim?
13:39:50 <danbri> zakim, who is talking?
13:40:02 <Zakim> danbri, listening for 10 seconds I heard sound from the following: yakovsh (19%), danbri (46%)
13:40:12 <tfinin> ML370?
13:40:32 <ivan> q+
13:40:47 <danbri> ack ivan?
13:40:52 <danbri> ack ivan
13:41:20 <JeniT> ivan: I think it's somewhere in between: I think if we say we should be able to map a CSV file to any XML schema or any RDF vocabulary out there, we will have to define something fairly complicated
13:41:37 <JeniT> ... it's equivalent to what the RML work did, on converting relational databases to RDF
13:42:00 <JeniT> ... that said, if there's something in the middle, in simple cases we might add something in the metadata
13:42:03 <AndyS> To gregg -- /me worried about putting JSON-LD algorithms on RDF path.
13:42:07 <Zakim> -fresco_
13:42:13 <JeniT> ... to help with the conversion, to produce an RDF closer to what's desired
13:42:23 <JeniT> ... I wouldn't want to be able to do it automatically with any vocabulary out there
13:42:24 <JeniT> q+
13:42:29 <danbri> ack jenit?
13:42:35 <danbri> ack jenit
13:42:40 <yakovsh> +q
13:42:59 <danbri> jenit: in other places, you can hand off to another system for the conversion
13:43:01 <andimou> *equivalent to what R2RML does with Relational Databases, RML extends R2RML and maps CSV/XML/JSON to RDF
13:43:16 <danbri> eg. grddl turns normal XMLs into RDF via XSLT files
13:43:42 <danbri> we might want to consider that we do need to discuss on the list, whether we want to have the option to bug out to such languages
13:43:44 <danbri> (bug?)
13:43:54 <ivan> +1 to Jeni
13:44:00 <danbri> …eg. ptr to an xslt file over a standard mapping into a specific format
13:44:03 <danbri> or construct
13:44:35 <danbri> jeni: using those kinds of langs might be worthwhile
13:44:55 <JeniT> danbri: an easy win is to reuse the hard work of other groups
13:45:04 <JeniT> ... eg the work of the relational-to-RDF mapping work
13:45:23 <JeniT> ... Barry Norton has mapped musicbrainz data into linked data
13:45:28 <JeniT> ... he's dropping down into SQL all the time
13:45:42 <JeniT> ... in some use cases, that's just right: in other cases XSLT might give us that flexibility
13:45:59 <JeniT> ... in browsers they might use Javascript
13:46:07 <danbri> q?
13:46:29 <JeniT> yakovsh: we're talking about conversion into JSON/XML/RDF, very removed from what users see
13:46:31 <danbri> musicbrainz example: https://github.com/LinkedBrainz/MusicBrainz-R2RML/blob/master/mappings/artist.ttl
13:46:45 <JeniT> ... what about open document XML and open XML, the document formats?
13:46:47 <danbri> http://en.wikipedia.org/wiki/Comparison_of_Office_Open_XML_and_OpenDocument
13:46:56 <JeniT> ... if we're talking about conversions into formats, those are probably more common than anything else
13:47:07 <JeniT> ... getting a spreadsheet out of CSV is going to be very common
13:47:19 <danbri> q?
13:47:24 <ivan> ack yakovsh
13:47:25 <danbri> ack yakovsh
13:47:29 <JeniT> danbri: that might be an unarticulated aspect of one of our existing use cases, we should take a look
13:47:43 <danbri> action: danbri scan use cases to see if http://en.wikipedia.org/wiki/Comparison_of_Office_Open_XML_and_OpenDocument are mentioned/implied
13:47:43 <trackbot> Created ACTION-8 - Scan use cases to see if http://en.wikipedia.org/wiki/comparison_of_office_open_xml_and_opendocument are mentioned/implied [on Dan Brickley - due 2014-03-26].
13:47:54 <JeniT> ivan: if I look at open document format, if I converted to that, it's down to Excel or OpenOffice, but these systems can do it directly from CSV
13:48:00 <JeniT> ... so there's no need to convert
13:48:15 <JeniT> ... is there a significant use case of systems other than traditional spreadsheet programs
13:48:29 <JeniT> ... that want to manipulate another format because they can't use the comma-separated version
13:48:53 <JeniT> danbri: last time I looked at the open office format, it was a container that had lots of extensibility points
13:49:05 <JeniT> ... even within XML languages, some are more specific than others
13:49:28 <JeniT> yakovsh: the point might be that these programs already handle CSV conversion, so no point because it's already built in
13:49:35 <JeniT> ivan: yes, I want to see if there are uses outside traditional spreadsheets
13:49:43 <JeniT> q+
13:50:01 <ivan> ack JeniT
13:50:25 <danbri> jenit: also considering importing into a relational database
13:50:34 <danbri> … also can apply to spreadsheet formats
13:50:58 <danbri> … would be useful to know types of columns, to format; to create database structures etc.
13:51:12 <danbri> … maybe we need a kind of focus in this area, to make sure we collect useful metadata
13:51:19 <danbri> q?
13:51:40 <danbri> jenit: do we need a focus group on reading csv into spreadsheets, relational databases
13:51:55 <JeniT> danbri: why not MatLab or R etc?
13:52:35 <JeniT> JeniT: I think we should be looking at those: that's what data scientists use
13:52:50 <danbri> q?
13:52:51 <JeniT> danbri: we should make some initial forays and see where we get
13:53:35 <danbri> jenit: maybe given earlier discussion, instead of 'sub-groups', think of them as products we're aiming at
13:53:52 <danbri> so we'd need a lead editor on each, with co-editors etc
13:54:07 <danbri> … and yes let's have a 4th, csv reading into tabular data stores of various kinds
13:54:19 <danbri> (dan: I'd say structures/frameworks not stores)
13:54:26 <yakovsh> +q
13:54:34 <danbri> ack yakov
13:54:47 <JeniT> yakovsh: I believe Part 9 of SQL discusses how they load CSVs
13:54:57 <JeniT> ... we should look at that
13:55:00 <danbri> http://en.wikipedia.org/wiki/SQL/MED
13:55:04 <danbri> http://en.wikipedia.org/wiki/SQL:2011
13:55:44 <JeniT> JeniT: yes, all of the conversions are going to have to take into account existing work
13:55:55 <JeniT> yakovsh: Postgres is the only one I think that has a full implementation
13:56:10 <JeniT> danbri: musicbrainz data is shared as a Postgres dump, which isn't a good way of sharing data
13:56:17 <danbri> q?
13:56:20 <AndyS> q+ to ask about "sub group"
13:56:21 <JeniT> ... maybe they could look at CSV support from Postgres
13:56:31 <danbri> ack andys
13:56:31 <Zakim> AndyS, you wanted to ask about "sub group"
13:56:56 <JeniT> AndyS: what does 'sub group' mean? are we discussing on the main mailing list?
13:57:22 <JeniT> danbri: we'll focus on products: all discussion on main mailing list, but having these as focused efforts & documents
13:57:51 <JeniT> Topic: TPAC
13:58:04 <JeniT> danbri: anyone have a clear view on which days they want to meet? Mon/Tue or Thur/Fri?
13:58:14 <JeniT> ivan: I'd like Mon/Tue because I have to be in another group Thur/Fri
13:58:15 <danbri> ivan: pref mon/tues
13:58:18 <JeniT> danbri: ok
13:58:20 <yakovsh> no particualr pref
13:58:29 <JeniT> ... any objections to mon/tue?
13:58:32 <JeniT> none heard
13:58:36 <danbri> action: danbri to request mon/tues tpac meeting
13:58:36 <trackbot> Created ACTION-9 - Request mon/tues tpac meeting [on Dan Brickley - due 2014-03-26].
13:59:01 <JeniT> danbri: please someone volunteer to scribe next week
13:59:13 <Zakim> -gkellogg
13:59:16 <Zakim> -Ivan
13:59:17 <Zakim> -JeniT
13:59:19 <Zakim> -tfinin
13:59:19 <Zakim> -danbri
13:59:22 <Zakim> -ericstephan
13:59:24 <Zakim> -DavideCeolin
13:59:25 <Zakim> -MathewThomas
13:59:25 <Zakim> -yakovsh
13:59:36 <Zakim> -andimou
13:59:46 <Zakim> -AndyS
13:59:46 <Zakim> DATA_CSVWG()9:00AM has ended
13:59:46 <Zakim> Attendees were +1.937.207.aaaa, yakovsh, danbri, gkellogg, JeniT, Ivan, +1.410.461.aacc, AndyS, MathewThomas, DavideCeolin, tfinin, +1.509.554.aadd, ericstephan, fresco_, andimou
14:00:40 <danbri> thanks all
14:00:47 <ivan> rrsagent, draft minutes
14:00:47 <RRSAgent> I have made the request to generate http://www.w3.org/2014/03/19-csvw-minutes.html ivan
15:42:19 <JeniT> JeniT has joined #csvw
16:26:26 <Zakim> Zakim has left #csvw
16:34:56 <danbri1> danbri1 has joined #csvw
17:21:24 <gkellogg> gkellogg has joined #csvw