You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
0:46 This shadow man looks eerie. Isn’t there somebody else? Or sth more positive? A flying bird for example?
slides
2:46 Dryad _> Dryad Digital Repository ?
2:52 dryad spelled with lower case, before it was Dryad. Make spelling consistent, also for the other repositories.
3:02 “Standardized” is British English, before you have been using AE. Make it consistent. These three sentences should consistently start with capitals and end with a period.
3:05 Use a -> delete “a”
I wonder: what are vocabularies (and I would not use it in plural form) that follow “fair” principles? Do you mean clear and transparent language? Well-defined terms/terminology?
3:14 “with a plurality” -> with a wealth of? variety of?
3:19 associated with detailed provenance -> information of provenance
text
0:46 spoken: should, written; shall. Should is correct.
0:54 spoken: “only while open” correct
“potential” , written: potention, correct is spoken
1:38 spoken: chance, written: chances. Written is correct
1:42 text disappears too fast to be read, it is also in too small letters. I would split it into two parts (at least)
1:42 spoken: or funded, written: and funded -> choose written
1:48 spoken: and NOW they , written: - both is possible, but maybe better keep it short
2:13 “happen in a swing” – I never heard this expression. It is also not in pons.de
2:26 “at the end, Research” -> IN the end, research
2:32 Researcher -> researchers (Kleinschreibung und Plural-S)
2:33 „to gear data“ -> – I never heard this expression. It is also not in pons.de
2:36 the -> they
2:37 “.” at the end of the sentence
Is it intented that there is no spoken text here?
Generally:
• Please make sure that the size of the letters remains the same.
• Please end every sentence with a period.
• A native speaker of English should proof-read the text.
The text was updated successfully, but these errors were encountered:
Feedback for https://rdmpromotion.rbind.io/blog/2018/11/02/a-video-about-open-data-as-a-new-standard/ v.2
From Petra (Jena RDM team)
video
0:46 This shadow man looks eerie. Isn’t there somebody else? Or sth more positive? A flying bird for example?
slides
2:46 Dryad _> Dryad Digital Repository ?
2:52 dryad spelled with lower case, before it was Dryad. Make spelling consistent, also for the other repositories.
3:02 “Standardized” is British English, before you have been using AE. Make it consistent. These three sentences should consistently start with capitals and end with a period.
3:05 Use a -> delete “a”
I wonder: what are vocabularies (and I would not use it in plural form) that follow “fair” principles? Do you mean clear and transparent language? Well-defined terms/terminology?
3:14 “with a plurality” -> with a wealth of? variety of?
3:19 associated with detailed provenance -> information of provenance
text
0:46 spoken: should, written; shall. Should is correct.
0:54 spoken: “only while open” correct
“potential” , written: potention, correct is spoken
1:38 spoken: chance, written: chances. Written is correct
1:42 text disappears too fast to be read, it is also in too small letters. I would split it into two parts (at least)
1:42 spoken: or funded, written: and funded -> choose written
1:48 spoken: and NOW they , written: - both is possible, but maybe better keep it short
2:13 “happen in a swing” – I never heard this expression. It is also not in pons.de
2:26 “at the end, Research” -> IN the end, research
2:32 Researcher -> researchers (Kleinschreibung und Plural-S)
2:33 „to gear data“ -> – I never heard this expression. It is also not in pons.de
2:36 the -> they
2:37 “.” at the end of the sentence
Is it intented that there is no spoken text here?
Generally:
• Please make sure that the size of the letters remains the same.
• Please end every sentence with a period.
• A native speaker of English should proof-read the text.
The text was updated successfully, but these errors were encountered: