Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Should the mapping output for a given row include a reference to the CSV source row? #98

Closed
6a6d74 opened this issue Dec 9, 2014 · 6 comments

Comments

@6a6d74
Copy link
Contributor

6a6d74 commented Dec 9, 2014

Should the row mapping include a property to identify the source row from which it was derived; e.g. rdfs:isDefinedBy from RDF Schema 1.1?

@iherman
Copy link
Member

iherman commented Dec 9, 2014

On 09 Dec 2014, at 16:18 , Jeremy Tandy notifications@github.com wrote:

Should the row mapping include a property to identify the source row from which it was derived; e.g. rdfs:isDefinedBy from RDF Schema 1.1?

I think adding the information using, for example, the fragment id, would be indeed useful

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

@JeniT
Copy link

JeniT commented Dec 14, 2014

I think this is likely to be difficult to define and implement given the flexibility in how the tables that are converted are generated based on files that might have multiple header lines etc. I'd suggest leaving it for now.

@iherman
Copy link
Member

iherman commented Dec 15, 2014

On 14 Dec 2014, at 22:54 , Jeni Tennison notifications@github.com wrote:

I think this is likely to be difficult to define and implement given the flexibility in how the tables that are converted are generated based on files that might have multiple header lines etc. I'd suggest leaving it for now.

Yeah... but we may hit the same issues with the usage of the fragment id-s elsewhere, eg, for annotation. If we find a decent solution at that point, we can adopt it for this case, too.

I agree to leave this unchanged for now, but let us leave the option open.

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

@gkellogg
Copy link
Member

RESOLUTION: resolve #98 and #101 as Gregg suggests (from http://www.w3.org/2015/01/28-csvw-minutes.html).

@JeniT
Copy link

JeniT commented Feb 4, 2015

Resolution was to always emit a csvw:rownum triple referencing the source row (which we might make optional in the future).

@6a6d74
Copy link
Contributor Author

6a6d74 commented Mar 5, 2015

csv2rdf and csv2json docs updated as per resolution.

@6a6d74 6a6d74 closed this as completed Mar 5, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants