Should primary keys be skipped from cell level triple (or k/v pairs) generation?

[iherman]

At the moment both specification generate a triple, resp. a k/v pair, for all cells in a row, including those that belong to a primary key column (and whose value is therefore reflected in the id of the whole row). Should these cells be skipped?

[JeniT]

@iherman Can you give an example to help us make a decision on this?

[iherman]

This may be moot in view of what we discussed, which may lead to dropping the primary keys. But the original issue was:

name1 | name2 | name3
"a" | "aa" | "aaa"
"b" | "bb" | "bbb"

and, say, name1 is declared as a primary key. In the current version of the mapping, the subject URI (for RDF) would be something like :a and :b, and then these triples are clearly generated:

:a :name2 "aa"; :name3 "aaa" .
:b :name2 "bb"; :name3 "bbb" .

what is not clear is whether the following triples should also be generated or not:

:a :name1 "a".
:b :name2 "b".

Ivan

On 31 Oct 2014, at 15:38 , Jeni Tennison notifications@github.com wrote:

@iherman Can you give an example to help us make a decision on this?

—
Reply to this email directly or view it on GitHub.

---

Ivan Herman, W3C
Digital Publishing Activity Lead
Home: http://www.w3.org/People/Ivan/
mobile: +31-641044153
GPG: 0x343F1A3D
WebID: http://www.ivan-herman.net/foaf#me

[JeniT]

@iherman Can you update this? Is it still an issue?

[iherman]

I have the impression that this has been overtaken by events. If my memory is correct, at that time the primary key played a role in generating the subject, but this has now been taken over by the aboutUrl property. Ie, the issue is probably moot? Do you agree?

[JeniT]

I think there's still an issue, where valueUrl is used, that we then only get a pointer to the resource (the URL generated by valueUrl) when we might also want a pointer to the original literal value held in the column. This relates to the need for phantom columns #179.

Possible resolution: when valueUrl is used, the resulting resource is also given an rdfs:label property (or just label in the JSON mapping) that holds the original value from the column.

[iherman]

On 04 Feb 2015, at 17:52 , Jeni Tennison notifications@github.com wrote:

I think there's still an issue, where valueUrl is used, that we then only get a pointer to the resource (the URL generated by valueUrl) when we might also want a pointer to the original literal value held in the column. This relates to the need for phantom columns #179.

Possible resolution: when valueUrl is used, the resulting resource is also given an rdfs:label property (or just label in the JSON mapping) that holds the original value from the column.

I like that.

Ivan

—
Reply to this email directly or view it on GitHub.

---

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