-
Notifications
You must be signed in to change notification settings - Fork 0
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
Comments
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. |
For languages, I'm using a language resource URI (currently private URI, but could be, e.g., |
Can we close this issue? |
I see that lexvo provides the necessary mappings and an API. Any reason to prefer private URI for this? |
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. |
Is the RDF data being represented properly or is it missing and has to be added?
The text was updated successfully, but these errors were encountered: