search

opengeospatial / ogc-geosparql

Public Repository for the OGC GeoSPARQL Standards Working Group
73 stars 20 forks source link

Add annotation in other languages next to English #43

Open FransKnibbe opened 3 years ago

FransKnibbe commented 3 years ago

This issue corresponds with OGC Standards tracker request 660.

For greater worldwide adoption of the GeoSPARQL standard, it would be good if the annotation (comments, definitions, descriptions) in the ontology is in more languages than English. Adding translations could be done on the basis of available linguistic knowledge within the SWG. This enhancement could work particularly well with publication of the ontology in JSON-LD format, allowing definitions to be easily incorporated in web pages.

nicholascar commented 3 years ago

See the DCAT2 ontology RDF file which has multiple languages in it for title & description properties: https://github.com/w3c/dxwg/blob/gh-pages/dcat/rdf/dcat2.ttl

mathib commented 3 years ago

Some experience from the W3C Linked Building Data group regarding the translation of the Building Topology Ontology (BOT):

Easiest workflow is to work in English until the main content is ready for a milestone. From then on, we worked in a Google Spreadsheet for collaborative preparation of translations. During the preparation of translations, issues tend to arise regarding certain (original English) definitions of concepts and these have to be corrected while previous translations need to be kept in sync or marked as "outdated". Whenever translations were outdated, they got marked in a color so that the translator responsible for it knows that the definition has changed and he/she needs to update it.

We used a script to transform the final CSV data to RDF, after performing a quick check with an automatic translation service for filtering out hijacked descriptions

nicholascar commented 3 years ago

We could do this: perhaps then we just need to link to a Google Spreadsheet from one of the README files in the repo?

nicholascar commented 3 years ago

Can people please nominate here for other language translations so we know who's keen? From today's meeting minutes, we have:

Nominee Language(s)
@kjano Polish
German
@situx German
@FransKnibbe Dutch
Gabriela Wiersma Portuguese

Any others? If you comment below, I will update this table.

dr-shorthair commented 3 years ago

@nicholascar Tongan ;-)

mathib commented 3 years ago

We might need to ask people from other communities (DCAT, LBD, etc.) for translations in other languages?

nicholascar commented 3 years ago

people from other communities

As long as we get 2+ translations done by us, the precedent will have been set, so others can be pointed at those and know how to contribute more.

FransKnibbe commented 3 years ago

It is probably best to do the translations just before publication of a new version, i.e. when the annotation in English is stable. Before that time, we could test scripts for exporting annotation to CSV and back again, to avoid delays later on.

mathib commented 3 years ago

I can ask for the script we used in the LBD group

mathib commented 3 years ago

I've just shared an adjusted spreadsheet and prepared a conversion script to generate triples through the internal mailing list.

FransKnibbe commented 3 years ago

I've just shared an adjusted spreadsheet and prepared a conversion script to generate triples through the internal mailing list.

Which mailing list is that? I have not seen it yet. We could make a new folder in the code tree for utilities.

mathib commented 3 years ago

Which mailing list is that? I have not seen it yet. geosparql.swg@lists.opengeospatial.org

We could make a new folder in the code tree for utilities. It's a Google Spreadsheet and a Google App Script for convenience. I can publish it as a .xls file and .gs (well javascript) respectively on the repo.

FransKnibbe commented 3 years ago

@mathib: geosparql.swg@lists.opengeospatial.org is not a public list, so I can not use it. For me and others without OGC membership it would be good to use this repository.

mathib commented 3 years ago

okay, that's a bummer. I had the idea that everyone was in that mailing list. I'll share the editable link with your gmail. If others are not in the mailing list, please let me know so I can give you the link directly

FransKnibbe commented 3 years ago

@mathib: Thank you, I have access to the spreadsheet now. Assuming that it is possible for all contributors to access and edit the same spreadsheet, how does getting the data out work? Can we export to TTL and merge that with the ontology?

By the way: geosemweb@lists.ogc.org is a public list. It could be used as an alternative to geosparql.swg@lists.opengeospatial.org.

mathib commented 3 years ago

It's currently running automatically (at least when I change stuff), creating text (Turtle formatted) in the Triples sheet. The different cells can be copy/pasted from there to the GeoSPARQL Turtle files. Further automation might be needed in the future, but for now this will do.

I don't think sharing an editable link to an open mailing list is a good idea. Maybe only for a limited period of time, when the English definitions are ready and checked, and when we need more translations from people outside the GeoSPARQL group.

FransKnibbe commented 3 years ago

@mathib: I like the plan. As a test, I made a small change. But generating altered triples failed because the function WriteTurtle could not be found. Perhaps the script needs to be shared too?

jabhay commented 2 years ago
Nominee Language(s)
@kjano Polish
German
@situx German (https://github.com/opengeospatial/ogc-geosparql/pull/240)
@lvdbrink Dutch
Gabriela Wiersma Portuguese
oldskeptic commented 2 years ago

Can people please nominate here for other language translations so we know who's keen?

@nicholascar If you don't mind lurker contributions, put me down for french.

nicholascar commented 2 years ago

@oldskeptic we'll take what's on offer!

We have a translation precedence now - the German version at https://github.com/opengeospatial/ogc-geosparql/pull/240 - so please follow that labels-only form.

You're probably free to translate now since the ontology is extremely unlikely to change much before release, but there is no rush here: you could also wait until close to release (some time in Jan/Feb).

dr-shorthair commented 2 years ago

@nicholascar Tongan ?

oldskeptic commented 2 years ago

@oldskeptic we'll take what's on offer!

We have a translation precedence now - the German version at #240 - so please follow that labels-only form.

You're probably free to translate now since the ontology is extremely unlikely to change much before release, but there is no rush here: you could also wait until close to release (some time in Jan/Feb).

@nicholascar Please confirm replacing rdfs:label with skos:prefLabel and rdfs:comment with skos:definition ?

nicholascar commented 2 years ago

@oldskeptic yes, that is correct. We have adopted the more specific SKOS properties.

dr-shorthair commented 2 years ago

I've also transitioned to SKOS-first in a number of vocabs that I'm managing.

oldskeptic commented 2 years ago

I have a french translation ready for a pull request based on the german template. Is there a file where I should add my name for credit purposes?

nicholascar commented 2 years ago

@oldskeptic why don't you add an owl:Ontology element to each file that you've made and add yourself in as the creator there, just like this:

https://github.com/opengeospatial/ogc-geosparql/blob/master/1.1/geo.ttl#L24

I note that @situx hasn't added himself to the German files at https://github.com/opengeospatial/ogc-geosparql/tree/master/1.1/translations in this manner, but perhaps he should.