Comments archive

The pages of this comments archive list all public comments on the latest version of the IBCS® Standards in chronological order.


Jürgen Faisst

Applying fixed category widths to an entire report with multiple pages seems not to be applicable in practice – at least not in dynamic dashboards. This is why I suggest to restrict the rule to one page or screen: “… this allocation should be the same at least for an entire page of a report or a screen of a dashboard.”

View comment inline
Avatar

In my oppinion the excerpt is a improvement compared to the current paragraph and support this change

View comment inline
Jürgen Faisst

I think the last sentence of this article is outdated:

“In charts with stacked columns, stacked areas, and charts with multiple lines or areas, the application of this semantic scenario notation can become a challenge. In these cases, applying the semantic notation to the axis instead of the columns etc. is a valid option.” 

It should be replaced by the rule, that the scenario notation is applied to the lowest segment while all other segments are filled with the same shade of gray as the rest of the data series with an additional frame (outlined) or hatch pattern if applicable.

Or is there anyone out there still using semantic axes for non-variance charts?

View comment inline
Jürgen Faisst

The paragraph “Highlighting ellipses” will be changed following the suggestions from Work Group 3. This change will also cover warning dots although they are not mentioned explicitly:
“For example, the IBCS suggests the use of the highlighting ellipse to bring attention to key data points. The company could decide that highlighting with a marker is a better fit for that company, as long as this is set out in the company’s notation manual and is applied consistently.”  – Excerpt from the proceedings of Work Group 3.

View comment inline
Avatar

Wili ”warning dots” still part of IBCS, but defined in the paragraph “Highlighting elipses” or is it planed to drop them entirely?

 

View comment inline
Jürgen Faisst

When following my suggestion to delete the paragraph on “Variance highlighting indicators” covering warning dots, we have to also delete this paragraph on warning dots because they overlap with the “Highlighting ellipses”.

View comment inline
Jürgen Faisst

This article about “Variance highlighting indicators” is more confusing than it helps. Traffic lights should be replaced by variance bars (EX 2.5) and warning dots overlap with the “Highlighting ellipses”. Let’s keep things simple and just delete this entire paragraph.

View comment inline
Rolf Hichert

Hi Jens –

thank you for your comment. I have discussed this issue beforehand with Jürgen and we both have the following thinking towards the color blue:

We see red, green and blue as highlighting colors. Red and green for bad and good variances, blue for the “rest”. As neutral variances belong to the “rest” we do not see a need for a different blue.

So we do not think that it is necessary to have different blues – but: every user who thinks that this is necessary: Let him use two different blues… 🙂

Rolf

View comment inline
Avatar

If i understand you correctly it is planed to have ‘standard’ colours for variances.

red (negative),  blue (neutral), green (positive) and green-blue(colour vision deficiency)?

I presume that the blue used in variances should have a different shade as the blue used for the comment markers?

the change is fair enough for me.

 

 

 

View comment inline
eliasteufel

Hello,

I see it the same way as Beat. Furthermore, it should be mentioned that ’17 is the IBCS recommended short form of 2017 (as mentioned in UN 3.3). Took me a bit to understand the reason for the format-change: from the 4-digit year format in UN 1.2 to the 2-digit year format incl. the apostrophe in UN 4.2.

The 2-digit version may also cause the following:

two digit years between ’01 and ’32 also being mistaken for days, and ’01-’12 mistaken for months in varying date formats”  (https://en.wikipedia.org/wiki/Year_2000_problem).

View comment inline