-
Notifications
You must be signed in to change notification settings - Fork 27
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
Add support for XML-based input files. Refs #202. #203
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…a#202. There is a need in Ogma to support XML-based input files, since this is produced by many standard tools in the industry. Like with JSON, we want users to be able to customize the input format via a command-line flag, so that users can work with XML-based files whose format is previously unknown to Ogma without having to modify the tool. This commit introduces a new library to parse Ogma specifications from XML files. The parsing functions are parameterized by the functions that parse requirement sub-expressions, allowing for further customization, The sub-expression parser may execute an IO-action, enabling the use of external commands and/or LLMs to pre-process expressions. The specification of the XML format is readable, which will also enable parsing a format specification from an input file (either a known file distributed with Ogma or a user-provided input file).
…#202. There is a need in Ogma to support XML-based input files, since this is produced by many standard tools in the industry. Like with JSON, we want users to be able to customize the input format via a command-line flag, so that users can work with XML-based files whose format is previously unknown to Ogma without having to modify the tool. A prior commit has introduced a library to parse Ogma specifications from XML files. This commit extends ogma-core to accept input files in XML, and to treat any configuration file containing an XMLFormat specification as format specification for an XML-based input file.
There is a need in Ogma to support XML-based input files, since this is produced by many standard tools in the industry. Like with JSON, we want users to be able to customize the input format via a command-line flag, so that users can work with XML-based files whose format is previously unknown to Ogma without having to modify the tool. A prior commit has introduced the capability to use XML files with ogma-core. This commit adds four XML format specifications based on two standard formats used in known MBSE tools.
ivanperez-keera
force-pushed
the
develop-xml
branch
from
January 19, 2025 18:31
147ed1b
to
c0af537
Compare
Implementor: Fix implemented, review requested. |
Change Manager: Verified that:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit introduces a new library to parse XML files, and modifies
ogma-core
to use that functionality to support processing input files in XML in the standalone backend, as prescribed in the solution proposed for #202.