sebbader-sap

@BirgitBoss with the splitting of the ValueOnly chapter to https://github.com/admin-shell-io/aas-specs/blob/IDTA-01001-3-1_working/documentation/IDTA-01001/modules/ROOT/pages/includes/IDTA-01001_ValueOnly.adoc, we should 1. move this issue to https://github.com/admin-shell-io/aas-specs and put it into the scope for V3.1 2. prepare a fix...

It definitely makes sense to locate them in the python file. The `ModelReference` constraint is not JSON-specific AND will be valid also for future versions. My main question is, can...

1. RDF 1.1 references XML Schema Part 2 - Datatypes Version 1.1, indeed. 2. However, this has no effect on the AAS RDF serialisation, and is completely unrelated to the...

The problem is that we can "serialise" AASd-130 into different regex patterns due to the fact that regex itself is underspecified. I tried to explain our decision for the UTF-16...

> use submodels to model both the security and data specifications. Using the submodel concept for managing AAS-content ('regulating' as in IT security & 'explaining' as in semantic meaning &...

Regarding the original topic: As long as we do not have a convincing pattern for JSON, I see this approach as blocked. Even though I agree that a more flexible...

@s-heppner what is the state here? Please ping me when I can re-review this PR again.

@s-heppner the current state looks good for me, just two last questions: 1. See my comment above about the cardinality declaration. I am just not sure whether `{,2}` is a...

@BirgitBoss I can confirm Sebastian's statement on the "contentType" regex. I just finished a bunch of tests and now agree that the pattern is working accordingly. (Even though the spaces...

@mkollenstart I need help to push the files into the releases folder. We have an Action for it, don't we?