Review of Guideline #28

Review of Guideline #28

Formatting

Item	Outcome
Guideline complies with the Guideline-Template	Yes
Name of guideline responsible with affiliation is clearly stated	Yes

Is the audience of the guideline correctly specified?

Yes.

Is the expertise required to write the guideline correctly specified?

Yes.

Are the keywords well selected?

I would suggest to add the following keywords: "data format" and "data compression"

Are parts of the guideline too generic or too specific?

I think, the guideline is good, not too generic and not too specific. But Philippe is right: one could split this guideline into two: "Avoid usage of complex libraries" and "Avoid complex data formats" (see his comment below).

Does the guideline explicitly refer to the handbook? To which part of the deliverable is it relevant (e.g., chapter of D1.2/D1.3)?

No. The guideline is relevant to Chapter 4.2 of the deliverable D1.3. The advice should be mentioned in the introductory text of the Chapter 4.2 of D1.3.

Does the guideline specify the work done in the project that can benefit from the guideline?

Yes.

Other comments

(PhM) There are actually 2 Guidelines out of this one:
(PhM) 1. Do not use Heavy Libraries to code your application. Write it Pure C instead
(PhM) 2. Do not use complex data format. Use even RAW format when possible.
(PhM) So I'll write it this way

1. Guideline advice: I would split the guideline into two as suggested above and be more generic (i.e. use the term "data" instead of "image").

2. Insights that led to the guideline: The section is good. I would suggest to change "the memory resources required by the library while doing image compression and decompression" --> "the memory resources required by the library for image compression and decompression"

3. Recommended implementation method of the guideline along with a solid motivation for the recommendation: This section is good. It is generic but uses coincrete examples, which is good.

4. Instantiation of the recommended implementation method in the reference platform: This section is good. Please introduce the abbreviation IP properly.

5. Evaluation of the guideline in reference applications: Please change "get ride of" to "get rid of".

6. References: No references required. However, references to the mentioned image format definitions would be nice.

Track changes:

1. 30/07/2018: Made some formatting changes in the guidelines to cope with template.
2. 27/08/2018: guideline reviewed.