Re: agenda for a CSVW call tomorrow?

Hi-

I note that there are a couple of emails with comment on the csv2* CR
publications; JSON [1] and RDF [2]. As yet unprocessed, but not forgotten.

I don't think there's anything urgent; mostly grammatical from a quick
parse. Will progress these in slow-time over the next few weeks; making
changes in GitHub as necessary.

Jeremy

[1]: https://lists.w3.org/Archives/Public/public-csv-wg/2015Jul/0062.html
[2]: https://lists.w3.org/Archives/Public/public-csv-wg/2015Jul/0060.html

On Tue, 28 Jul 2015 at 16:18 Yakov Shafranovich <yakov-ietf@shaftek.org>
wrote:

> I just sent something to IETF's general discussion list and the app
> area group as well.
>
> Yakov
>
> On Tue, Jul 28, 2015 at 10:45 AM, Dan Brickley <danbri@google.com> wrote:
> > Jeni wrote last week "will be around next week, then off for two."
> > Jeremy too.  I'll also be away some in August too. We could have a
> > call tomorrow, but is there sufficient agenda? I'll be around but we
> > should let Gregg know whether to set his alarm clock. Gregg and I had
> > a chat yesterday in IRC. He reports that all his issues are in the
> > tracker.
> >
> > Last week we agreed that the testcases are accepted
> > (https://github.com/w3c/csvw/issues/683).
> >
> > Nothing in https://github.com/w3c/csvw/issues seems burning urgent.
> >
> > We need to bounce these specs around a bit further and drum up some
> > implementations. I've just posted to semantic-web@, public-lod@ and
> > public-vocabs@. I'll also fwd that post on to the Schema.org Community
> > Group. Are there other groups that we should announce to, beyond those
> > already handled within W3C?
> >
> > Dan
> >
> > ps. I made a < 100 line not-really-an-implementation in python last
> > week to show the basic idea of the rdf mapping stuff.
> >
> https://github.com/w3c/csvw/blob/gh-pages/experiments/quick-python-demo/python-rdfize-demo.py
> > ... am looking at a D3.js version. I'm ashamed of how non-compliant
> > the script is but Gregg was kind about it so I've left it there for
> > now.
> >
>
>