Closed matthiaskoenig closed 3 years ago
Actually, if the name isn't defined, it's reasonable to use the 'id' instead. I'm fine being more explicit, but I would use 'should' instead of 'must' and mention the ID as an option.
Yes, definitely we should add the fallback to the id. And add "If neither name or id are set it is up to the tool what to used as label."
Added the following text:
The name of the AbstractCurve should be used to label the curve in the given Plot2D, or, if name is not defined, the id may be used. If neither are present, the name or id of the referenced yDataReference may be used in the case of a Curve or the yDataReferenceFrom and/or yDataReferenceTo in the case of a ShadedArea. Because of the complications this can engender, it is highly recommended to define the name of all AbstractCurve elements.
and later:
The name of the Surface should be used to label the surface in the given Plot3D, or, if name is not defined, the id may be used. If neither are present, the name or id of the referenced zDataReference may be used. In general, it is highly recommended to define the name of all Surface elements.
Oh, I should say: I did not add any additional text to the bit about the legend, as that seemed redundant, but would be OK if someone wants to add it in anyway.
The description of the legend currently reads:
This should be less ambiguous as
In addition the description in legend should be updated from
to