Skip to content

model.base: Fix MultiLanguageNameType value length to 128#577

Merged
s-heppner merged 2 commits into
eclipse-basyx:developfrom
thammel:fix/check-short-name-type
Jul 13, 2026
Merged

model.base: Fix MultiLanguageNameType value length to 128#577
s-heppner merged 2 commits into
eclipse-basyx:developfrom
thammel:fix/check-short-name-type

Conversation

@thammel

@thammel thammel commented Jun 16, 2026

Copy link
Copy Markdown

Until now, each value of a MultiLanguageNameType was constrained to a maximum length of 64 via check_short_name_type. This never matched the specification: LangStringNameType/text has had a maximum length of 128 characters since AAS Part 1 Metamodel V3.0, identical to NameType.

MultiLanguageNameType now uses check_name_type instead. The now-unused check_short_name_type and constrain_short_name_type functions are removed accordingly.

Fixes #576

Until now, each value of a MultiLanguageNameType was constrained to a
maximum length of 64 via check_short_name_type. This never matched the
specification: LangStringNameType/text has had a maximum length of 128
characters since AAS Part 1 Metamodel V3.0, identical to NameType.

MultiLanguageNameType now uses check_name_type instead. The now-unused
check_short_name_type and constrain_short_name_type functions are
removed accordingly.
Comment thread sdk/basyx/aas/model/_string_constraints.py Outdated
@s-heppner s-heppner added this to the Release 2.1.0 milestone Jul 6, 2026

@s-heppner s-heppner left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thank you!

@s-heppner s-heppner merged commit 06a9b62 into eclipse-basyx:develop Jul 13, 2026
15 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants