Given this kind of problem, I've often developed an intermediate
schema, say Schema Z, that attempts to model the information in a way
compatible with both Schema's A and B.
You're then left with 2 validations: the first for transforming A to Z
and the second for transforming Z to B, this makes the transform rules
simpler, but means you have to manage 2 transforms.
This apprach also makes things simpler when the inevitable A2 and B2
come along. Hopefully the design of Schema Z ensures validity.
Phil Fearon
On Mon, Sep 9, 2013 at 8:42 AM, davep <davep(_at_)dpawson(_dot_)co(_dot_)uk>
wrote:
Given schema A as input XML. Schema B as XML output.
Assume no hierarchical simple relationship.
Assume mapping of values needed from input values to output values.
Assume literals are needed.
How do (might) you specify the required transform?
How do (might) you validate that instance A has been correctly transformed
to instance B, assuming input and output are both valid to the schemas.
Not something I've seen mentioned on this list?
regards
--
Dave Pawson
XSLT XSL-FO FAQ.
http://www.dpawson.co.uk
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail:
<mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--