-
Notifications
You must be signed in to change notification settings - Fork 47
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
Policy for translations in the RDF of DCAT #1352
Labels
Milestone
Comments
Makes perfect sense to me. |
I agree this is a good approach. |
The resolution voted during the last DCAT call says that "we accept a policy of deciding on the best efforts we will provide to translations when we get to the CR stage". |
should we close this or we need to make this clarification somewhere else? |
15 tasks
riccardoAlbertoni
added
the
due for closing
Issue that is going to be closed if there are no objection within 6 days
label
May 24, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
We need to agree on an internal policy on dealing with translations in the DCAT RDF.
It is not always possible to provide a proper translation for all the languages during the DCAT updates. And asking for translation for different languages during the process slows down PR's acceptance, imposing complex interactions between contributors.
I'd suggest maintaining only the English text while defining the specification and deal with the update of translations when we reach the CR or PR stage.
Does this sound like a reasonable strategy?
The text was updated successfully, but these errors were encountered: