Labels

• aas-core

  impact on aas-core but not on specification
• accepted

  accepted as proposed by the Workstream AAS Specifications
• accepted in principle

  problem noted but solution differs from original proposal
• acknowledged

  in work
• bug

  Something isn't working
• documentation

  Improvements or additions to documentation
• duplicate

  This issue or pull request already exists. Typically closed with reference to the other issue.
• enhancement

  New feature or request
• good first issue

  Good for newcomers
• help wanted

  Extra attention is needed
• invalid

  This doesn't seem right
• JSON

  impact on JSON schema only (not on specification)
• not accpeted
• Not-backward-compatible

  not backward comptible, would require a major release
• on hold

  requirement accepted, solution open
• postponed for next version(s)

  postponed, no decision which version it will be contained in
• process

  not content related but related to process
• question

  Further information is requested
• RDF

  impact on RDF (not on specification)
• 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
• Schemas

  generated schemata for xml, JSON and rdf or XMI
• Server API
• specification

  impact on specification and thus on xml, json etc., label "aas-core" not set additinally
• transfer

  issue refers to other part of specification or other and will be transfered
• V3.0RC02

  Issues related to the schemas for V3RC02
• V3.1.1
• V3.2
• wontfix

  This will not be worked on
• workstream Process of IDTA

  forwarded to Workstream "Process" of the IDTA (SMT Spec.)