How to manage a "set"?

[ThomasPO]

For me, the "set" of the whole code list (for example a "Total" in the case presented below) is not a real code within a code list representing a dimension.
Maybe, i'm wrong.

I had a look at the data sets available in your data catalog and totals are considered as codes (as we usually do in data files available on the Insee website).

Use case:

French population by sex and age groups on 1 january 2017

	Male	Female	Total
Less than 15 years	5 978 099	6 248 352	12 226 451
15 years and over	2 8675 386	2 6284 801	54960187
Total	34 653 485	32 533 153	67 186 638

Is Total a code within th "Gender" code list? And within the "Age groups" code list too?

For the hackathon, let's do simple in keeping the code "Total" within the code lists.

If you agree for replacing the data file and DSD file, i'm going to replace the empty value with a "Total" code and fix the issue #2 at the same time?

I gonna post this question about modelisation on a forum.

[derwas]

For the moment, as you suggested, we consider "Total" as another entry in the code list. This is something we want/will discuss during the hackathon.

In fact, having the total as a part of the code list, generates very bad visualizations and this is something we prefer to avoid with removing the total from the generated rdf data.