- From: Tandy, Jeremy <jeremy.tandy@metoffice.gov.uk>
- Date: Thu, 20 Feb 2014 14:06:52 +0000
- To: Tim Finin <finin@cs.umbc.edu>, "public-csv-wg@w3.org" <public-csv-wg@w3.org>
"""In general, the optional certainty measure can come at the end of any of the rows. There was also an option for relations that allowed people to include two provenance items (doc,offset,offset,offset). Using a 'universal relation' format with a fixed number of fields would then require twelve columns.""" Noted. Can you include rationale in the use case why fixed numbers of columns becomes clumsy? Many thanks, Jeremy -----Original Message----- From: Tim Finin [mailto:finin@cs.umbc.edu] Sent: 20 February 2014 13:34 To: public-csv-wg@w3.org Subject: Re: CSV+ file lines with differing number of columns On 2/19/14, 12:21 PM, Tandy, Jeremy wrote: > #1: this is a good example to include as a use case. I think there's > enough text here already ... it would be great if you could move > this across to the wiki... I'll do this. > #2: your example ... > :e4 type PER > :e4 mention "Bart" D00124 283-286 > :e4 per:siblings :e7 D00124 283-286 173-179 274-281 > :e4 per:age "10" D00124 180-181 173-179 182-191 0.9 > ... seems to be quite regular; from your description, the column > headings might be: > > subject,predicate,object,document-id,string-offset-1,string-offset-2,string-offset-3,confidence > > thus, in comma delimited form, your variable-length rows become: > :e4,type,PER,,,,, > :e4,mention,"Bart",D00124,283-286,,, > :e4,per:siblings,:e7,D00124,283-286,173-179,274-281, > :e4,per:age,"10",D00124,180-181,173-179,182-191,0.9 In general, the optional certainty measure can come at the end of any of the rows. There was also an option for relations that allowed people to include two provenance items (doc,offset,offset,offset). Using a 'universal relation' format with a fixed number of fields would then require twelve columns.
Received on Thursday, 20 February 2014 14:07:21 UTC