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

How should language be used in RDF mapping? #59

Closed
iherman opened this issue Nov 4, 2014 · 5 comments
Closed

How should language be used in RDF mapping? #59

iherman opened this issue Nov 4, 2014 · 5 comments

Comments

@iherman
Copy link
Member

iherman commented Nov 4, 2014

The metadata may include a language tag, that is for the content of the data. How does this translate into RDF? Proposal:

  • If the content of the cell is not datatyped, and is not a URI, and the language tag's value is not "en", then the generated object should be a language literal with the global language tag set.

(Seems fairly uncontroversial, I put this as a possible entry to decide right away.)

@danbri
Copy link
Contributor

danbri commented Nov 12, 2014

Are there precedents (in CSV standards or W3C in general) for special-casing "en" in this way?

@danbri
Copy link
Contributor

danbri commented Nov 12, 2014

discussion: See http://www.w3.org/2014/11/12-csvw-irc#T15-18-27

@iherman
Copy link
Member Author

iherman commented Nov 13, 2014

Well... In HTML, if the language tag is not set, the language is considered to be in English...

But, indeed, we can leave that to the author. It is true, isn't it, that the language setting is not required in the metadata? If that is the case, we can use this: if there is no language setting, the output can be plain literal, and language literal otherwise.

Ivan

@6a6d74
Copy link
Contributor

6a6d74 commented Nov 18, 2014

Discussed in meeting 12-Nov-2014 (Minutes); summary ...

RESOLUTION: for RDF mapping, apply locale / language tag from metadata to all literal string values in output

RESOLUTION: for (plain old) JSON mapping, no locale information is added to the JSON output - we assume that people will look at the complimentary metadata for locale information

We agreed that for the 'plain old JSON' mapping, we don't include locale information because we want it to be as simple as possible. If people want locale, then they should use the RDF mapping & JSON-LD syntax.

Finally, we noted that if you want to say a particular locale for plain old json, you might say "property_en" or "property_fr". This mechanism could be used to distinguish between columns that confer the same property but in different languages. The 2-letter country code suffix gives a human readable hint.

We agreed not to implement anything regarding assumptions about "en" locale/language.

Issue not closed because the Mapping doc is not yet updated.

@6a6d74
Copy link
Contributor

6a6d74 commented Mar 5, 2015

csv2rdf doc 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

5 participants