Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] first line in .xml considered to be invalid #43

Open
BirgitBoss opened this issue Jul 18, 2024 · 1 comment
Open

[BUG] first line in .xml considered to be invalid #43

BirgitBoss opened this issue Jul 18, 2024 · 1 comment
Labels
File Issues related to File (AASX, JSON, Xml) validation

Comments

@BirgitBoss
Copy link

There are two files in the attached .zip file: both are assumed to be valid and should lead to successful certification.

issues_603.zip

Incorrect Result:

>>> result.dump()
←[91mInvalid xml: not well-formed (invalid token): line 1, column 1←[0m

First line is
<environment xmlns="https://admin-shell.io/aas/3/0">
The file *_fixed.xml was fixed with aasx package explorer
The original file *_corrected.xml - from my point of view - is also a valid xml file but leads to many many error (see #41)

Same result with line
<environment xmlns:aas=https://admin-shell.io/aas/3/0 xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance xsi:schemaLocation=[https://admin-shell.io/aas/3/0 AAS.xsd](https://admin-shell.io/aas/3/0%20AAS.xsd)>
Or with

<?xml version='1.0' encoding='UTF-8'?>
<aas:environment xmlns:aas=https://admin-shell.io/aas/3/0 xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance xsi:schemaLocation=[https://admin-shell.io/aas/3/0 AAS.xsd](https://admin-shell.io/aas/3/0%20AAS.xsd)>
@otto-ifak
Copy link
Collaborator

I am sorry, I do not get the problem here. I am actually not able to reproduce it. Both

python -m aas_test_engines check_file ext/issues/43/issues_603/Aspect3.ttl.aas_corrected.xml --format xml
python -m aas_test_engines check_file ext/issues/43/issues_603/Aspect3.ttl.aas_corrected_fixed.xml --format xml

do not complain about invalid xml. However, they reject the file due many other problems. For example, Constraint_AASd-131 does not hold.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
File Issues related to File (AASX, JSON, Xml) validation
Projects
None yet
Development

No branches or pull requests

2 participants