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.

Sign up for GitHub

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

Jump to bottom

Adapt PathType regex #303

Open
s-heppner opened this issue Feb 2, 2024 · 0 comments · May be fixed by #316
Open

Adapt PathType regex #303

s-heppner opened this issue Feb 2, 2024 · 0 comments · May be fixed by #316
Labels
V3.1 SpecAAS V3.1
Milestone
V3.1

Comments

@s-heppner
Copy link
Collaborator

s-heppner commented Feb 2, 2024 •
edited
Loading

Previously, the PathType regex was too strict for AASX packages.
The new version of the spec softens the requirements to follow xs:anyURI.

See also: aas-specs#299

This depends on #317
@s-heppner s-heppner added the V3.1 SpecAAS V3.1 label Feb 2, 2024
@s-heppner s-heppner added this to the V3.1 milestone Feb 2, 2024
s-heppner added a commit that referenced this issue Feb 22, 2024
@s-heppner
V3.1: Change PathType to be of Type xs:anyURI
d7fae2d 
Previously, PathType was matched towards
RFC 8089, however this posed several problems,
such as [basyx-python-sdk#72](eclipse-basyx/basyx-python-sdk#72).

In [aas-specs#299](admin-shell-io/aas-specs#299),
the proposed solution is to make PathType of
type xs:anyURI.

Fixes #303
@s-heppner s-heppner linked a pull request Feb 22, 2024 that will close this issue
Draft
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
V3.1 SpecAAS V3.1
Projects
None yet
Milestone
V3.1
Development

Successfully merging a pull request may close this issue.

V3.1: Change PathType to be of Type xs:anyURI aas-core-works/aas-core-meta
1 participant
@s-heppner