Documentation Issue: Ambiguos explanation of what is considered model name

[JulijaRamoskiene]

There are 2 pages describing what is considered model name:

• https://www.itwinjs.org/bis/guide/fundamentals/model-fundamentals/ says that "a Model does not store a name of its own. Instead, its name comes from the CodeValue of its modeled element."
• https://www.itwinjs.org/bis/guide/data-organization/top-of-the-world/ says that "since the "Name" (e.g. Code and UserLabel properties) of an InformationPartitionElement is typically not meaningful in the context of a business, it is typically the Code of its parent Subject what is considered to be the "Name" of the Partition's submodel."
  Which one is correct and which property is considered model's 'Name'? Is it 'CodeValue' of modeled element, or is it CodeValue of parent Subject of modeled element?
  Found on page https://www.itwinjs.org/bis/guide/data-organization/top-of-the-world - "Top of the World"

[ben-polinsky]

@ColinKerr could best answer this, I believe.

[diegoalexdiaz]

We've discussed that "exception" a few of times at the BWG, leading to the clarification of the exception of the general rule for Partitions in the docs. Partitions were introduced for machines to understand, not for humans, thus their Codes are rather meaningless.

Short-term, we could mention the exception of the rule in the "model-fundamentals" article.

I wonder if we could solve this situation in cleaner ways ... e.g., by introducing additional pieces in the schema. E.g. an ISubModeledElement being able to optional state whether its own Label & Code apply to its Submodel, or if not, where to find them.