Rename Entity label and alternativeLabels to name and aliases, respectively

[larrybabb]

This particular issue is in regards to "renaming" attributes on subclasses. While it think it is fine to further "specialize" an attribute name so that it is clearer to those trying to apply a given class or profile. I found that one particular case is a bit challenging.

This was instigated by one of our open discussions for the TU ballot around the idea of changing alternativeLabels to aliases. It is conflated with the idea of whether or not MappableConcept should inherit from Entity or Element which I will not bring in here for now.

I contest that label and alternativeLabels on Entity should be renamed to name and aliases. I'm not an ontologist or really even very good with the english language but I did read up on a few threads and found this one pushed me over the top.

Kori is using pydantic to help us implement the models in python and as such it gets into some interesting things around "renaming" subclassed attributes. It's all fine, but the Agent class renames label to name which seems upside down since label is more specific that name and less of an identifying-like attribute (based on my readings). I think it would be best if we consider just using name in place of label and aliases in place of alternativeLabels if possible.

[mbrush]

I think I am ok with this (using name and aliases instead of label and alternativeLabels) in the Entity class.

Consider also if/how to update other classes with name / label / title attributes that don't inherit from Entity, or that extend Entity.label:

• MappableConcept.label -> change to name?
• Coding.label -> change to name?
• Extension.name -> keep as is?
• Agent.name (currently extends Entity.label) -> no longer need to define this as an extension if we use Entity.name
• Document.title -> should this extend Entity.name?

[mbrush]

Outcomes from 1-29-25 Discussion:

• We will rename Entity label and alternativeLabels to name and aliases, respectively
• MappableConcept.label will change to name
• Coding.label will change to name
• Extension.name will stay as is
• Agent.name, which currently extends Entity.label, will no longer need to do so (as it will now simple inherit name fromEntity)
• Document.title will be deprecated, and will simply use the name attribute it inherits from Entity. We will add a description to Document.name that explains this attribute should capture the formal title of the document when one exists, otherwise it can capture whatever name the source provides for it. If implementers feel it is useful to add a separate title attribute, we can do so in future versions.

[larrybabb]

gks-core commit #a4b4f81 chnage made to Entity to change label and alternativeLabelstonameandaliases`, respectively.
This will be propogated up to VA in the forthcoming release.