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

Discussion: Name attestations #8

Open
kintopp opened this issue Jun 27, 2018 · 5 comments
Open

Discussion: Name attestations #8

kintopp opened this issue Jun 27, 2018 · 5 comments
Assignees

Comments

@kintopp
Copy link
Member

kintopp commented Jun 27, 2018

Is the RDF data being represented properly or is it missing and has to be added?

@kintopp kintopp self-assigned this Jun 27, 2018
@kintopp
Copy link
Member Author

kintopp commented Jul 4, 2018

We may want to be able to capture more than one language for a name attestation. And to switch to using three-letter ISO-639-3 codes.

@kintopp kintopp changed the title Check mappings for name attestations Discussion: Name attestations Aug 1, 2018
@gklyne
Copy link
Contributor

gklyne commented Aug 20, 2018

For languages, I'm using a language resource URI (currently private URI, but could be, e.g., lexvo) The language resource description both 2- and 3- letter codes could be supplied.

@gklyne
Copy link
Contributor

gklyne commented Aug 20, 2018

Can we close this issue?

@kintopp
Copy link
Member Author

kintopp commented Sep 5, 2018

I see that lexvo provides the necessary mappings and an API. Any reason to prefer private URI for this?

@gklyne
Copy link
Contributor

gklyne commented Sep 7, 2018

Mainly that I wasn't sure how widely used, well supported or generally stable it is. If it has a good following and support, then probably better to use that than new private terms.

(Partly my style of working: unless there's an obvious good candidate, I tend to use private namespaces with the intent of aligning later... but I'm not saying that's always, of even even, the best way.)

It seems we should keep this open until we make a final decision either way on Lexvo.

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

2 participants