-
Notifications
You must be signed in to change notification settings - Fork 23
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
German labels as alternative terms #1471
Comments
If the proposal is favoured, I think it could be useful to build upon German labels from existing and in-use vocabulary, such as EnArgus. |
If the concepts match -- why not. However, in a lot of cases we propably cannot match 1:1, for example EnArgus has For matching concepts we can additionally use the annotation property |
This is more a comment: I agree that German labels would be helpful not only for mapping, but also for using the OEO as e.g. dictionary for a wider public (@Ludee, didn't you suggest, that we could add easier to read German explanations of the most important terms some day?) If we agree that German lables are important for improving the comparison tool, what workflow should be applied then? Most of the German translations won't cause trouble, but some may need discussion. Would it make sense to create issues like "Add german label to existing classes: sector", "... : sector division" etc. with lists of all important classes within these higher level classes and then work through it? |
I think, it is best to discuss the workflow on the next OEO dev meeting. That's why I already added the oeo dev meeting label. |
As a short test, I took six core concepts of the OEO and listed how I would translated. Then I checked against EnArgus and found for only two of the six corresponding entries in EnArgus.
|
Using the search bar I found two more as full synonyms - plus derived "Energieübertragung" from "energy transfer system" = "Energieübertragungssystem". Input for the discussion.
|
Kraftstoff from EnArgus is not equivalent to our |
As discussed, I finalised the spreadsheet with the German labels and the EnArgus matching. However, I am not able to share this file via Google Docs. Does someone else have the possibility to share a spreedsheet in a way that it is accessible and editable without registration by user? If not, an alternative would be to export the spreadsheet to a CSV file and add this to feature branch. |
Now as a google docs document |
I worked today a bit on the table. In total we have in the list currently 1055 OEO classes and individuals 1. Of these 627 have one or more proposals for German labels. Additionally, 122 entries are matched to EnArgus. There are some very fundamental OEO concepts where we have do discuss to find good German labels:
Further, we have to find good translations for the BFO classes Footnotes
|
@han-f @stap-m @chrwm @u-mueller @carstenhoyerklick : Has anyone already had a look on the translations table? https://docs.google.com/spreadsheets/d/1snsx6zF8dqXGM9WCX0EckrdGnorrB9lMnvdvP2fx9ZQ/edit?usp=sharing |
I close this issue now. The enArgus matching that is also part of the spreadsheet can be reused in the enArgus issue #179. |
Description of the issue
In today's SIROP meeting we spoke shortly whether we should add German labels as alternative terms to all or at least the most relevant classes.
Ideas of solution
If you already have ideas for the solution describe them here
Workflow checklist
I am aware that
The text was updated successfully, but these errors were encountered: