-
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
More restrictive schemas for Reference
aas-core
impact on aas-core but not on specification
#310
opened Dec 12, 2023 by
mhrimaz
Update Approval Process in Contribution Guide - Labeling Proposal+
process
not content related but related to process
Contribution Guide - add chapter about legal information and authors
process
not content related but related to process
Update Contribution Guide -add chapter about release process
process
not content related but related to process
substitutionGroup for Data Specifications
on hold
requirement accepted, solution open
specification
impact on specification and thus on xml, json etc., label "aas-core" not set additinally
Update the links in the JSON, XML and RDF Readmes to reference the correct version of the specification
documentation
Improvements or additions to documentation
Automate synchronization process
process
not content related but related to process
#267
opened Apr 21, 2023 by
s-heppner
XSD data types instead of xs:string for value type
RDF
impact on RDF
#284
opened Jun 29, 2023 by
mhrimaz
Is there a consistent approach to mapping a classification of assets in the AAS?
on hold
requirement accepted, solution open
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
#292
opened Oct 16, 2023 by
foprs
AdministrativeInformation: templateId only for Submodels
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
JSON Schema for ValueOnly-Serialization. Exception also for SubmodelElementList?
documentation
Improvements or additions to documentation
invalid
This doesn't seem right
requires workstream approval
strategic decision proposal needs to be prepared in TF spec team
ValueOnly-Serialization: add information how to deal with optional elements
documentation
Improvements or additions to documentation
#370
opened Nov 16, 2023 by
BirgitBoss
1 task done
Properties in RDF are prefixed by class names
postponed for next version(s)
RDF
impact on RDF
#43
opened Jul 21, 2021 by
kenwenzel
Update Contribution Guideline w.r.t. approval
process
not content related but related to process
#302
opened Nov 16, 2023 by
BirgitBoss
[BUG] missing rdf prefix in SHACL's SPARQL queries
bug
Something isn't working
RDF
impact on RDF
#330
opened Jan 6, 2024 by
mhrimaz
Support IRDI-Path from ECLASS
acknowledged
in work
requires workstream approval
strategic decision proposal needs to be prepared in TF spec team
#334
opened Jan 22, 2024 by
BirgitBoss
Allow to also reference Qualiers, specificAssetIds etc.
requires workstream approval
strategic decision proposal needs to be prepared in TF spec team
ValueOnly Example Illustrating Precision Problems
documentation
Improvements or additions to documentation
[BUG] relative URL without base in RDF examples
bug
Something isn't working
RDF
impact on RDF
#379
opened Mar 8, 2024 by
VladimirAlexiev
enable the use of custom datatypes (for RDF)
RDF
impact on RDF
#380
opened Mar 8, 2024 by
VladimirAlexiev
enable the use of lang tags for langString
RDF
impact on RDF
#382
opened Mar 11, 2024 by
VladimirAlexiev
allow using Linked Data principles in the RDF rendition
RDF
impact on RDF
#383
opened Mar 11, 2024 by
VladimirAlexiev
RDF-native interpretation/profile
RDF
impact on RDF
#384
opened Mar 11, 2024 by
VladimirAlexiev
4 of 17 tasks
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
Previous Next
ProTip!
Type g i on any issue or pull request to go back to the issue listing page.