I have great new ideas!
I just realized that my new "hobby project" (which is about softeware supply chain traceability) got to a point where the hermes stuff would fit in just great.
... okay, at least the core data model.
What I can see you are very good ahead of refactoring and testing the base data model.
I think the state you achieved is really great (even if it is exactly the opposite of what it was meant to).
Looking at the latest discussions, you are very close to the point where you can skip the jsonld-dependency.
Next step is the "merging engine" (or whatever I called it back then).
For my project, I'm processing software delivery chains (e.g., in-toto, SLSA, ...) and therefore I need a JSON(-LD) engine.
And here is where hermes comes in.
I'm certain that I will base my development on the hermes code in one way or another...
Integrating into hermes as a plugin make the whole thing not flexible enough.
Just using hermes as a library might be feasable for now as I'm not processing data much right now.
But I think time will come that I need to advance...
Looking at the current state, I could image "slicing out" the JSON-LD part would be sensible.
However, I really appreciate the strict development process that I'm too lazy to obey from time to time... ;)
Hence, I could also live with a "friendly fork" (contributing well-packaged features back after they have been under rogue development over at led-inc.net).
Just wanted to share my ideas with you right now, would be happy to hear from you! :)
I have great new ideas!
I just realized that my new "hobby project" (which is about softeware supply chain traceability) got to a point where the hermes stuff would fit in just great.
... okay, at least the core data model.
What I can see you are very good ahead of refactoring and testing the base data model.
I think the state you achieved is really great (even if it is exactly the opposite of what it was meant to).
Looking at the latest discussions, you are very close to the point where you can skip the jsonld-dependency.
Next step is the "merging engine" (or whatever I called it back then).
For my project, I'm processing software delivery chains (e.g., in-toto, SLSA, ...) and therefore I need a JSON(-LD) engine.
And here is where hermes comes in.
I'm certain that I will base my development on the hermes code in one way or another...
Integrating into hermes as a plugin make the whole thing not flexible enough.
Just using hermes as a library might be feasable for now as I'm not processing data much right now.
But I think time will come that I need to advance...
Looking at the current state, I could image "slicing out" the JSON-LD part would be sensible.
However, I really appreciate the strict development process that I'm too lazy to obey from time to time... ;)
Hence, I could also live with a "friendly fork" (contributing well-packaged features back after they have been under rogue development over at led-inc.net).
Just wanted to share my ideas with you right now, would be happy to hear from you! :)