afs commented on issue #3593:
URL: https://github.com/apache/jena/issues/3593#issuecomment-3675849027

   _roughly_ ...
   Jena 5.6.0 was mid-October so Jena 6.0.0 is later than mid-January.
   
   I'd like there to a quiet time (no changes that motivate the major version 
number change) because impactful changes right up to the deadline have a habit 
of causing unexpected changes. A couples of weeks minimum.
   
   At the moment, I've done all the major changes I had listed as "must do" 
except adding the SPDX identifier. There maybe "clear-up" PRs if I stumble 
cross something that could do with some maintenance (see recent reformatting).
   
   I'm wondering whether have the extra directory level of `jena-extras` is 
worth it. It is 3 modules and all 3 are long-time modules so not really "extra".
   
   Another area is whether ARP (old RDF/XML parser) ought to move to `test`. 
   
   `jena-core` then only has N-Triples reader (which is out of date).  But 
updating ARP for RDF 1.2 is significant work (it is a SAX based parser) for 
little benefit. Using `jena-core` on its own is not a good idea so the idea of 
"N-Triples" has a logic to it. `jena-core` also has an the RDF/XML writers).
   
   As I write this comment, it feels like a good thing to move ARP. At worse, 
it can go back, but delaying is a delay of at least 2 years.
   
   If there is a need for better I/O in `jena-core`, putting in a Turtle parser 
and basic writer (which can serve for N-Triples) seems bette long term but 
unlikely to be ready for 6.0.0.
   
   RDF & SPARQL WG is very time consuming at the moment.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to