Skip to content

adapter: Allow optional contentType in Blob and File#572

Merged
s-heppner merged 2 commits into
eclipse-basyx:developfrom
rwth-iat:fix-optional-contenttype
Jun 29, 2026
Merged

adapter: Allow optional contentType in Blob and File#572
s-heppner merged 2 commits into
eclipse-basyx:developfrom
rwth-iat:fix-optional-contenttype

Conversation

@paul-gerber-svg

@paul-gerber-svg paul-gerber-svg commented Jun 15, 2026

Copy link
Copy Markdown

Currently, the JSON and XMOL deserializiers raise an error when parsing Blob or File submodels that do not include a contentType

The contentType attribute has a cardinality of 0..1 for both classes and should therefore be optional. The implementation now aligns with this specification and defaults to None if the field is absent in the data.

Fixes #561

Currently, the JSON and XMOL deserializiers raise an error when parsing Blob or File submodels that do not include a contentType

The contentType attribute has a cardinality of 0..1 for both classes and should therefore be optional.
The implementation now aligns with this specification and defaults to None if the field is absent in the data.
Comment thread sdk/basyx/aas/adapter/json/json_deserialization.py Outdated

@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 now, thank you!

@s-heppner s-heppner merged commit 8c538c0 into eclipse-basyx:develop Jun 29, 2026
13 checks passed
@s-heppner s-heppner deleted the fix-optional-contenttype branch June 29, 2026 08:13
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