Hi Arne, hi Simon,
It got removed because there wasn't evidence of use. 5.x.x was a chance
It is opinionated and it doesn't feel like a good fit being in the
central code for graph. It's more like a utility library feature.
It can come back, maybe in a better form or better location.
So to both of you - what are your use cases? What are the
TripleBoundary/StatementBoundary in use?
Andy
On 09/04/2024 19:56, Arne Bernhardt wrote:
Hi Simon,
my colleagues had the same problem with GraphExtract.
The code has been removed in the context of Jena5 Model API changes
<https://github.com/apache/jena/issues/2021> in the commit
https://github.com/afs/jena/commit/6697a516724745532616bb0db3ce67a8778e2b6c.
So anyone may fetch the latest code from there.
Unfortunately, I am not sure why exactly it has been removed. Since it does
not implement any standard and is not documented under
https://jena.apache.org/documentation/, I doubt it will find its way back
into Jena.
Greetings
Arne
Am Di., 9. Apr. 2024 um 19:54 Uhr schrieb Dutkowski, Simon <
[email protected]>:
Hi All
I realized that in version 5.0.0, the classes ModelExtract and co are
removed. Are there any replacements or other ways to achieve the same (or
similar) results?
I can easily fetch the classes from earlier versions and integrate them
into my project directly, but I am not sure if it is necessary, and if
possible I would prefer to avoid it.
Thanks in advance
Simon
--
Dipl.-Inf. Simon Dutkowski
Fraunhofer FOKUS (DPS)
Kaiserin-Augusta-Allee 31, 10589 Berlin
+49 160 90112644
