- From: Gregg Kellogg <gregg@greggkellogg.net>
- Date: Thu, 20 Mar 2014 10:08:17 -0700
- To: Andy Seaborne <andy@apache.org>
- Cc: Ivan Herman <ivan@w3.org>, Juan Sequeda <juanfederico@gmail.com>, W3C CSV on the Web Working Group <public-csv-wg@w3.org>
On Mar 20, 2014, at 9:52 AM, Andy Seaborne <andy@apache.org> wrote: > On 20/03/14 15:34, Ivan Herman wrote: >> >> On 20 Mar 2014, at 16:03 , Juan Sequeda <juanfederico@gmail.com> wrote: >> >>> I would say yes :) >>> >>> 1) Direct Mapping is completely automatic >>> 2) R2RML is a manual. >> >> Correct. The question for me is: do the use cases around justify the extra (non-trivial) effort of defining an R2RML-CSV? Remember that the definition of R2RML took over two years:-( > > Caution warranted - it needs to be scoped downwards. I hope (but can not prove) that the CSV mapping is less of a mountain. > > CSV-LD is a R2RML(-ish) mapping. Gregg's already started, so not 2 years :-) Yes, CSV-LD is much like R2RML, but I think we could complete a spec in fairly short order. For the direct mapping, this could be a default mapping done by automatically constructing a context along the lines Andy had suggested, and could fall out of that spec as well. One consideration, is converting CSV files with a very large number of rows. The CSV-LD model would essentially create a document for each row, so converting to RDF could be streamed, but some provision for BNode identifiers would need to be made, so that if some value maps to a BNode, it would be preserved across records and not result in a new BNode being minted, even though it had the same identifier. This isn't really a problem, but it would mean specifying an algorithm that extended the existing JSON-LD conversion algorithms to the degree that the BNode identifier mapping would persist so that the conversion can be streamed. Gregg > Andy > >> >> Ivan >> >>> >>> Direct Mapping bootstraps the R2RML. >>> >>> Btw, I would be interested in participating in the CSV to RDF effort. >>> >>> >>> Juan Sequeda >>> +1-575-SEQ-UEDA >>> www.juansequeda.com >>> >>> >>> On Thu, Mar 20, 2014 at 6:44 AM, Andy Seaborne <andy@apache.org> wrote: >>> On 20/03/14 11:31, Ivan Herman wrote: >>> >>> On 20 Mar 2014, at 11:40 , Andy Seaborne <andy@apache.org> wrote: >>> >>> On 19/03/14 23:09, Jeni Tennison wrote: >>> Hi, >>> >>> Now that the first two of our documents are getting published as first public working drafts, we are moving on to the next stage of our work, namely looking at conversion from tabular data into other formats. >>> >>> We have a wiki document here: >>> >>> https://www.w3.org/2013/csvw/wiki/Conversions >>> >>> that describes in very broad terms what we need to do. >>> >>> Specifically, we’re looking for volunteers to lead the efforts / edit four documents, specifying: >>> >>> * Conversion of CSV to RDF >>> >>> RDF to RDF had two conversion documents. >>> >>> I guess you meant RDB to RDF... >>> >>> Yes. Typo. s/x42/x46/ -- only one bit out. >>> >>> Andy >>> >>> >>> >>> Ivan >>> >>> >>> (with no strong advocacy) >>> With hindsight, was it a good idea? Should we do the same? >>> >>> * Conversion of CSV to JSON and/or a browser API >>> * Conversion of CSV to XML (possibly pending actually having a use case for this) >>> * Conversion of CSV into a tabular data platform / framework / store (eg into a spreadsheet application or relational database or application like R) >>> >>> Please step forward, by editing the wiki, to lead the work on one of these documents and/or volunteer to help someone else with the work that needs to go into it. Obviously everything will be discussed on the list, but lead editors are instrumental in framing those discussions. >>> >>> Thanks, >>> >>> Jeni >>> -- >>> Jeni Tennison >>> http://www.jenitennison.com/ >>> >>> >>> >>> >>> >>> ---- >>> Ivan Herman, W3C >>> Digital Publishing Activity Lead >>> Home: http://www.w3.org/People/Ivan/ >>> mobile: +31-641044153 >>> GPG: 0x343F1A3D >>> FOAF: http://www.ivan-herman.net/foaf >>> >>> >>> >>> >>> >>> >>> >>> >> >> >> ---- >> Ivan Herman, W3C >> Digital Publishing Activity Lead >> Home: http://www.w3.org/People/Ivan/ >> mobile: +31-641044153 >> GPG: 0x343F1A3D >> FOAF: http://www.ivan-herman.net/foaf >> >> >> >> >> > >
Received on Thursday, 20 March 2014 17:08:48 UTC