Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Allow reading non-compliant AAS

Open
#211 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 4 days

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
backend

Research direction

Start by reviewing the constraint checks at attribute setting described in #210 and trace how non-compliant AAS data is read and serialized. Define the warning behavior and the boundary between readable and rejected data; done means invalid AAS can be read as far as possible, users receive clear warnings, and a corrected version can be serialized.

Written by the indexing model from the issue text.

Description

feature high priority sdk

Currently, it is not possible to read AAS that are non-compliant due to the fact that we check constraints at setting of an attribute (see #210 ).
We could make it possible to read these AASs as far as possible, in order to allow users to fix them and serialize the fixed version.
However, we should make it very clear with warnings what's happening.

Depends on #210

Dominant language
Python
Stars
104
Forks
56
Avg merge
12d 13h
Merged PRs (30d)
5

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from eclipse-basyx/basyx-python-sdk

All issues in eclipse-basyx/basyx-python-sdk

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.