[namedgraphs] Base64 encoding

[Jennifer C. <jen...@at...>]

Hi everyone,

The Base64 encoding is working slightly different since the change away
from the sun libraries.  (Note: I have no issues with the change, and
thank Tim for making it!  We needed to move away from those libs.)

If you run the SWPExample (in src/de.fuberlin.wiwiss.ng4j.examples) and
compare the functionality from the prior release, it can be seen that the
sun libraries didn't chunk the data when encoding.  (i.e. no carriage
return is added after 76 characters.)

The new code (e.g. in SWPSignatureUtilities.calculateDigest) is using
Base64.encodeBase64Chunked so it does insert the carriage return.

>From what I've read, it's actually standard to include the carriage
return.

HOWEVER I'm not sure we want to do that for the digest in NG4J.  The
digest is then added to the warrantGraph as a literal (as the object in an
RDF statement about the digest).  Perhaps that's legal, but it does look
odd when the RDF is written in whatever format.

I'm assuming that change was made unintentionally and we could go back to
the chunk-less style?  i.e. change to use Base64.encodeBase64 in all
places?

Jennifer

Jennifer P. Cormier
Sr. Computer Scientist
ATC-NY
www.atc-nycorp.com