- From: Phil Archer <phila@w3.org>
- Date: Fri, 18 Dec 2015 09:20:28 +0000
- To: Maik Riechert <maik.riechert@arcor.de>, public-dwbp-wg@w3.org
Morning Maik, When I first saw this I thought Agh! OK, I'll fix the error in the Editors draft for next time. However, reading through the example more carefully I think the error is deeper than that. It's a set of CSV files that are described by json files - but this isn't clear and I think you're right that it needs fixing. Ironic (I mean bad) that we made this mistake in a document published on the same day as the CSV work on which the example is based made it to Rec! I've raised this issue. The editors will get back to you when it's fixed. Phil Tracker: Issue-232 On 17/12/2015 20:51, Maik Riechert wrote: > Hi all, > > I just noticed that example 14 has a wrong media type for the DCAT > distribution: text/csv. It should be application/ld+json since this is > what bus_timetables_mycity.json is and since this is referenced by > downloadURL there is really no way around it, compared to accessURL. I > think downloadURL is the right one here though. > > If more type information should be included in the media type then this > could be done with the profile parameter of the JSON LD media type. One > idea could be that http://www.w3.org/ns/csvw defines such a profile URI > and such a profile could then put restrictions on the JSON-LD structure > that is allowed (such as having to use the JSON-LD context > http://www.w3.org/ns/csvw and forcing a certain fixed structure) making > it easier for clients. The media type could be: > application/ld+json;profile="http://www.w3.org/ns/csvw" Of course, no > idea if something like that is actually appropriate, I just saw this > idea used somewhere else > (http://www.w3.org/TR/activitystreams-core/#media-type). > > Cheers > Maik > > -- Phil Archer W3C Data Activity Lead http://www.w3.org/2013/data/ http://philarcher.org +44 (0)7887 767755 @philarcher1
Received on Friday, 18 December 2015 09:20:20 UTC