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

no support for internationalization #126

Open
cmungall opened this issue Dec 22, 2022 · 1 comment
Open

no support for internationalization #126

cmungall opened this issue Dec 22, 2022 · 1 comment
Labels
1.4 major issues issues that are priority to address in 1.6

Comments

@cmungall
Copy link
Member

No standard way to specify string literal language (and interoperate with built-in RDF syntax for this)

@cmungall cmungall added the 1.4 major issues issues that are priority to address in 1.6 label Dec 22, 2022
@althonos
Copy link
Member

Regarding this, I think there is nothing in the spec that conflicts with the usage of a language tag the same way they exist in OWL syntaxes: this means that you could have a language tag after quoted and unquoted strings, not inside:

synonym: "nageoire pectorale"@fr EXACT [VSAO:0000147]

to take back the example from #93.

The advantage of this is that it's easier to map to OWL, and the escaping is more obvious: for quoted strings you don't need escaping, for unquoted strings you do, just like for most special characters.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1.4 major issues issues that are priority to address in 1.6
Projects
None yet
Development

No branches or pull requests

2 participants