Hi,
that is a good point! We assumed digests as "quasi natural" Hex-encoded,
as you can see in the example.
But we also saw the same problem for digital signatures, as one can see
in the semantic unit "signatureInformationEncoding". And had a different
solution.
I would like to support the idea of adding an optional semantic unit
"messageDigestEncoding". Not only for levelling an inconsistency but
also to support newer computing environments in the network.
Olaf
Matt Cordial schrieb:
> Is there any best practice or requirement concerning the preferred
> encoding of MD5 digests in the fixity element? I notice that the vast
> majority of the examples are hex encoded (which ends up being 32
> characters). We are developing a web service and because the HTTP spec
> specifies that MD5's be Base64 encoded we were wondering if we could
> use Base64 encoded digests instead of hex encoded? If there is not an
> encoding requirement, should there be a way to specify how these
> digests are encoded?
>
> Thanks,
>
> ~Matt
>
--
---------------------------------------------------------
Goettingen State and University Library
Olaf Brandt
Project kopal
Tel.: +49-551-39-7805
Email: [log in to unmask]
http://www.sub.uni-goettingen.de/
http://kopal.langzeitarchivierung.de/
|