[namedgraphs] Inconsistent RDF Signatures?

[landong z. <lan...@go...>]

Hi,

I am using SWPNamedGraphSet.assertWithSignature function to semantically
sign two N-triple files with the same semantic statements.

The N-triple files are from the different states of the publishing work
flow, i.e. before/after the file being loaded into the triple-store.

These two files might be slightly different in terms of order-of-triples and
naming-of-Bnode.  The equality of semantic is proven by Jena
Model.isIsomorphic() function as True.

Presumably, what I got from two files would be the same signature regardless
the meaningless change of the RDF serialisation. However, I am surprised to
receive two different signatures from NG4J output. Can anyone help me to
understand the cause of difference? or I've missed out any significant
concept? Thanks in advance.

The following is how the N-triple file is signed:

ArrayList<Node> propertiestoBePublished = new ArrayList<Node>();
            propertiestoBePublished.add(SWP.X509Certificate);

            result = set.assertWithSignature(auth,
                        SWP.JjcRdfC14N_rsa_sha1,
                        SWP.JjcRdfC14N_sha1,
                        propertiestoBePublished,
                        p12keystore,
                        password);
            set.write(output, "RDF/XML", "");



I can attach more details if it would help.

Regards,

Landong