-
Notifications
You must be signed in to change notification settings - Fork 29
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.
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
grammar for IDs for metamodel elements: value or values?
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
Enhancing Property Requiredness: Introducing a "Recommended" Option
#525
opened Feb 13, 2025 by
Philipp-Liedl
CanonicalAAS: Define Ordering Rules and Canonical Representation for AAS
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
#521
opened Jan 17, 2025 by
mhrimaz
Remove AASd-006
documentation
Improvements or additions to documentation
requires workstream approval
strategic decision proposal needs to be prepared in TF spec team
#515
opened Dec 15, 2024 by
BirgitBoss
use idShort instead of index in idShortPath for elements of SML
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
[BUG] Regex for xs:dateTime does not properly support timezones
accepted
accepted as proposed
documentation
Improvements or additions to documentation
requires workstream approval
strategic decision proposal needs to be prepared in TF spec team
Preserve AAS-/SM-Id of original AAS/SM after cross enterprise AAS-/SM-transfer with modification of Ids
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
#497
opened Dec 10, 2024 by
HeinrichChristian
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
[BUG] Reference to the not existing accepted as proposed
Complete_Example.ttl
accepted
#489
opened Nov 28, 2024 by
zrgt
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
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
[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
Modelling of operation parameters
bug
Something isn't working
question
Further information is requested
#462
opened Aug 12, 2024 by
mjacoby
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
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
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
Remove abstract Class HasKind and incorporate directly in class Submodel
accepted
accepted as proposed
Not-backward-compatible
not backward comptible, would require a major release
specification
impact on specification and thus on xml, json etc., label "aas-core" not set additinally
ECLASS RDF Representation
RDF
impact on 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
Improve SHACL schema
bug
Something isn't working
RDF
impact on RDF
#421
opened Apr 23, 2024 by
VladimirAlexiev
8 tasks
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
rename repository to aas-specs-metamodel
accepted
accepted as proposed
process
not content related but related to process
Omitted Attributes for BasicEventElement, Entity, CD in Metadata
specification
impact on specification and thus on xml, json etc., label "aas-core" not set additinally
#522
opened Mar 12, 2024 by
sebbader-sap
RDF-native interpretation/profile
RDF
impact on RDF
#384
opened Mar 11, 2024 by
VladimirAlexiev
4 of 17 tasks
Previous Next
ProTip!
Mix and match filters to narrow down what you’re looking for.