Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: Ignorant meta-document (from schema?) question

From: Martin Honnen <mahotrash@-----.-->
To: NULL
Date: 11/1/2004 6:26:00 PM

Mike wrote:
> I am writing a post-processor for an existing XML document (that I have
> no control over), this entails a lot of inserting and deleting of
> nodes.
> 
> I don't want to have to hard code the (schema-defined) 'parent' XPath
> of every node (so that I know what to clone and where to insert). It
> seems that there should be someway of dynamically determining (via the
> schema?) the 'parent' paths such that I am able to create valid
> documents.
> 
> Does anything like this exist or is it just wishful thinking?
> 
> (I use 'parent' here not to mean the physical parent of a node, rather
> the logical parent from the schema's point of view (as in if I clone
> this node then I really have to clone this entire path and insert it
> here)).

I think MSXML 4 when validating XML instance files against XML schemas 
tries to display the XPath to the relevant element e.g.
   /root/el1[3]/el2[4]/el3[5]
and it is certainly possible to construct such paths using XSLT. I can't 
point you to an existing XSLT stylesheet or other XML software tools 
that solves that.

-- 

	Martin Honnen
	http://JavaScript.FAQTs.com/


transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent