[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: Re: What Does SOAP/WS Do that A REST System Can't?

• To: 'Dare Obasanjo' <dareo@m...>, xml-dev@l...
• Subject: RE: Re: What Does SOAP/WS Do that A REST System Can't?
• From: "Bullard, Claude L (Len)" <len.bullard@i...>
• Date: Mon, 4 Apr 2005 08:41:42 -0500

In some cases there is a requirement to keep a full 
fidelity copy.  This is common in public safety reporting 
and other litigious domains.
 
PDFs are archived for that reason.  Otherwise, it is 
the usual combination of timestamps and audit records 
in the db.  XML wasn't a player.  SGML was rejected for 
the same reasons.  The term one sees is "final fixed format". 
Digital and scanned signatures (from sig pads) are used.

Before anyone else says it, yes any of these can be 
ditzed with digitally, so there are layers of security 
around the hardware as well and significant concern about 
the use of the Internet for legal transactions requiring 
proof of fidelity.   It's another 'good enough' situation 
until someone defeats it in a very public case.

len


From: Dare Obasanjo [mailto:dareo@m...]

Is there some legal requirement to keep a full fidelity copy of the
document? If not, I can't see why you don't just generate the XML as needed
from the database when export is needed. Most major database products have
had SQL<->XML mapping functionality for years. 
 

• Prev by Date: Re: Re: What Does SOAP/WS Do that A REST System Can't?
• Next by Date: Re: archiving with xml
• Previous by thread: Re: more reasons why xml accounting systems make sense.....
• Next by thread: RE: Re: What Does SOAP/WS Do that A REST System Can't?
• Index(es):
  • Date
  • Thread