Re: CR: Generating RDF from Tabular Data on the Web

Hello-

First, please accept apologies for taking so long to process your detailed
comments; thank you very much for taking the time to review the CSV2RDF CR
in such detail.

I believe that I have resolved the concerns that you raised (we captured
this in GitHub ISSUE #679 [1]). Please refer to PULL REQUEST #751 [2] for
details (this contains fixes for both CSV2RDF and CSV2JSON).

I've checked through to ensure use of en-us spelling.

I have also, I hope, fixed recurring examples of the issues you raised once.

Two points to raise.

First, in CSV2JSON, you suggested that the definition of "Root" should be
modified from "child of any vertex" to "child of another vertex". As
identified by David Booth in his email [3], I think the original was
correct. No change was made.

Second, you asked why, in the example below, "B.B. King" was not quoted.

example: http://example.org/events-listing.csv
```

Name, Start Date, Location Name, Location Address, Ticket Url
B.B. King,2014-04-12T19:30,"Lupo’s Heartbreak Hotel","79 Washington
St., Providence, RI",https://www.etix.com/ticket/1771656
B.B. King,2014-04-13T20:00,"Lynn Auditorium","Lynn, MA,
01901",http://frontgatetickets.com/venue.php?id=11766


```

Within tabular data, cells MAY be quoted - but do not have to be. Where the
cell value includes the separator character (e.g. comma `,`), wrapping the
cell value in quotes enables the cell value to be treated as a single item.
Please refer to 'Parsing Tabular Data' [4] for more information.

*Can you please confirm that you are content that the comments you raised
in relation to CSV2RDF have been appropriately resolved?*

Many thanks, Jeremy

[1]: https://github.com/w3c/csvw/issues/679
[2]: https://github.com/w3c/csvw/pull/751
[3]: https://lists.w3.org/Archives/Public/public-csv-wg/2015Jul/0064.html
[4]: http://www.w3.org/TR/tabular-data-model/#parsing

On Fri, 17 Jul 2015 at 07:56 timeless <timeless@gmail.com> wrote:

> http://www.w3.org/TR/2015/CR-csv2rdf-20150716/
>
> > In order to faciliate [sic] the provision of such information,
>
> > The resources described by each row are explcitly [sic] defined using
> the about URL annotation this case three resources per row
>
> > Tables in a relational databases bear a strong resemblence [sic] to
> tabular data as defined in [tabular-data-model];
>
> > else, the datatype's base annotation value MUST be mapped to the RDF
> datatype IRI using the table below.
>
> I expected to see a table below, instead I ran into a NOTE. Move the
> note? (or somehow fix reader expectation about immediacy of table)
>
> > the cell value has already been parsed from the contents the cell
> according to the format annotation.
>
> contents the => contents of the
>
> > Where the contents of the cell cannot be parsed, or other validation
> errors occur, cell errors will be provided.
>
> `will be provided` is odd, provided by whom?
>
> > It is an implementation decision to determine how conversion
> applications should proceed in the event that cell errors are encountered.
>
> occur/encountered is an odd mix
>
> > string xsd:string or rdf:langString depending on whether or not the
> value has an associated language.
>
> there's a remarks column, and most of this text probably belongs in it...
>
> > According to [rdf11-concepts] language tags cannot be combined with any
> other xsd datatypes.
>
> drop `any`
>
> > If a cell has any other datatype than string,
>
> any other datatype => a datatype other
>
> > specific serializations, like Turtle [turtle],
>
> you don't usually write `like Foo [foo]`, the document is written to
> be read as `like Foo foo` and thus you should probably just have `like
> [foo]` which reads as `like foo`.
>
> > In order to faciliate the provision of such information,
>
> the provision of => providing
>
> > through some application specific API-s.
>
> drop the `-`
>
> > Establish a new node S from the value of @id, if it exists, and new
> blank node otherwise and emit the following triple:
>
> and new => and a new
>
> > If value is true or false, create an RDF Literal lit using the strings
> "true" or "false", accordingly with datatype xsd:boolean
>
> missing `.`
>
> > Annotations for the resulting table T, with 4 columns and 3 rows, are
> shown below:
> > Annotations for the columns, rows and cells in table T are shown in the
> tables below.
>
> I kind of expected `:`
>
> > The datatype annotation is set on columns C5, C6, C8 and C9 ({ "name":
> "dbh"}, { "name": "inventory_date" }, { "name": "protected" } and { "name":
> "kml" });
> > integer, date, boolean and xml respectively.
>
> you're missing an `as` or `to` or similar after `;`
>
> > B.B. King,2014-04-13T20:00,"Lynn Auditorium","Lynn, MA, 01901",
> http://frontgatetickets.com/venue.php?id=11766
>
> why isn't `B.B. King` quoted? Or why is `Lynn Auditorium` quoted?
>
> > e.g. for row R1 we state [] csvw:describes t1:event-1, t1:place-1,
> t1:offer-1 . .
>
> this is hard to read without styling, please consider using ""s around
> the stuff, or something, otherwise `. .` is a mess...
>
> > This example is concerned only with converting the information provided
> each government department or organization not the centrally published
> information listing organizations and professions.
>
> provided => provided by
> not => `; not` or similar
>
> > Similarly, columns Cc7 and Cd8 (both with { "name": "organizationRef" })
> use the about URL, property URL and value URL annotations to assert the
> relationship between the given post and the organization to which it
> belongs for the cells those columns.
>
> `cells [in] those columns` ???
>
> > A processor exporting the table into a CSV file could also generate such
> a metadata automatically.
>
> such a => such  ???
>
> > Cells in both the city and state columns in the Addresses table contain
> strings
>
> missing `.`
>
> > The corresponding relational schema specifies that
>
> missing `:` ??
>
> > To generate the right object URI in the highlighted statement of the
> direct graph the processor has to find that unique key combination in the
> Departments table and,
> > using that combination,
> > has to establish the subject for that specific row that can is to be
> used as an object URI in the highlighted statement.
>
> 1. this is too long to be a sentence
> 2. `that can is to be` is wrong
> 3. once you fix the first two, the section should be revisited...
>
>