Skip to content

Issues: admin-shell-io/aas-specs

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

59 Open 137 Closed
59 Open 137 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

[BUG] Regex for xs:dateTime does not properly support timezones bug Something isn't working JSON impatc on JSON only Schemas generated schemata for xml, JSON and rdf or XMI
#498 opened Dec 11, 2024 by mjacoby
@s-heppner
2
Preserve AAS-/SM-Id of original AAS/SM after cross enterprise AAS-/SM-transfer with modification of Ids postponed for next version(s)
#497 opened Dec 10, 2024 by HeinrichChristian
2
remove Annex "Requirements", update with IEC 63278 documentation Improvements or additions to documentation requires workstream approval strategic decision proposal needs to be prepared in TF spec team
#495 opened Dec 8, 2024 by BirgitBoss V3.x
add mapping rules to specification accepted accepted in principle to be fixed documentation Improvements or additions to documentation
#493 opened Dec 4, 2024 by BirgitBoss
@BirgitBoss
[BUG] Reference to the not existing Complete_Example.ttl accepted accepted in principle to be fixed
#489 opened Nov 28, 2024 by zrgt
@s-heppner
2
Clarify Handling of IRDI pathes postponed for next version(s)
#487 opened Nov 27, 2024 by BirgitBoss
AdministrativeInformation: add createdAt and updatedAt attributes ready for approval TF proposes how to resolve the issue. Needs final approval my Workstream specification impact on specification and thus on xml, json etc., label "aas-core" not set additinally
#484 opened Nov 15, 2024 by BirgitBoss V3.x
2
AssetKind: add Batch besides Type and Instance? ready for approval TF proposes how to resolve the issue. Needs final approval my Workstream specification impact on specification and thus on xml, json etc., label "aas-core" not set additinally
#483 opened Nov 15, 2024 by BirgitBoss V3.x
6
[BUG] Example for Reference wrong bug Something isn't working documentation Improvements or additions to documentation
#481 opened Oct 31, 2024 by BirgitBoss V3.1
1
Add Example of Reference String serialization that includes a References with referredSemanticId accepted accepted in principle to be fixed documentation Improvements or additions to documentation
#480 opened Oct 30, 2024 by J-Blume V3.1
1
1
Add Matching Strategy how to deal with supplementalSemanticID accepted accepted in principle to be fixed documentation Improvements or additions to documentation
#479 opened Oct 30, 2024 by J-Blume V3.1
1
2
Update Matching Strategy SemanticId accepted accepted in principle to be fixed documentation Improvements or additions to documentation
#473 opened Oct 9, 2024 by BirgitBoss V3.1
1
2
Matching Strategies semantic IDs etc. accepted accepted in principle to be fixed documentation Improvements or additions to documentation
#471 opened Oct 7, 2024 by BirgitBoss
2
[BUG] Do not use keywords in the meta-model bug Something isn't working specification impact on specification and thus on xml, json etc., label "aas-core" not set additinally
#468 opened Sep 12, 2024 by mristin V4.x
1
Modelling of operation parameters bug Something isn't working question Further information is requested
#462 opened Aug 12, 2024 by mjacoby
8
Revisit <<experimental>> attribute "kind" of Qualifier requires workstream approval strategic decision proposal needs to be prepared in TF spec team specification impact on specification and thus on xml, json etc., label "aas-core" not set additinally
#451 opened Jul 19, 2024 by BirgitBoss V3.x
Revisit <<experimental>> SubmodelElement Range requires workstream approval strategic decision proposal needs to be prepared in TF spec team specification impact on specification and thus on xml, json etc., label "aas-core" not set additinally
#450 opened Jul 19, 2024 by BirgitBoss V3.x
ValueOnly: Support dateTime Range and not only string postponed for next version(s) requires workstream approval strategic decision proposal needs to be prepared in TF spec team specification impact on specification and thus on xml, json etc., label "aas-core" not set additinally
#444 opened Jun 30, 2024 by BirgitBoss V3.x
1
Remove abstract Class HasKind and incorporate directly in class Submodel accepted accepted in principle to be fixed specification impact on specification and thus on xml, json etc., label "aas-core" not set additinally
#434 opened May 27, 2024 by BirgitBoss V4.x
2
Relax Constraint AASD-120 for SMT allow idShort in SML accepted accepted in principle to be fixed specification impact on specification and thus on xml, json etc., label "aas-core" not set additinally
#432 opened May 22, 2024 by BirgitBoss V3.1
1
9
ECLASS RDF Representation RDF impact to RDF requires workstream approval strategic decision proposal needs to be prepared in TF spec team specification impact on specification and thus on xml, json etc., label "aas-core" not set additinally
#422 opened Apr 26, 2024 by VladimirAlexiev
6
Improve SHACL schema bug Something isn't working RDF impact to RDF
#421 opened Apr 23, 2024 by VladimirAlexiev
8 tasks
Introduce ContainerElement as SubmodelElement interface accepted accepted in principle to be fixed ready for approval TF proposes how to resolve the issue. Needs final approval my Workstream requires workstream approval strategic decision proposal needs to be prepared in TF spec team specification impact on specification and thus on xml, json etc., label "aas-core" not set additinally
#420 opened Apr 22, 2024 by alexgordtop V3.1
4
Revisit Events <<Experimental>> requires workstream approval strategic decision proposal needs to be prepared in TF spec team specification impact on specification and thus on xml, json etc., label "aas-core" not set additinally
#406 opened Apr 12, 2024 by BirgitBoss V3.x
1
Produce a holistic JSON example documentation Improvements or additions to documentation
#405 opened Apr 12, 2024 by mristin V3.x
5
ProTip! Adding no:label will show everything without a label.