[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Notary services requirements -- directions?




Merriam-Webster is sometimes helpful: 

'notarization' =  
1. the act, process, or an instance of notarising.
2. the notarial certificate appended to a document.

'notarize' = to acknowledge or attest as notary public.

'notarial' = 
1. of relating to, or characteristic of a notary public
2. donce or executed by a notary public.         

'notary public' = a public officer who attests or certifies writings
(as a deed) to make them authentic, and takes affidavits, depositions,
and protests of negotiable paper.

It seems that indeed the words notarXXX are heavily connected to
one profession, and, as I conclude from this discussion, notaries
don't like someone else playing in their garden. :-) So be it. :-)

(As far as I understand from French dictionaries, the words
 notarisation or notariser seem not to exist in French. I
 haven't contacted the Acedemy Francaise. 

It was (maybe) a mistake (of mime?) to have the word in the name
of the working group. 

How can we (escape from)/remedy this situation?
We could add a remark "the term is a French word". 

But, well, before making a title, it seems to me that we may first come 
to an agreement  about *what* protocol we are doing, i.e., the ones 
between machines that 'certify' something, my view:

- act as a more or less automatic tool to perform some defined 
  validation activity 
- a to 'certify' the result, i.e. authenticating the data.
- used in workflows.  

Note that protocol is meant in a large sense, not just the 'access protocol', 
there are components for auditable operational requirements, i.e. a service
must play the game in the right way, and cannot just pretend to do something. 

Is it that what we are talking about? 
It seems that this is what Larry was proposing? 

Since more than 15 years or 20, we call some beasts 'certification authority',
and not 'e-certification authority', I am not sure whether the remark 'clumsy'
is related to the prefix 'e-' or to 'e-certification' as a buzzword.  

  "Protocol requirements for (data?) certification services"
 
seems another possibilities, also long and maybe 'clumsy', too. 

("Data" in order to avoid a confusion with public key certification)

I hope not having added too much confusion to the discussion. 
Peter