Loading Glossary… Severin Willig Mar 11 2026 at 9:02AM on page 135
Resolution
Thank you for this comment. We have reworked the paragraph.
Consistent notation and creative composition of clear reporting
×
Warning message
The installed version of the browser you are using is outdated and no longer supported by Konveio. Please upgrade your browser to the latest release.IBCS Standards 2.0 (clean draft)
Please add your comments until Jan 31, 2026
Use this document version if your prefer commenting on a clean draft.
Commenting is closed for this document.
in reply to Rafal Pierzchlewicz's comment
Severin Willig Mar 11 2026 at 9:00AM on page 21
Resolution
Thank you for this one. In priciple you are right, however this example serves for avoiding repeated words and for the sake of simplifing it, we have reduced the chart here.
in reply to Vidya Rani 1 1 1 1 1 1's comment
Severin Willig Mar 11 2026 at 8:59AM on page 16
Resolution
Thank you. We understand that "view-port" is a term from UX design, so your comment is valid and appropriate. However, this term is not as well known in the reporting context. Therefore, we would prefer to avoid using the term "view-port."
in reply to Vidya Rani 1 1's comment
Severin Willig Mar 11 2026 at 8:57AM on page 3
Resolution
Thank you for the note; this section will be completely revised due to many other comments.
in reply to Vidya Rani 1 1 1 1 1's comment
Severin Willig Mar 11 2026 at 8:57AM on page 3
Resolution
Thank you for the note; this section will be completely revised due to many other comments.
in reply to Vidya Rani 1 1 1 1's comment
Severin Willig Mar 11 2026 at 8:57AM on page 3
Resolution
Thank you for the note; this section will be completely revised due to many other comments.
in reply to Vidya Rani 1 1 1's comment
Severin Willig Mar 11 2026 at 8:57AM on page 3
Resolution
Thank you for the note; this section will be completely revised due to many other comments.
in reply to Vidya Rani 1's comment
Severin Willig Mar 11 2026 at 8:57AM on page 3
Resolution
Thank you for the note; this section will be completely revised due to many other comments.
in reply to Vidya Rani's comment
Severin Willig Mar 11 2026 at 8:56AM on page 3
Resolution
Thank you for the note; this section will be completely revised due to many other comments.
in reply to Tobias Guggemos's comment
Severin Willig Mar 11 2026 at 8:44AM on page 107
Resolution
Thank you, you’re right. We don’t see any concrete need for changes, especially since the main points are already mentioned in the preceding paragraph.
in reply to Tobias Guggemos's comment
Severin Willig Mar 11 2026 at 8:43AM on page 67
Resolution
Thanks, but maybe too specific to mention it here.
in reply to Tobias Guggemos's comment
Severin Willig Mar 11 2026 at 8:42AM on page 56
Resolution
Thank you, these are interesting approaches, and we may discuss them in later versions.
in reply to Tobias Guggemos's comment
Severin Willig Mar 11 2026 at 8:41AM on page 49
Resolution
Thank you very much. We appreciate your reasoning in principle; however, we don’t see a concrete suggestion for an alternative approach. With this in mind, we will need to postpone the discussion to a later version.
in reply to Rafal Pierzchlewicz's comment
Severin Willig Mar 11 2026 at 8:39AM on page 92
Resolution
Thank you, this is a good note. However that is already implemented in EX 1.2.
in reply to Marnix's comment
Severin Willig Mar 11 2026 at 8:36AM on page 46
Resolution
Thank you and you are right. We have noted it and will discuss it for potential future versions.
in reply to Markus's comment
Severin Willig Mar 11 2026 at 8:36AM on page 6
Resolution
Thanks for the suggestion. We will implement a different wording.
in reply to Mario 2's comment
Severin Willig Mar 11 2026 at 8:35AM on page 46
Resolution
Thank you for the question. There is no clear recommendation from IBCS, but using an additional color (such as yellow or orange) seems to us the most obvious choice.
in reply to Marcus Bitterlich's comment
Severin Willig Mar 11 2026 at 8:34AM on page 25
Resolution
Thanks, however we are quite limited as ISO already provides the framework we are meking use of here.
in reply to Marcus Bitterlich's comment
Severin Willig Mar 11 2026 at 8:33AM on page 19
Resolution
Thanks. In SI 1, the focus is more on the overall layout concept of the report, whereas SI 3 deals with the clean layout and design of individual visuals.
in reply to Marcus Bitterlich's comment
Severin Willig Mar 11 2026 at 8:32AM on page 17
Resolution
Thanks for your suggestion. We will implement it.
in reply to Marcus Bitterlich's comment
Severin Willig Mar 11 2026 at 8:30AM on page 6
Resolution
Thank you and within e.g. SAP Analytics Cloud language that is correct. However, we would like to stay with it as we are using regions and products fore more examples as well.
in reply to Marcus Bitterlich's comment
Severin Willig Mar 11 2026 at 8:29AM on page 3
Resolution
Thank you. Report pages are explained in the definitions and we also explain the "screen" or "slide" in this section.
in reply to Mala Deep Upadhaya 1 1 1 1 1 1 1 1 1 1 1 1 1 1's comment
Severin Willig Mar 11 2026 at 8:28AM on page 154
Resolution
Thank you! Each individual rule has subpoints listed in the table of contents that can serve as a checklist. Additionally, the poster serves as a visual checklist, which can be obtained through IBCS.
in reply to Mala Deep Upadhaya 1 1 1 1 1 1 1 1 1 1 1 1 1's comment
Severin Willig Mar 11 2026 at 8:27AM on page 32
Resolution
Thanks. We do think that we are a bit more specific in our example and therefore would like to stay with it.
in reply to Mala Deep Upadhaya 1 1 1 1 1 1 1 1 1 1 1 1's comment
Severin Willig Mar 11 2026 at 8:26AM on page 32
Resolution
That’s generally a good point, as we typically use bullet points not for rules but only for lists. However, in this case, we don’t have any lists.
in reply to Mala Deep Upadhaya 1 1 1 1 1 1 1 1 1 1 1's comment
Severin Willig Mar 11 2026 at 8:25AM on page 27
Resolution
Thank you for your input. However, we would still prefer to decline the suggestion. Once the image is described in more detail, it creates redundancies. Additionally, these images are used in the IBCS poster, where we only have space for a single line.
in reply to Mala Deep Upadhaya 1 1 1 1 1 1 1 1 1's comment
Severin Willig Mar 11 2026 at 8:24AM on page 25
Resolution
Thanks. Unfortunately, it is not true that ISO suggests capital letters for non-monetary values as the example of "k" shows.
in reply to Mala Deep Upadhaya 1 1 1 1 1 1 1 1's comment
Severin Willig Mar 11 2026 at 8:24AM on page 25
Resolution
Thank you for this one. We have reworked the paragraph.
in reply to Mala Deep Upadhaya 1 1 1 1 1 1's comment
Severin Willig Mar 11 2026 at 8:22AM on page 20
Resolution
Thank you. In principle this is a good idea. However, we think that a specific example will help.
in reply to Mala Deep Upadhaya 1 1 1 1's comment
Severin Willig Mar 11 2026 at 8:20AM on page 17
Resolution
Thank you for your input. However, we would still prefer to decline the suggestion. Once the image is described in more detail, it creates redundancies. Additionally, these images are used in the IBCS poster, where we only have space for a single line.
in reply to Mala Deep Upadhaya 1 1 1's comment
Severin Willig Mar 11 2026 at 8:20AM on page 16
Resolution
Thank you for your input. However, we would still prefer to decline the suggestion. Once the image is described in more detail, it creates redundancies. Additionally, these images are used in the IBCS poster, where we only have space for a single line.
in reply to Mala Deep Upadhaya 1 1's comment
Severin Willig Mar 11 2026 at 8:18AM on page 16
Resolution
Thank you. We rarely use the dashes, that is why we would like to stay with the current format.
in reply to Mala Deep Upadhaya 1's comment
Severin Willig Mar 11 2026 at 8:17AM on page 5
Resolution
Thank you for this one. However we can only talk about the example after we have explained that it belongs to the business topic..
in reply to Mala Deep Upadhaya's comment
Severin Willig Mar 11 2026 at 8:14AM on page 5
Resolution
Thanks for your suggestion. We will implement it.
in reply to Lars's comment
Severin Willig Mar 11 2026 at 8:12AM on page 3
Resolution
Thanks for your suggestion. We will implement it.
in reply to Juan-Pierre's comment
Severin Willig Mar 11 2026 at 8:12AM on page 64
Resolution
Thanks. Indeed there is light blue recommended. We have added it to the text.
in reply to Juan-Pierre's comment
Severin Willig Mar 11 2026 at 8:10AM on page 49
Resolution
Thank you. We have no preference regarding which RGB codes are used for the colors, as this is not necessary for pattern recognition.
in reply to Juan-Pierre's comment
Severin Willig Mar 11 2026 at 8:09AM on page 43
Resolution
That’s generally a good point. We don’t provide strict guidelines for this kind of internal company representation. This should be included in the glossary.
in reply to Juan-Pierre's comment
Severin Willig Mar 11 2026 at 8:09AM on page 42
Resolution
Thank you. PL is included in our glossary. These definitions are likely to vary between organizations (but not within one organization; there should only exist one definition) anyway.
in reply to Juan-Pierre's comment
Severin Willig Mar 11 2026 at 8:07AM on page 32
Resolution
Thank you. We believe this is fairly self-explanatory, and that everyone can easily imagine how it looks on the other side.
in reply to Juan-Pierre's comment
Severin Willig Mar 11 2026 at 8:06AM on page 32
Resolution
Thank you! It’s neither alphabetical nor by size; rather, the most important items should be placed at the bottom. This is also mentioned in EX 1.1.
in reply to Juan-Pierre's comment
Severin Willig Mar 11 2026 at 8:06AM on page 31
Resolution
Thanks and there seems to be a misunderstanding. The separator is not meant to be printed in the title but serves as a separator solely on this page.
in reply to Juan-Pierre's comment
Severin Willig Mar 11 2026 at 8:04AM on page 23
Resolution
Thanks for the suggestion. We do see it differently indeed. For one organization, there should be exactly one glossary and the definitions (e.g. "KPI" as an abbreviation) should not very through the same organization.
in reply to Juan-Pierre's comment
Severin Willig Mar 11 2026 at 8:03AM on page 20
Resolution
Thank you and you are right. It would only be redundant in case of "sum". Otherwise we would not consider it as a case for "avoid superflous words".
in reply to Juan-Pierre's comment
Severin Willig Mar 11 2026 at 8:01AM on page 22
Resolution
Thanks you, you are abolutely right. This is being defined under UN 1.1.
in reply to Juan-Pierre's comment
Severin Willig Mar 11 2026 at 8:00AM on page 20
Resolution
Thanks and you are abolutely right. This is being defined under UN 1.1.
in reply to Juan-Pierre's comment
Severin Willig Mar 11 2026 at 8:00AM on page 19
Resolution
Thank you, you’re basically right, and this is already mentioned under EX 1.2 Column Types. This section specifically deals with vertical lines.
in reply to Juan-Pierre's comment
Severin Willig Mar 11 2026 at 7:57AM on page 18
Resolution
Thank you for the comment. We have added it - there is no strict recommendation for a specific font; sans-serif fonts are preferred. This can be found in chapter SI 2.3 Avoid decorative fonts.
in reply to Juan-Pierre's comment
Severin Willig Mar 11 2026 at 7:52AM on page 16
Resolution
Thank you. Due to the many comments, we have decided to include a general note on accessibility in the introduction.
in reply to Juan-Pierre's comment
Severin Willig Mar 11 2026 at 7:51AM on page 16
Resolution
Thanks for this one. Basically, you’re right. However, there have been no interpretation issues so far in this and the past versions, so we would assume that it is self-explanatory.
View all
Comments
View all Cancel