Proposition de traduction : Introduction aux principes des données ouvertes liées

[marie-flesch]

Programming Historian en français a reçu une proposition de notre cher David Valentine (@davvalent ). Il propose la traduction de la leçon Introduction to the Principles of Linked Open Data, intitulée en français "Introduction aux principes des données ouvertes liées".

La traduction a été réalisée et sera confiée à un·e membre de l'équipe prochainement.

[charlottejmc]

Bonjour @marie-flesch et @davvalent,

Vous trouverez les fichiers ici :

• .md: /fr/en-cours/traductions/intro-donnees-ouvertes-liees.md
• images: /images/intro-to-linked-data
• assets: [none]

Vous pouvez parcourir l’aperçu de la soumission ici :

• http://programminghistorian.github.io/ph-submissions/fr/en-cours/traductions/intro-donnees-ouvertes-liees

---

Bonjour @davvalent, merci beaucoup pour la traduction ! Pourrais-je vous demander seulement de traduire les figure captions pour chaque image, ainsi que de rédiger le alt-text correspondant ? Nous n'avions pas encore introduit l'alt-text lors de la publication en anglais ou espagnol, mais il est présent dans la traduction en portugais, si ça peut vous aider.

Si vous avez des questions, nous avons quelques indications (en anglais), qui peuvent aussi vous être utiles :

The syntax which we use to embed figures within our lessons includes an 'alt-text': this descriptive element enables screen readers to read the information conveyed in the images for people with visual impairments, different learning abilities, or who cannot otherwise view them, for example due to a slow internet connection. It's important to say that 'alt-text' should go further than repeating the figure captions.

We have found Amy Cesal's guide to Writing Alt Text for Data Visualization useful. This guide advises that alt-text for graphs and data visualisations should consist of the following:

alt="[Chart type] of [data type] where [reason for including chart]"

What Amy Cesal's guide achieves is prompting an author to reflect on their reasons for including the graph or visualisation. What idea does this support? What can a reader learn or understand from this visual?

The Graphs section of Diagram Center's guidance is also useful. Some key points (relevant to all graph types) we can take away from it are:

• Briefly describe the graph and give a summary if one is immediately apparent
• Provide any titles and axis labels
• It is not necessary to describe the visual attributes of the graph (colour, shading, line-style etc.) unless there is an explicit need
• Often, data shown in a graph can be converted into accessible tables

For general images, Harvard's guidance notes some useful ideas. A key point is to keep descriptions simple, and adapt them to the context and purpose for which the image is being included.

Would you feel comfortable making a first draft of the alt-text for each of the figures? This is certainly a bit time-consuming, but we believe it is very worthwhile in terms of making your translation accessible to the broadest possible audience. We would be very grateful for your support with this.

Merci beaucoup !

[anisa-hawes]

Bonjour David @davvalent,

What's happening now?

Your lesson has been moved to the next phase of our workflow which is Phase 2: Initial Edit.

In this phase, your editor Daphné @DMathelier will read your lesson, and provide some initial feedback. They will post feedback and suggestions as a comment in this issue, so that you can revise your draft in the following phase (Phase 3: Revision 1).

%%{init: { 'logLevel': 'debug', 'theme': 'dark', 'themeVariables': {
              'cScale0': '#444444', 'cScaleLabel0': '#ffffff',
              'cScale1': '#3d7c81', 'cScaleLabel1': '#ffffff',
              'cScale2': '#444444', 'cScaleLabel2': '#ffffff'
       } } }%%
timeline
Section Phase 1 <br> Submission
Who worked on this? : Publishing Assistant (@charlottejmc) 
All  Phase 1 tasks completed? : Yes
Section Phase 2 <br> Initial Edit
Who's working on this? : Editor (@DMathelier)  
Expected completion date? : Feb 22
Section Phase 3 <br> Revision 1
Who's responsible? : Translator (@davvalent) 
Expected timeframe? : ~30 days after feedback is received

Loading

Note: The Mermaid diagram above may not render on GitHub mobile. Please check in via desktop when you have a moment.

[marie-flesch]

C'est @DMathelier qui effectuera le suivi éditorial de la leçon !

[davvalent]

Bonjour,

Merci à toutes pour les remarques initiales et les informations!

@charlottejmc Yes, I feel comfortable making a first draft of the alt-text for each of the figures. I'll include that in my planning. Thank you for the resources you pointed out.

@anisa-hawes Thank for that useful timeline! By the way I would like to let you know that I have spotted some issues in the original lesson that we should discuss. Some in code snippets, and some typos in the text. Do you want me to put that here in this thread?

@DMathelier J'aimerais solliciter ton avis concernant quelques remarques et questions en suspens pour cette traduction. Je prévois d’être en mesure de te les partager ici sous peu.

À très bientôt,

David

[DMathelier]

Bonjour @davvalent, c’est noté, prends le temps dont tu as besoin, notamment pour la rédaction des captions.
J’attends tes remarques puis ton feu vert pour commencer la relecture de la leçon :)
À bientôt !

[charlottejmc]

Merci @davvalent, we look forward to hearing your feedback on the issues you found, which you can describe right here in the comments. Translating a lesson is a great opportunity to renew and improve upon the original, and we are very grateful for your attention to detail.

You can edit the figure captions and alt-text directly in the markdown file once @anisa-hawes has granted you access to edit it.

One other opportunity for improvement here would be to translate the text in the diagrams of Figures 1 and 2 – I'll check whether we have "empty" copies of those figures which you could edit.

Thank you! ✨

[anisa-hawes]

Thank you, @davvalent!

I've double-checked and you already have the Write permission to make direct edits to your translation markdown file, /fr/en-cours/traductions/intro-donnees-ouvertes-liees.md.

We don't have 'mute' copies of the diagrammatic figures for this lesson, but they seem simple enough to recreate. Please let us know if you'd like our help with this. As Charlotte mentions, our CC-BY open licence invites and encourages adaptation for new audiences, so if there are adjustments you'd like to make we welcome that during the process of translation. If you found technical errors in the lesson, we can update the original lesson with your suggested changes as a maintenance issue - it is always helpful if we can fix glitches, so thank you in advance for your insights.

I wondered if you have considered localising the dataset in the case of this translation? As the lesson is an introduction to the principles of Linked Open Data it seems that the examples of a former British politician (as subject) and UK constituency (as object) is really incidental and could usefully exchanged for a francophone example. What do you think?