Re: [xsl] How do you ensure that data is not altered/corrupted in atransformation?

["Roger L Costello costello@xxxxxxxxx" <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx>]

Hi Alan,

> hashing can be used to verify that the data
> in instance A is identical to instance B

That is exactly what is needed. It must be ensured that the data -- 12000 feet
-- is not altered/corrupted during the transformation. From an XSLT
perspective, what is the best way to ensure that data is not
altered/corrupted?

/Roger

From: Alan Painter alan.painter@xxxxxxxxx
<xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx>
Sent: Friday, May 19, 2023 4:56 AM
To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
Subject: [EXT] Re: [xsl] How do you ensure that data is not altered/corrupted
in atransformation?

An XML schema validation would do the trick in this case.B  If your schema
requires "alt" rather than "altitude", schema validation would catch this.

I don't see "hashing" as a solution in this case .. hashing can be used to
verify that the data in instance A is identical to instance B .. but if you
are doing a transformation, then you are probably "changing" something hence
the before/after instances would not be identical.

On Fri, May 19, 2023 at 10:36b/AM Roger L Costello mailto:costello@xxxxxxxxx
<mailto:xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> wrote:
Hi Folks,

In certain domains loss of life may occur if data is altered/corrupted in any
way.

Suppose you write an XSLT program which transforms this:

<alt>12000 feet</alt>

to this:

<altitude>12000 feet</altitude>

How do you ensure that the data -- 12000 feet -- was not altered/corrupted in
the transformation?

I have heard of people doing a hash on the data prior to the transformation, a
hash on the data after the transformation, and then comparing the hashes. Is
that what you would do when lives are on the line? What is your
recommendation?

/Roger

http://www.mulberrytech.com/xsl/xsl-list
http://lists.mulberrytech.com/unsub/xsl-list/673357 ()