Comments (3)
I'm not sure what the best solution would be in this case...on the one hand we are talking about milestone releases which I guess would in theory allow adding breaking changes. However, I agree that this will most likely cause problems and disappointment from the users that they no longer can load files create by the previous version.
Therefore, I see two potential approaches (if technically possible)
- Keep backwards compatibility by supporting both
http://www.admin-shell.io/aasx/relationships
andhttp://admin-shell.io/aasx/relationships
. We should add a warning message when loading a file using the "old" URL that the file is not compliant to the standard and will no longer be supported with the next release. Also we should always save files using the correct URL. - Remove support for "old" URL. In this case we should a a big fat note in the release notes stating the problem. We should also provide some simple command line tool to fix existing AASX files and should link that tool in the release notes.
I am fine with any of these two approaches.
from aas4j.
I think approach 1) would be feasible with little effort. I can take a look at implementing this next week.
from aas4j.
I would also keep backwards compatibility for now. The idea of warning users is a good idea. And I would always automatically convert to the format as described in the spec.
from aas4j.
Related Issues (20)
- Throw out Validator for V1
- Update AasUtils - sameAs(...) and resolve(...)
- Serialized AASX File not readable by the AASX-Package-Explorer HOT 15
- Bug in XML Serializer HOT 1
- Bug while generating extentions in submodel
- Update utility functions to V.3.0
- XmlDeserializer can't read AASX file HOT 4
- Throw sensible exception in case of deserialization error or output warning HOT 3
- ProtocolInformation misses SecurityAttributes HOT 1
- IDTA deserialization issue HOT 1
- AASX - Ids in Relationship files are not valid HOT 2
- xsiSchemaLocation in generated XML documents not processable by AASXPackageExplorer HOT 8
- Explore if removing the XSI Schema Location from XML fixes AASX Package Explorer Issue HOT 1
- Prefix artifact names with "aas4j-" HOT 1
- Ensure that adding support for further DataSpecificationContent is possible in future without breaking changes
- Make APIs type safe according to AAS meta model spec HOT 5
- EmbeddedDataSpecifications inside XML SubmodelElements are not deserialised
- Trigger Final Release via Eclipse Foundations HOT 1
- Get Parent of Referable HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from aas4j.