I work with HL7 files which have elements in excess of 300 for each
document. It is tedious to say the least to draw the lines for these since
most of them just map across to their counterpart in the destination
document.

We are working on a tool to automatically map elements that have the same
name, cardinality  and datatype. The tool is being written in C#. Two
approaches are being considered.

The first is to extract the information from a source and destination
document and store the information in custom classes held in collections and
then processed them to create the page and link information.

The second approach is to use the XPathDocument, XPathNavigator, and
XPathNodeIterator classes to hold and  process the documents. We would
prefer to use the XPath approach but we have limited experience with XML
technologies and have run into problems when trying to apply this
expression, "*[//Schema]"  to the XML extract below. It returns an empty
node set:

<Schema name="ADT_A01" b:BizTalkServerEditorTool_Version="1.5"
b:root_reference="ADT-A01" b:standard="XML"
xmlns="urn:schemas-microsoft-com:xml-data"
xmlns:b="urn:schemas-microsoft-com:BizTalkServer"
xmlns:d="urn:schemas-microsoft-com:datatypes">
<b:SelectionFields />
<ElementType name="MSH_1_FieldSeparator" content="textOnly"
model="closed" b:type="string">
<description>Field Separator</description>
</ElementType>
</Schema>

If I remove the namespaces and their references the expression returns a
node set when applied to this XML extract. The Name property of the
XPathNodeIterator current property is Schema the Value property is Field
Separator which is the contents of the node description.

<Schema name="ADT_A01" BizTalkServerEditorTool_Version="1.5"
root_reference="ADT-A01" standard="XML">
<SelectionFields />
<ElementType name="MSH_1_FieldSeparator" content="textOnly"
model="closed" type="string">
<description>Field Separator</description>
</ElementType>
</Schema>


If anyone has some code samples that show how to manipulate the map I would
appreciate it!

Thanks!
--
The opinions stated above do not necessarily reflect those of St. Joseph's
Hospital,
The aforementioned institution takes no responsibility for the contents of
this message.

[ Post a follow-up to this message ]

Steve,

Have you tried the autolink feature?  Shift-click on a source parent node
and drag it to a destination parent node.  All the elements will get linked
by "Structure" or by "Node Name" (see the map properties).

Regards,
Tan Nguyen
Microsoft BizTalk Server

This posting is provided "AS IS", and confers no rights.

--------------------[vbcol=seagreen] 
and[vbcol=seagreen] 
would[vbcol=seagreen] 

[ Post a follow-up to this message ]

I think Tan recommendation applies to BizTalk 2004.
If I remember correctly autolink feature was added for BizTalk2004 and was n
ot present in BizTalk2002.

To learn write XPaths you can take a look at MSDN or [url]http://www.w3.org/TR/xpath.[/
url]
For example "/" should select the document root (Schema in your case).

Thanks,
Tatyana

--------------------
>X-Tomcat-ID: 531305683
>References: <#33QAs8eEHA.2468@TK2MSFTNGP12.phx.gbl>
>MIME-Version: 1.0
>Content-Type: text/plain
>Content-Transfer-Encoding: 7bit
>From: tanbn@online.microsoft.com (Tan Bao Nguyen)
>Organization: Microsoft
>Date: Fri, 06 Aug 2004 21:19:54 GMT
>Subject: RE: BTZ2002 Map Tool Enhancement?
>X-Tomcat-NG: microsoft.public.biztalk.tools
>Message-ID: <Gmxkgs$eEHA.1340@cpmsftngxa06.phx.gbl>
>Newsgroups: microsoft.public.biztalk.tools
>Lines: 87
>Path: cpmsftngxa06.phx.gbl
>Xref: cpmsftngxa06.phx.gbl microsoft.public.biztalk.tools:3957
>NNTP-Posting-Host: tomcatimport2.phx.gbl 10.201.218.182
>
>Steve,
>
>Have you tried the autolink feature?  Shift-click on a source parent node
>and drag it to a destination parent node.  All the elements will get linked
>by "Structure" or by "Node Name" (see the map properties).
>
>Regards,
>Tan Nguyen
>Microsoft BizTalk Server
>
>This posting is provided "AS IS", and confers no rights.
>
>-------------------- 
>and 
>would 
>
>


--

This posting is provided "AS IS" with no warranties, and confers no rights. 
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note:  For the benefit of the community-at-large, all responses to this mess
age are best directed to the newsgroup/thread from which they originated.

[ Post a follow-up to this message ]