RE: Style Matters - A class act

["Vun Kannon, David" <dvunkannon@xxxxxxxx>]

	My first response is that if Didier found it important enough to
write about, I found it important enough to respond to. ;-p
	I think there has been quite a frothy debate on this list, at times,
about the importance of being able to tie back to the source from a
presentation.
	The particular use of this functionality that I described was a
desktop application in which the GUI presentation was tied to an XML
archival (File/Save) format. A number of applications are almost in this
position today and the next generation certainly will be. UML modeling tools
such as Rational Rose (only an example) could save to XMI as their native
file format.
	In such an instance, you are correct that the user only sees the
GUI, but the application itself has to keep track of both node trees (assume
the GUI was SVG for argument's sake), map back changes from the GUI to the
source, and then style forward to keep the two in sync with each other.
	Many other kinds of desktop productivity apps are amenable to the
same argument, word processors, spreadsheets, CAD tools, network management
consoles, etc. XML vocabularies will creep in on little cat feet, from
File/Save As to File/Save, when developers realize there is little point and
much cost in supporting two file formats, an interoperable transfer syntax
built on XML standards, and a crufty old proprietary format that is held
together by baling wire and chewing gum.

-----Original Message-----
From: Pawson, David [mailto:DPawson@xxxxxxxxxxx]
Sent: Friday, February 04, 2000 2:17 AM
To: 'xsl-list@xxxxxxxxxxxxxxxx'
Subject: RE: Style Matters - A class act


 Vun Kannon, David presents a solid mechanism
to 'link back' from target to source.

Simple question: Why?

In todays usage, certainly from this list,
it would appear that users aren't presenting
two documents to the reader, source and target,
simply the intended readable version.

Regards, DaveP


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
*****************************************************************************
The information in this email is confidential and may be legally privileged.
It is intended solely for the addressee. Access to this email by anyone else
is unauthorized. 

If you are not the intended recipient, any disclosure, copying, distribution
or any action taken or omitted to be taken in reliance on it, is prohibited
and may be unlawful. When addressed to our clients any opinions or advice
contained in this email are subject to the terms and conditions expressed in
the governing KPMG client engagement letter.         
*****************************************************************************


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