Re: Data misuse (was Re: template matching..)

[Guy_Murphy@xxxxxxxxxx]

Hi Marcus.

You're right in that there is a relationship between the data provider and
the data reciever. I would however say that in business terms a large part
of this relationship is still best solved person to person in that we
provide *very* large data feeds to companies, and any changes to those
feeds would be part of a negotiated business solution.

Likewise I as a developer of Web applications now recieve data from the
back-end in XML format. This solution was negotiated between myself and the
back-end developers. Likewise any change would be negotiated.

In dealing with change, or migrating from one data model to another as an
interim solution we have XSL that can be utilised as a translational
filter, until applications migrate.

In terms of dealing with unpredictable changes to recieved data, there are
two strategies off the top of my head...

If you provide a DCD with your data, then I can look for changes in the
data model and bring in a contingency plan for rendering that data.

The other iedea, is again if you provide a DCD with data types described,
is to use an XSL stylesheet to transform the DCD into and XSL stylsheet for
transforming the data. In this way you can pretty much change your data
(within reasonable bounds) in any way you wish and it wont effect me at
all.

In providing a solution dealing with ever changing data models the latter
dynamic construction of stylesheets is probably the way to go.

All this doesn't change the fact that in the end it is my resopsibility as
the recipient of your data to deal with that data. Obviously if you can
facilitate that the relationship will be a happier one, but I certianly
don't like the experience of the data provider dictating the stylesheet.

Cheers
     Guy Murphy
     Web Developer
     The Dialog Corporation plc.
     guy_murphy@xxxxxxxxxx





xsl-list@xxxxxxxxxxxxxxxx on 03/26/99 05:44:55 PM

To:   xsl-list@xxxxxxxxxxxxxxxx
cc:    (bcc: Guy Murphy/UK/MAID)
Subject:  Data misuse (was Re: template matching..)





Guy_Murphy@xxxxxxxxxx wrote:
> Well, one we get to philosophical matters, we can only express subjective
> opinions....
I wouldn't ask for anything less. :-)
> I take well your point about the provider of the data knowing best and in
> the kindest possible way would say "blah!"
I believe that will be the predominant opinion, and for the most part it
should
be. XML is about sending properly defined data somewhere else to be used in
any
variety of ways. If you are to "blah" me now, then how are you going to
react
when I change my structure in a way that harms your downstream use of the
data?
Is it buyer beware? I'm not saying that you shouldn't use the data, I'm
just
curious about how the relationship between the vendor and the repurposer
might
be managed. If you (the repurposer) told me (the vendor) how you wanted the
data, then I could change my structure as long as I managed the impact on
what
you expected. Isn't this proof that as much as possible (or at least on one
layer) this is best handled by the vendor?
> As a final point, a core paradigm of XML is the divorcement of data
mark-up
> from data presentation. To the person marking up the data who insists on
> stipilating presentational use I say "mind your own business" :)
I'd go further and tell them "you're wasting your time". That doesn't
bridge
the gap between consumer and vendor though.

--
Regards,
Marcus Carr                      email:  mrc@xxxxxxxxxxxxxx
___________________________________________________________________
Allette Systems (Australia)      www:    http://www.allette.com.au
___________________________________________________________________
"Everything should be made as simple as possible, but not simpler."
       - Einstein


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list






 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list