Using xsd file - xmlDraft - Products - SysOnyx Inc. - Message Board - Yuku

RSS
Email

0 Kudo

<< Previous Topic Next Topic >>

Using xsd file

Author	Comment
RMittelman	Using xsd file	Lead	[-]
Posts: 50 (11/17/04 10:56:45) Reply Quote More My Recent Posts Message Me Connection Blocking Invite Ignore User's Posts	Tags : None Ok, this is probably a stupid question. How do I actually USE the xsd file I create? This is related to my thread in xmlLinguist forum on features. I imported an xml file which looks like this: <?xml version="1.0" encoding="utf-8"?><EDI_Info> <HeaderInfo> <DocType>278</DocType> <DocDate>10/18/04</DocDate> <DocTime>3:08 pm</DocTime> </HeaderInfo> <PayerInfo> <ID></ID> </PayerInfo> <RequesterInfo> <ID></ID> </RequesterInfo> <SubscriberInfo> <LastName>JONES II</LastName> <FirstName>Erle</FirstName> <MiddleName></MiddleName> <Suffix></Suffix> <Subscriber-Member>126701759000</Subscriber-Member> <SrcSystem-Plan>WGS2BCC</SrcSystem-Plan> </SubscriberInfo> <DiagnosisInfo> <DiagnosisCodeQualifier>BK</DiagnosisCodeQualifier> <DiagnosisCode>7999</DiagnosisCode> </DiagnosisInfo> <ClaimNotesInfo> <ClaimNotes></ClaimNotes> </ClaimNotesInfo> <ServiceProviderInfo> <LastName>Lewis</LastName> <FirstName>John</FirstName> <MiddleName></MiddleName> <Suffix></Suffix> <ID>123456789</ID> <ProviderID>+LewiJA00106</ProviderID> <SrcSystem>MATRIX</SrcSystem> </ServiceProviderInfo> <ServiceLevelInfo> <TraceTypeCode1></TraceTypeCode1> <ClaimNo1>ClaimNo</ClaimNo1> <OrigCoID1></OrigCoID1> <OrigClaimNo1></OrigClaimNo1> <TraceTypeCode2></TraceTypeCode2> <ClaimNo2></ClaimNo2> <OrigCoID2></OrigCoID2> <OrigClaimNo2></OrigClaimNo2> <TraceTypeCode3></TraceTypeCode3> <ClaimNo3></ClaimNo3> <OrigCoID3></OrigCoID3> <OrigClaimNo3></OrigClaimNo3> <ServiceCode></ServiceCode> </ServiceLevelInfo> <DrugInfo> <Drug> <DrugCode>01698</DrugCode> <BeginDate>3/3/04</BeginDate> <EndDate>6/3/04</EndDate> <Quantity>4</Quantity> </Drug> </DrugInfo></EDI_Info> With regards to the <DrugInfo> section: I want to have exactly 12 <Drug> sections in the resulting file. So, I went in and edited the Drug section of the tree area. I don't know what Inline means, but I assume it's related to a complex type. I couldn't figure out how to add a Drug line under the DrugInfo line, so I had to re-design my source xml file and re-import it. Also, there is no available properties area for that inline type line. So I customized the columns and added min & max occurrances columns, and entered 12 in each on the Drug line. This did update the text area below. So, exporting the file as xml sample didn't really help, I expected it to now have 12 Drug nodes, which it didn't. I'd like to "push" the original xml file through this schema and see what comes out, but I don't exactly know how. Could you explain how to do this? Maybe a vbScript sample, such as the xml-to-850 one that comes with xmlLinguist? Thanks...
RMittelman	Re: Using xsd file	#1	[-]
Posts: 50 (11/17/04 11:26:50) Reply Quote More My Recent Posts Message Me Connection Blocking Invite Ignore User's Posts	In the instance tree, no matter what level of item is selected, the Node Type property area displays either NodeName(Inline) or xsd:String, but when you click in there and drop-down the list, it always has only "attribute" and "element". I don't get this, shouldn't it have other context-sensitive choices like the help file says?
Bryce K Nielsen	Re: Using xsd file	#2	[-]
Posts: 230 (11/18/04 12:43:57) Administrator Reply Quote More My Recent Posts Message Me Connection Blocking Invite Ignore User's Posts	The NodeType dropdown should do one of two things: - If it's a simpleType, all built-in XSD types are listed, and at the bottom of the dropdown, all global simpleType nodes are listed - If the node is a complexType, the dropdown lists "(inline)" when the element is not referencing a global complexType (i.e. there is no type attribute and the child element is a xs:complexType node). You seem to be experiencing a bug that slipped past testings. Can you send me a copy of your schema? As for the actual usage, it will be similar to how you're using stylesheets. Just like XSL, XSD doesn't really do anything in-and-of-itself, you need a parser to apply the document with. MSXML4 is pretty good (I don't think ver 3 has support for XSD). msdn.microsoft.com has a bunch of info on how to do this with their parser. -BKN
RMittelman	Re: Using xsd file	#3	[-]
Posts: 50 (11/18/04 17:16:37) Reply Quote More My Recent Posts Message Me Connection Blocking Invite Ignore User's Posts	I'm trying to apply a schema (see the one I e-mailed you) to an incomplete source document (incomplete to the extent that there are 2 node sets where the schema says there should be 3, for example). The document agrees with the schema in every other regard. I tried to send it the following xml file: <?xml version="1.0" encoding="utf-8"?><EDI_Info> <HeaderInfo> <DocType>278</DocType> <DocDate>10/18/04</DocDate> <DocTime>3:08 pm</DocTime> </HeaderInfo> <DrugInfo> <Drug> <DrugCode>one</DrugCode> <BeginDate>1/1/04</BeginDate> <EndDate>1/1/04</EndDate> <Quantity>1</Quantity> </Drug> <Drug> <DrugCode>two</DrugCode> <BeginDate>2/2/04</BeginDate> <EndDate>2/2/04</EndDate> <Quantity>2</Quantity> </Drug> </DrugInfo></EDI_Info> I can get the file validated by using the following VB code: Public Sub Main() Dim sc As New MSXML2.XMLSchemaCache50 Dim d1 As New MSXML2.DOMDocument50 Dim d2 As New MSXML2.DOMDocument50 Dim src As String Dim bOk As Boolean sc.Add "", "MyXSDFile.xsd" src = "MySourceXMLFile.xml" d1.async = False d1.Load src d2.async = False Set d2.schemas = sc bOk = d2.loadXML(d1.xml) If Not bOk Then Debug.Print d2.parseError.reason Debug.Print "Source:" Debug.Print d1.xml Debug.Print Debug.Print "Output:" Debug.Print d2.xml Stop Set d1 = Nothing Set sc = NothingEnd Sub If I set <Drug>'s min & max to 2 in the xsd, all is well, both outputs agree. If I raise them to 3 or more, save the file, and run the app, the destination is empty, and the error line says "Content for element 'DrugInfo' is incomplete according to the DTD/Schema." So obviously I'm missing something. I've tried giving the sub-nodes default values, that didn't help. Instead of a fail notice, I want it to supply the "missing" nodes to the output file. Is that so hard to do? I've searched for about an hour on Microsoft and other sites via Google, and can't find out how to use the schema in this manner. So now I'm ready to dump the whole schema idea, and just hard-code everything using choose for every possible element in the xsl file. Signed, Frustrated in XML-land
Bryce K Nielsen	Re: Using xsd file	#4	[-]
Posts: 230 (11/18/04 18:41:12) Administrator Reply Quote More My Recent Posts Message Me Connection Blocking Invite Ignore User's Posts	You know what, I think you're right. For some reason I was confusing the default value of an Element with the ability to force blank nodes. I don't think XSD will do this... Here's another solution, then, using xsl:templates. This will reduce a lot of the replicated hardcoded typing. I was avoiding this initially since it does add another layer of complications to everything, but I think you're ready ;) Add this node at the "global" level (i.e. as a child of the xsl:stylesheet node): <xsl:template name="DrugData"> <xsl:param name="Number" /> <xsl:choose> <xsl:when test="DrugInfo/Drug[number($Number)]"> <xsl:element name="{concat('HI011-PROCEDURE-CD-Q-', $Number)}">BO</xsl:element> <xsl:element name="{concat('HI012-PROCEDURE-CD-', $Number)}"><xsl:value-of select="DrugInfo/Drug[number($Number)]/DrugCode"/></xsl:element> <xsl:element name="{concat('HI013-DATE-FORMAT-', $Number)}">RD8</xsl:element> <xsl:element name="{concat('HI014-DATE-', $Number)}"><xsl:value-of select="user:GetDateYYYYMMDD(string(DrugInfo/Drug[number($Number)]/BeginDate))"/>-<xsl:value-of select="user:GetDateYYYYMMDD(string(DrugInfo/Drug[number($Number)]/EndDate))"/></xsl:element> <xsl:element name="{concat('HI016-QUANTITY-', $Number)}"><xsl:value-of select='format-number(DrugInfo/Drug[number($Number)]/Quantity * 100,"000000000")'/></xsl:element> <xsl:element name="{concat('HI017-VERSION-ID-', $Number)}">RD8</xsl:element> </xsl:when> <xsl:otherwise> <xsl:element name="{concat('HI011-PROCEDURE-CD-Q-', $Number)}">BO</xsl:element> <xsl:element name="{concat('HI012-PROCEDURE-CD-', $Number)}"><xsl:value-of select="DrugInfo/Drug[number($Number)]/DrugCode"/></xsl:element> <xsl:element name="{concat('HI013-DATE-FORMAT-', $Number)}">RD8</xsl:element> <xsl:element name="{concat('HI014-DATE-', $Number)}"><xsl:value-of select="user:GetDateYYYYMMDD(string(DrugInfo/Drug[number($Number)]/BeginDate))"/>-<xsl:value-of select="user:GetDateYYYYMMDD(string(DrugInfo/Drug[number($Number)]/EndDate))"/></xsl:element> <xsl:element name="{concat('HI016-QUANTITY-', $Number)}"><xsl:value-of select='format-number(0,"000000000")'/></xsl:element> <xsl:element name="{concat('HI017-VERSION-ID-', $Number)}">RD8</xsl:element> </xsl:otherwise> </xsl:choose></xsl:template> Then, inside of your original area, remove all that code and just use this: <xsl:call-template name="DrugData"> <xsl:with-param name="Number">1</xsl:with-param> </xsl:call-template> <xsl:call-template name="DrugData"> <xsl:with-param name="Number">2</xsl:with-param> </xsl:call-template> <xsl:call-template name="DrugData"> <xsl:with-param name="Number">3</xsl:with-param> </xsl:call-template> Repeat that 12 times and I believe that's what you're looking for. -BKN
Bryce K Nielsen	Re: Using xsd file	#5	[-]
Posts: 230 (11/18/04 18:47:04) Administrator Reply Quote More My Recent Posts Message Me Connection Blocking Invite Ignore User's Posts	I got your schema and now I see what you're talking about. The NodeType in the PROPERTIES window, not in the Instance Tree window, is only showing two very wrong values. Yeaup, that's a bug. A workaround, in the Instance Tree window, do a Right Click -> Customize Columns and find the "Type" column. Drag that into the grid, and _that_ dropdown should work for you. Sorry 'about that, -BKN
RMittelman	Re: Using xsd file	#6	[-]
Posts: 50 (11/19/04 15:06:39) Reply Quote More My Recent Posts Message Me Connection Blocking Invite Ignore User's Posts	Wow...That was the coolest solution yet! I've modified all the repeating-field sections in each record, and put templates in for each, works like a charm. So, I don't need no stinkin' schema editor! (at least for this project) Thanks for all your help.
Bryce K Nielsen	Re: Using xsd file	#7	[-]
Posts: 230 (11/19/04 16:17:29) Administrator Reply Quote More My Recent Posts Message Me Connection Blocking Invite Ignore User's Posts	Hehehe, good on ya! Glad to see things coming together. XSL is an interesting beast, you truly can do a lot of amazing things with it, but takes a while to start seeing how to do what. -BKN

<< Previous Topic Next Topic >>

Quick Reply