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

[BUG] use xsd 1.0 data types #312

Closed
BirgitBoss opened this issue Dec 15, 2023 · 2 comments
Closed

[BUG] use xsd 1.0 data types #312

BirgitBoss opened this issue Dec 15, 2023 · 2 comments
Labels
accepted accepted in principle to be fixed bug Something isn't working documentation Improvements or additions to documentation
Milestone
V3.0.1

Comments

@BirgitBoss
Copy link
Collaborator

BirgitBoss commented Dec 15, 2023 •
edited
Loading

Describe the bug
In DataTypeDefXsd links to xmlschema11-2, i.e. xsd V1.1 are contained. However, the decision is to use xsd 1.0. See also Figure 54

The xsd schema is using 1.0

Where
substitute xmlschema11-2 with xmlschema2 links
@BirgitBoss BirgitBoss added bug Something isn't working documentation Improvements or additions to documentation accepted accepted in principle to be fixed labels Dec 15, 2023
@BirgitBoss BirgitBoss added this to the V3.1 milestone Dec 15, 2023
BirgitBoss added a commit that referenced this issue Dec 15, 2023
@BirgitBoss
* (Editorial) MultiLanguageNameType inconsistent description, maxLeng…
0640d66 
…th=128 (schemata were correct) ([#313](#313))

* (Editorial) HasKind/kind explanataroy text: use template, not type ([#313](#313))
* (Editorial) DataTypeDefXsd links now correctly to xmlschema11-2, not to xsd V1.1 ([#312](#312))
+ minor editorial changes
@BirgitBoss BirgitBoss mentioned this issue Dec 15, 2023
Closed
@BirgitBoss BirgitBoss linked a pull request Dec 15, 2023 that will close this issue
Resolve issues, focus specification/schemata #315
Closed
@BirgitBoss BirgitBoss mentioned this issue Dec 21, 2023
Merged
BirgitBoss added a commit that referenced this issue Jan 29, 2024
@BirgitBoss
Resolve Issues V3.1 (#317)
e484be0 
* * (Editorial) MultiLanguageNameType inconsistent description, maxLength=128 (schemata were correct) ([#313](#313))
* (Editorial) HasKind/kind explanataroy text: use template, not type ([#313](#313))
* (Editorial) DataTypeDefXsd links now correctly to xmlschema11-2, not to xsd V1.1 ([#312](#312))
+ minor editorial changes

* New value "Role" in Enumeration AssetKind (#294)

* add new value "AssetKind" enumeration "Role"  #294
Change PathType to allow not only file:  #299

* Identifier: change length from 2000 to 2024 characters #299

* allow hyphens in idShort of Referables #295

* make Entity/entityType optional #287

* editorial change, add missing link to issue #295

* Update Constraint AASd-014 (part 2 of #287)

* EmbeddedDataSpecification/dataSpecification now mandatory #296

* Update Change Appendix w.r.t. EmbeddedDataSpecifcation/dataSpecification (now mandatory) #296

* #296 update Changes Section

* Editorial changes
#313

* semanticId of specificAssetId with name "globalAssetId"
#298

* Correct AASd-002

see #295 
for backward compatibility reasons idShort can end with an underscore. Additionally also 1 char idShorts are allowed.

* path .Specification.pdf

remove \

* fix typo
@BirgitBoss BirgitBoss modified the milestones: V3.1, V3.0.1 Feb 29, 2024
@BirgitBoss
Copy link
Collaborator Author

Finding in Workstream 204-04-11: w3.org/TR/RDF uses XML Schema 1.1.

@BirgitBoss BirgitBoss mentioned this issue Apr 11, 2024
Closed
@BirgitBoss BirgitBoss reopened this Apr 11, 2024
@BirgitBoss
Copy link
Collaborator Author

solved in IDTA-01001-3-0-1: https://industrialdigitaltwin.org/wp-content/uploads/2024/06/IDTA-01001-3-0-1_SpecificationAssetAdministrationShell_Part1_Metamodel.pdf

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
accepted accepted in principle to be fixed bug Something isn't working documentation Improvements or additions to documentation
Projects
None yet
Milestone
V3.0.1
Development

Successfully merging a pull request may close this issue.

Resolve issues, focus specification/schemata admin-shell-io/aas-specs
1 participant
@BirgitBoss