-
Notifications
You must be signed in to change notification settings - Fork 1
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
Investigate parallel validation of SCL files #18
Comments
The idea we have with CoMPAS is to integrate RiseClipse as a Java Library in a existing Microservice and start the validation of IEC 61850 SCL XML from a Java Class (Single running JVM). Multiple validation can be running at the same time and maybe even with different configurations if that's necessary/possible. Also it would be nice that files can be configured using a Inputstream or Resource. Currently I only see the possibility to pass a file name that RiseClipse will load from the local filesystem. |
RiseClipse uses two inputs to validate SCL files: OCL and NSD files. |
NSD files can be loaded with starting the microservice (they do not change that often). Question: If we could adress the "big issues" com-pas/compas-scl-validator#2, we could use riseclipse for the validation of the LF energy CoMPAS project. I prefer to re-use and collaborate as much as possible to me the most beneficial to the industry. |
@jeanetiennelemaire What is your idea in terms of loading OCL rules? I suggest to discuss this on the CoMPAS refinement the comming monday 10:00. https://lists.lfenergy.org/g/CoMPAS/viewevent?repeatid=40465&eventid=1337091&calstart=2022-03-07 |
We discussed this topic today during the community call, we all agreed that is would be nice if we can give the data service the OCL rules and the SCL file. |
Can we just a send a pull request with these changes or do you guys want to discuss them first? |
The model must be known at build time by RiseClipse, so it is not possible to check with OCL private elements.
No time for the moment to work on this issue, but any PR is welcome. |
Use cases:
The text was updated successfully, but these errors were encountered: