Key principles 101

[matuskalas]

Add the key principles of EDAM design that are not obvious, e.g.:

• What and not How (and even if a bit of how, then only when absolutely necessary). If how is an expected search term, add as either 'Related term' or narrow or related synonym. The primary label should always be more about what (except extreme cases where conceptual distinction is needed, e.g. morphological ops or segmentation techniques)
• Terms and synonyms cannot be used in multiple concepts. When necessary, add some words|modifiers to the term. Applies to 'Related term'-s, too. (But 'seeAlso' can be the same in multiple concepts)
• etc.

Add a link to these to https://github.com/edamontology/edam-bioimaging#contributing and the CONTRIBUTE file.

[matuskalas]

+ EDITING HINTS

Add to https://github.com/edamontology/edam-bioimaging#editing.

TO N.B.:

• Ask @matuskalas to get invited to Glip
• BLOCKER for adding one given subontology at a time; ask @matuskalas to change
• "Resolved" closes the whole thread! DO NOT use if not the whole thread solved
• Vice versa, open a NEW THREAD when appropriate

WONDERING: Any way to copy comment threads between concepts in WebProtégé? Would help us unbelievably!!!! And if even between ontologies, woudl be absolutely marvellous!

[joakimlindblad]

Consider a note on English spelling, with 2-3 examples.

[matuskalas]

I want write something in the sense of "as an effort to help preserving this disappearing cultural heritage, we use "strict" BrE spelling, and latin plural endings" :-DD

[matuskalas]

(and "only North American citizens are allowed to use AmE spelling, but not in primary terms" ;P)

[joakimlindblad]

And to do that they will have to present a passport at least!

[matuskalas]

(Luckily we don't have to mention the use of

• metric units
• right-side driving
• integrated water faucets

But the use of GMT yes;P)

[bogovicj]

What not How

so.. no need to describe what's under the bonnet of a given algorithm?

[martlj]

Or the mathS behind it.

[matuskalas]

so.. no need to describe what's under the bonnet of a given algorithm?

Nie, rozhodne nie ;-)

[bogovicj]

Relating to this:

(except extreme cases where conceptual distinction is needed, e.g. morphological ops or segmentation techniques)

It would be helpful to have some guidance on when/under what conditions distinctions are needed vs when topics should be grouped by being (narrow/related) synonyms of some parent.

E.g., Wavelet Transform and FFT are now "Related Synonyms" to Frequency Analysis, but there are seven children of Morphological operation. What should go into deciding "how deep to go" ?