- From: Tandy, Jeremy <jeremy.tandy@metoffice.gov.uk>
- Date: Mon, 16 Jun 2014 08:38:35 +0000
- To: Ivan Herman <ivan@w3.org>, Jeni Tennison <jeni@jenitennison.com>
- CC: "public-csv-wg@w3.org" <public-csv-wg@w3.org>
Hi - definitely agree with move to ".json" & need to recognise use of JSON-LD (which is itself JSON). Is there a filename suffix convention for JSON-LD or is (plain old) ".json" sufficient? Jeremy > -----Original Message----- > From: Ivan Herman [mailto:ivan@w3.org] > Sent: 15 June 2014 14:20 > To: Jeni Tennison > Cc: public-csv-wg@w3.org > Subject: Re: Extension for metadata file > > Another alternative would be to use .jsonld (I guess we agreed that the > metadata is, in fact, in JSON LD). The media type of JSON LD is > /ld+json; I am not sure how well the '+' approach is honoured by > different tools (I am not too optimistic...). > > I do not feel strong about it, but I thought we should at least give it > some thought... > > Ivan > > --- > Ivan Herman > Tel:+31 641044153 > http://www.ivan-herman.net > > (Written on mobile, sorry for brevity and misspellings...) > > > > > On 15 Jun 2014, at 13:39, Jeni Tennison <jeni@jenitennison.com> > wrote: > > > > Hi, > > > > I’ve created a pull request [1] for changing from using `.csvm` as > the extension for metadata files to using `.json`. The reason for the > change is that we’ve concluded (I think) that we’ll use JSON as the > format for the metadata file, and it’s a lost easier for users if that > JSON is automatically displayed/formatted as JSON in editors etc, which > it will be if the `.json` extension gets used. > > > > Thoughts? > > > > Jeni > > > > [1] https://github.com/w3c/csvw/pull/21 > > -- > > Jeni Tennison > > http://www.jenitennison.com/ > >
Received on Monday, 16 June 2014 08:39:04 UTC