YAML based version of NBility for easier automated processing - #14
Open
patrickb-alliander wants to merge 2 commits into
Open
YAML based version of NBility for easier automated processing#14patrickb-alliander wants to merge 2 commits into
patrickb-alliander wants to merge 2 commits into
Conversation
Signed-off-by: patrickb-alliander <[email protected]>
Signed-off-by: patrickb-alliander <[email protected]>
Author
|
@LexDeWolff , @Jonasvdbo , please review. |
This file contains hidden or 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
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.
As we do more and more with 'as-code', having the NBility model in a computer interpretable structure makes it much easier to use, link, process NBility information and structure within other environments.
Also for use with agents, a YAML representation makes it easier for agents (LLM's) to understand NBility.
This YAML is generated from the Excel file using Python and validated against a fixed (JSON) schema. Also available if needed.