RE: Some possible rqmt/design points

The notary should produce and authenticate an affidavit document that refers
unambiguously to the document being notarized and explicit his assertion "I
Notary Public nnnn assert that the content of the document referred by xxx
was known in date of yyyy" or "I Notary Public nnn assert that the content
of the document referred by xx has been proven genuine in regard to records
rrrr presented to me by yyyy in date of zzzz" or ...

Signature endorsement carries no intrinsic meaning besides attesting of a
signature chronology. Attributes can give a meaning to an endorsement but
this could be done more efficiently by making use of specific assertions
(turned into XML document or element).

Sincerely,

Richard D. Brown


> -----Original Message-----
> From: w3c-ietf-xmldsig-request@w3.org
> [mailto:w3c-ietf-xmldsig-request@w3.org]On Behalf Of Phillip M
> Hallam-Baker
> Sent: Wednesday, June 16, 1999 2:24 PM
> To: rdbrown@GlobeSet.com; david.solo@citicorp.com
> Cc: 'IETF/W3C XML-DSig WG'
> Subject: RE: Some possible rqmt/design points
>
>
> > Phil,
> >
> > > OK Dave, I accept the point that the interpretation of the work is
> > > performed by the recipient. I don't however accept that this means
> > > that the sender should not have the means to fully express their
> > > original intentions.
> >
> > It should a matter of the XML body to explicit the
> intention. The body of
> > the document represents the assertion. The signature attests its
> > authenticity.
>
> What if the entity is a notary public?
>
> I certainly don't want to vet documents before stamping them.
> I may well not want to see the document itself to create the
> signature.
>
> But I do want to incorporate disclaimers.
>
>
> 		Phill
>

Received on Wednesday, 16 June 1999 16:00:53 UTC