Adapt the schema files to v3.0.1

[s-heppner]

This adapts the schema files to version 3.0.1
of the specification.

However, this is not an official release yet
and may be subject to change.
This is only meant as reference for the
API specification.

[sebbader-sap]

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

[s-heppner]

@sebbader-sap You can use the now updated version for the API generation, however we still need to run the tests and generate the example files, before I will mark this PR as ready.

[sebbader-sap]

aas-specs/schemas/json/aas.json

Line 44 in b0e3e73

"pattern": "^([\\t\\n\\r -\ud7ff\ue000-\ufffd]|\\ud800[\\udc00-\\udfff]|[\\ud801-\\udbfe][\\udc00-\\udfff]|\\udbff[\\udc00-\\udfff])*$"

still has the old regex pattern.

[s-heppner]

aas-specs/schemas/json/aas.json

Line 44 in b0e3e73

"pattern": "^([\\t\\n\\r -\ud7ff\ue000-\ufffd]|\\ud800[\\udc00-\\udfff]|[\\ud801-\\udbfe][\\udc00-\\udfff]|\\udbff[\\udc00-\\udfff])*$"

still has the old regex pattern.

This should be resolved now. Can you please check again?

[sebbader-sap]

@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 valid shortcut for {0,2}. Can you confirm this?
2. You removed the spaces from the general String-checking regex pattern, this seems fine therefore. However, I still find patterns with spaces, e.g.

   aas-specs/schemas/json/aas.json

   Line 692 in 6ab2e16

   "pattern": "^([!#$%&'*+\\-.^_`|~0-9a-zA-Z])+/([!#$%&'*+\\-.^_`|~0-9a-zA-Z])+([ \\t]*;[ \\t]*([!#$%&'*+\\-.^_`|~0-9a-zA-Z])+=(([!#$%&'*+\\-.^_`|~0-9a-zA-Z])+|\"(([\\t !#-\\[\\]-~]|[\\x80-\\xff])|\\\\([\\t !-~]|[\\x80-\\xff]))*\"))*$"

   Is this a problem?

[s-heppner]

@sebbader-sap

ad 1.) The zero is optional in regexes, see this comment

ad 2.) From all I can tell, this regex is fine and generally the spaces shouldn't place problems.

Please wait with the release until I was able to run the schema generation one last time, since we found one last issue: aas-core-works/aas-core-codegen#494

[s-heppner]

I regenerated the JSON Schema and confirmed that there are no other effects of aas-core-works/aas-core-codegen#494.

Therefore, this is now ready for release, as far as I'm converned

[sebbader-sap]

@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 do have an effect, same as the tabs ('\t'), this effect is exactly as desired as far as I understand it.)
From my point of view, you merge this PR.