BioPAX Paxtools and Validator update

[rod...@gmail.com]

PaxTools v5.2.1, v5.3.0 and Validator v5.1.0

• Released to Maven Central repository
• see https://biopax.github.io/Paxtools/, https://github.com/BioPAX/Paxtools
• see https://biopax.github.io/validator/, https://github.com/BioPAX/validator
• Executable (fat) JARs can be also downloaded from http://www.biopax.org/downloads/
  
  There were not many changes - just to build and use with modern JDKs (17-20...) and to update some of 3rd-party dependencies. Fixed a bug that caused RDF/XML long output like rdf:datatype = "http://www.w3.org/2001/XMLSchema#string" instead of rdf:datatype = "xsd:string" (unlike it was for xsd:int.)
  
  Pxtools 5.3.0 is same as 5.2.1 but without paxtools-trove (optional collections; one can still use separately if needed)

[rod...@gmail.com]

Well, turned out that "Fixed a bug that caused RDF/XML long output...", mentioned in the Paxtools v5.2.1,v5.3.0 release anouncement last year, actually intruduced an older regression bug: rdf:datatype = "xsd:string" attribute inside e.g. bp:name, bp:db, etc. biopax properties in RDFXML does not make sense or is just wrong (affects some SPARQL and RDF tool/converter use cases); so paxtools-core i/o (SimpleIOHandler) either should not add rdf:datatype when serializing a BioPAX Model to RDFXML (because biopax-level3.owl defines each property's range anyway, and RDF tools should be able to find out, infer that) or use absolute IRI there like before, e.g., rdf:datatype = "http://www.w3.org/2001/XMLSchema#string", or could use XML entity, e.g. rdf:datatype = "&xsd;string"; see #54)

This is going to be fixed in Paxtools v6.0.0 and may be v5.2.2 as well.