[
Lists Home |
Date Index |
Thread Index
]
- From: "Ashvil" <ashvil@i3connect.net>
- To: <abisheks@india.hp.com>, <xml-dev@xml.org>
- Date: Sun, 2 Jul 2000 09:33:22 -0700
Abhishek Srivastava wrote
>
> If the output of a XSL Translation is an XML document..
> then another style
> sheet can be written that will transform the output
> document back to the
> source document.
>
I think this is the preferred solution that this group is leaning
towards. And it would resolve my current problem. However, I see an
issue with making two stylesheets, every time I want the users to edit
the XML data. More work, sigh !
I was thinking of an extended XSLT processor that would automatically
add more information to the resultant tree (eg. Back pointers to the
original tree), so that it could apply the reverse transformation.
Something like this.
Extended Extended
XSLT XSLT
XML tree ---> XHTML tree ----> (Users edit ---> XML tree
(with data only (with
information no tree updated
for reverse manipulation data)
transformation) is allowed)
I am still interested in what information would the extended XSLT need
to store for the reverse transformation to occur. I think this would
be important for a read-write web especially when languages like SVG
become popular.
Regards,
Ashvil
***************************************************************************
This is xml-dev, the mailing list for XML developers.
To unsubscribe, mailto:majordomo@xml.org&BODY=unsubscribe%20xml-dev
List archives are available at http://xml.org/archives/xml-dev/
***************************************************************************
|