On 10/29/07, Mathias wrote: > > Signing isn't something you can use without understanding what you are > > doing. You must create a signature first. So there is no way to hide > > this functionality behind something and IMHO it would be wrong also. > > On 10/29/07, Alan wrote:
> I think people use features, like 'read only,' all the time without > understanding them. ... read only gets used because most users see 'read > only' and understand it to mean restricting rights to the document. > > Regarding creating a signature, I am not aware of having created or been > issued one on my home PC, and was able to sign a document in Writer. > On 10/29/07, Mathias wrote: > > > I still understand why "Tools-Options-Security" is not enough: it > > creates a document that is opened read-only and so is protected against > > inadvertent changes. Can somebody explain me what is wrong with that > > What I think is wrong is that the average user will expect read-only to be more difficult to circumvent (Why? Because of experience with Word which has dominant market share and as a result sets expectations). So what's needed is a way to make it apparent, without reading instructions or resorting to support lists, that signing makes it impossible to make changes and still represent the document as the original document. Signing does achieve the desired effect but I don't think the average user understands that. What I suggest is interface changes to make the effect of signing more obvious. e.gIn the digital signature message area, rather than being empty when the document is unsigned, a bold red exclamation mark when the document is unsigned and when the mouse is over it a message to the effect "The document is not signed. To detect changes the document must be signed." This might even be improved by adding a Sign button below the 'Open this document in read-only mode' check box. The same design used with the Protect button below the 'Record changes' check box. And when the mouse is over the digital signature message area on a signed document the message could be modified to include "Saving any changes to this document will remove all signatures." The other component I think is needed is already there. A warning when a signed document is about to be saved indicating that saving the document will remove the signature. What I'm trying to imagine is a way to build the interface so the average user, who won't RTFM and who probably won't find their way to a support list, would understand easily from using the application that signing prevents undetected changes to the document. I hope this makes sense. I also wonder, if the discussion continues, if it belongs here or on a different list? -Alan
