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

66 Open 98 Closed
66 Open 98 Closed
Author
Filter by author
Label
Filter by label
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Milestones
Filter by milestone
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

ECLASS RDF Representation
#422 opened Apr 26, 2024 by VladimirAlexiev
5
Improve SHACL schema bug Something isn't working
#421 opened Apr 23, 2024 by VladimirAlexiev
8 tasks
Introduce ContainerElement as SubmodelElement interface ready for approval TF proposes how to resolve the issue. Needs final approval my Workstream requires workstream approval strategic decision in spec team needed
#420 opened Apr 22, 2024 by alexgordtop V3.1
1
Handling of optional sets if elements in serializations ready for approval TF proposes how to resolve the issue. Needs final approval my Workstream requires workstream approval strategic decision in spec team needed specification impact on specification and thus on xml, json etc., label "aas-core" not set additinally
#418 opened Apr 20, 2024 by BirgitBoss V3.1
4
Optional values for all SubmodelElements 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
#412 opened Apr 16, 2024 by alexgordtop V3.1
@BirgitBoss
2
Cardinality > 1, distinguish between Map / Array documentation Improvements or additions to documentation requires workstream approval strategic decision in spec team needed
#411 opened Apr 16, 2024 by alexgordtop V3.1
Do not change Value-Only type for Range: stay with number requires workstream approval strategic decision in spec team needed specification impact on specification and thus on xml, json etc., label "aas-core" not set additinally
#407 opened Apr 12, 2024 by BirgitBoss V3.1
2
Revisit Events <<Experimental>> requires workstream approval strategic decision in spec team needed 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
Produce a holistic JSON example documentation Improvements or additions to documentation
#405 opened Apr 12, 2024 by mristin V3.x
4
What is the Value-Only of a List of Operations or Capabilities requires workstream approval strategic decision in spec team needed specification impact on specification and thus on xml, json etc., label "aas-core" not set additinally
#402 opened Apr 11, 2024 by BirgitBoss V3.1
Improve documentation of Value-Only documentation Improvements or additions to documentation
#401 opened Apr 11, 2024 by BirgitBoss V3.1
3
add constraint: for Submodel with kind=Instance Property/value and MultiLanguageProperty shall be defined. requires workstream approval strategic decision in spec team needed specification impact on specification and thus on xml, json etc., label "aas-core" not set additinally
#398 opened Apr 10, 2024 by BirgitBoss
1
Update infos for OPC UA and AML documentation Improvements or additions to documentation
#397 opened Apr 10, 2024 by BirgitBoss V3.1
1
Handle valueId and isCaseOf like semanticId requires workstream approval strategic decision in spec team needed specification impact on specification and thus on xml, json etc., label "aas-core" not set additinally
#396 opened Apr 10, 2024 by BirgitBoss V3.1
XSD datatype version mismatch bug Something isn't working specification impact on specification and thus on xml, json etc., label "aas-core" not set additinally
#395 opened Apr 10, 2024 by g1zzm0 V3.0.1
@BirgitBoss
2
rename repository to aas-specs-metamodel ready for approval TF proposes how to resolve the issue. Needs final approval my Workstream requires workstream approval strategic decision in spec team needed
#394 opened Apr 10, 2024 by BirgitBoss V3.1
Proposal for MultiLanguageFile Support requires workstream approval strategic decision in spec team needed specification impact on specification and thus on xml, json etc., label "aas-core" not set additinally
#392 opened Apr 5, 2024 by alaettindogan
Clarify Handling of globalAssetId and specificAssetId (Constraint AASd-116) accepted accepted in principle to be fixed documentation Improvements or additions to documentation ready for approval TF proposes how to resolve the issue. Needs final approval my Workstream
#390 opened Mar 26, 2024 by BirgitBoss V3.0.1
@BirgitBoss
4
[BUG] Reference/type is underspecified documentation Improvements or additions to documentation requires workstream approval strategic decision in spec team needed
#389 opened Mar 24, 2024 by arnoweiss V3.1
2
Definition of Cardinality seems to be wrong (01001-3-0, p. 134) bug Something isn't working documentation Improvements or additions to documentation
#388 opened Mar 19, 2024 by foprs V3.1
1
JSON-LD context (and frame)
#386 opened Mar 14, 2024 by VladimirAlexiev
23
[BUG] The spelling of ID-Short-Path should be uniform bug Something isn't working documentation Improvements or additions to documentation RDF impact to RDF
#385 opened Mar 12, 2024 by g1zzm0
RDF-native interpretation/profile RDF impact to RDF
#384 opened Mar 11, 2024 by VladimirAlexiev
2 of 17 tasks
9
allow using Linked Data principles in the RDF rendition
#383 opened Mar 11, 2024 by VladimirAlexiev
1
enable the use of lang tags for langString RDF impact to RDF
#382 opened Mar 11, 2024 by VladimirAlexiev
3
ProTip! Add no:assignee to see everything that’s not assigned.