- From: Ivan Herman <ivan@w3.org>
- Date: Sun, 14 Dec 2014 09:50:07 +0100
- To: Jeremy Tandy <jeremy.tandy@gmail.com>
- Cc: W3C CSV on the Web Working Group <public-csv-wg@w3.org>, Jeni Tennison <jeni@jenitennison.com>
- Message-Id: <7BCDA1F1-3E27-4B9B-BD7F-9A918D489666@w3.org>
Jeremy, another thing that I realized since I sent my previous mail. To emphasize again, I do not think this should be done _now_, but to consider it after the FPWD publication. Several steps in 4.1.1. are not JSON specific, namely the creation of what you called column description objects. Although you have not published the RDF mapping yet, I would expect that to include the very same steps. The reason is that, in fact, the generation of JSON is based on what I would also call an expanded metadata, which essentially means the fully expanded version of the core metadata with all the inherited properties being added so that the column description objects would correspond to the "schema" part of the metadata. I think it might be a better way of presenting this if we could somehow factor this out in the document and, actually, among the conversion documents. I see two viable possibilities 1. As a separate section in each conversion document that would be exactly identical 2. As a separate section in the metadata document (hence my explicit cc to Jeni:-) #2 would have the advantage of making the procedures clear for other applications than conversions, but it may not fit the overall goals of the metadata document. If we go #1, we may end up with a version hell. Fortunately, respec may come to our rescue for #2: the data inclusion possibility ([1], or possibly [2]) may take care of that. I think I am more in favour of #1 at this point, but only mildly; #2 may also work. WDYT? Ivan [1] http://www.w3.org/respec/ref.html#data-include [2] http://www.w3.org/respec/ref.html#data-include-sync > On 11 Dec 2014, at 22:53 , Jeremy Tandy <jeremy.tandy@gmail.com> wrote: > > All - the [JSON mapping document][1] is now published to w3c/csvw:gh-pages and is ready for your review. Feedback welcome of course :-) > > My next job is to to the RDF mapping document; this will follow a very similar structure … > > Jeremy > > [1]:http://w3c.github.io/csvw/csv2json/ ---- Ivan Herman, W3C Digital Publishing Activity Lead Home: http://www.w3.org/People/Ivan/ mobile: +31-641044153 ORCID ID: http://orcid.org/0000-0003-0782-2704
Received on Sunday, 14 December 2014 08:50:38 UTC