-
Notifications
You must be signed in to change notification settings - Fork 25
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
ogma-core
: Generalize JSON parsing
#115
Comments
Change Manager: Confirmed that the issue exists. |
Technical Lead: Confirmed that the issue should be addressed. |
Technical Lead: Issue scheduled for fixing in Ogma 1.2. Fix assigned to: @ivanperez-keera. |
. Ogma currently has no standard representation for specifications, and instead relies on a representation that is tied to the input format from which the spec was read. This commit introduces a new library to represent generic Ogma specifications. The specifications are parameterized by the type of the requirement expressions. This will allow us to use the same internal representation to hold data obtained from different kinds of input files (e.g., JSON, XML).
. The JSON parsing functions currently included with Ogma are very specific to two formats supported, and cannot be easily generalized. This limits our ability to adapt to changes and to different formats. This commit introduces a new library to parse Ogma specifications from JSON files. The parsing functions are parameterized by the functions that parse requirement sub-expressions, allowing for further customization.
To avoid name clashes, it is sometimes necessary to replace identifiers in SMV boolean expressions. This commit adds identifier substitution functions to the SMV language library.
The JSON parsing functions currently used by ogma-core are very specific to two formats supported, and cannot be easily generalized. This commit replaces the existing FRET component specficiation parser and converter by one that is based on the new generic parsing library.
The library ogma-language-fret-cs is no longer needed, since its functions have been generalized in other libraries. Therefore, this library can be completely removed.
Implementor: Solution implemented, review requested. |
Change Manager: Verified that:
|
Change Manager: Implementation ready to be merged. |
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.
Description
The JSON parsing functions currently included with Ogma are very specific to two formats supported, and cannot be easily generalized. This limits our ability to adapt to changes and to different formats.
Type
Additional context
None.
Requester
Method to check presence of bug
Not a bug.
Expected result
The parsing functions support any JSON file and can be easily customized to support specific JSON-based formats.
Desired result
The parsing functions support any JSON file and can be easily customized to support specific JSON-based formats.
Proposed solution
Use selectors, similar to XPath, to customize how fields are selected in JSON files.
Further notes
None.
The text was updated successfully, but these errors were encountered: