XML / XSL

Schema for "Element or List of Elements"

27-Oct-06 8:03

Just change your code to trim off the leading and trailing spaces:

Dim customer_code = invoiceId.InnerText.Trim()

peterchen25-Oct-06 6:06

peterchen

25-Oct-06 6:06

I want to define a schema for an XML fiel that contains either a "Topic" or a "TopicList" which is a collection of topics.

i.e. the XML file should contain either

<?xml blubber?>
<Topic>

</Topic>

or

<?xml blubber?>
<TopicList>
<Topic>

</Topic>

<Topic>

</Topic>

</TopicList>

I currently make the topic list required, but I'm curious how to avoid that.

led mike25-Oct-06 8:58

led mike

25-Oct-06 8:58

peterchen wrote:
but I'm curious how to avoid that.

Why would you want to? It seems your current solution is correct.

led mike

peterchen25-Oct-06 9:15

peterchen

25-Oct-06 9:15

It's more a general question: can I check against different "top level tags" with one Schema?

All use cases I can imagine a mandatory "outer tag" solves things. But I'm doing my first "serious toying" with XML, I still don't like all these tags^*, I come from a "be strict with your output, but flexible on your input" culture, and I just want to KNOW Wink | ;)

a client once wanted 500 point curves exported as <point><X>12.34</X><Y>123.42</Y></point> in a time critical high throughput application - bno problem making them happy, but I'm still a big XML sceptic.

We are a big screwed up dysfunctional psychotic happy family - some more screwed up, others more happy, but everybody's psychotic joint venture definition of CP

Linkify! || Fold With Us! || sighist

Michael Dunn25-Oct-06 9:30

Michael Dunn

25-Oct-06 9:30

It's much easier to always have the outer container tag, no matter how many tags are inside it. That way, you can enumerate all the Topics with a simple /TopicList/Topic XPath query. Don't take shortcuts on your schema just to save yourself 5 seconds of typing. Wink | ;)

--Mike--
Visual C++ MVP Cool | :cool:

LINKS~! Ericahist | PimpFish | CP SearchBar v3.0 | C++ Forum FAQ

BoneSoft27-Oct-06 10:29

BoneSoft

27-Oct-06 10:29

This is easy to do in the Schema, the software that uses it is where the complication comes in with this type of structure. Never understood why someone would want to do this, but it can be done.

<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified">
	<xs:complexType name="Topic">
	</xs:complexType>
	<xs:complexType name="TopicList">
		<xs:sequence>
			<xs:element type="Topic" minOccurs="0" maxOccurs="unbounded"></xs:element>
		</xs:sequence>
	</xs:complexType>
	<xs:complexType name="RootNode">
		<xs:choice>
			<xs:element type="Topic"></xs:element>
			<xs:element type="TopicList"></xs:element>
		</xs:choice>
	</xs:complexType>
	
	<xs:element type="RootNode"></xs:element>
</xs:schema>

Your root node is of type "RootNode", which is a Choice, meaning it will accept either a "Topic" or a "TopicList". And "TopicList" is a sequence of "Topics".

Try code model generation tools at BoneSoft.com.

peterchen27-Oct-06 12:06

peterchen

27-Oct-06 12:06

thanks a lot for the reply!

BoneSoft wrote:
the complication comes in with this type of structure. Never understood why someone would want to do this, but it can be done.

OK OK, I get the hints Wink | ;)

KaЯl2-Nov-06 21:35

KaЯl

2-Nov-06 21:35

IMHO, if the concept of TopicList exists and the info meaningful, it should be represented explicitly.

We're the regulators that de-regulate
We're the animators that de-animate

Fold with us! ¤ flickr

XSL/Xpath Problem

Sarvis24-Oct-06 17:23

24-Oct-06 17:23

This is my first attempt at making "real" modifications to an xsl stylesheet, and I'm completely stumped now. This is probably something simple, so try not to laugh too much. Wink | ;)

Here's the code I'm having trouble with:

<xsl:variable name="reportName">
<xsl:value-of select="NodeName"/>
</xsl:variable>

<xsl:value-of select="$reportName"/>


<xsl:value-of select="//PageXML/Document/report[name = $reportName]/regionalFlag"/>


<xsl:value-of select="//PageXML/Document/report[name = 'workordertime']/regionalFlag"/>

Now, I'm printing the value of $reportName every time and it IS coming up as workordertime, but for some reason it isn't selecting any value. If I hardcode the report name, however, it DOES work... so the basic XSL is right. I'm fairly sure that's how I'd use a variable to do the select, as the same technique is used in other places... I have no idea what could be causing the problem...

Elina Blank25-Oct-06 2:39

Elina Blank

25-Oct-06 2:39

Try using parameter instead of variable

Sincerely,
Elina

Life is great!!!
Enjoy every moment of it! Blush | :O

Sarvis25-Oct-06 4:46

25-Oct-06 4:46

Parameters are passed into the stylesheet though right? That won't help here, I'm running through a list of reports from the source sheet, and trying to find configuration information for each report also in the source sheet... so it's not something I can just pass in on the command line.

Elina Blank25-Oct-06 5:45

Elina Blank

25-Oct-06 5:45

You define the parameter the same way as you devine the variable.
Just write: xsl:parameter.

I have no idea, if it is passed throught stylesheets. sorry Frown | :(

Sincerely,
Elina

Life is great!!!
Enjoy every moment of it! Blush | :O

Sarvis25-Oct-06 10:22

25-Oct-06 10:22

I get an error saying that xsl:parameter is an invalid child element when I try to use it.

Elina Blank26-Oct-06 3:38

Elina Blank

26-Oct-06 3:38

Sorry, it is xsl:param, not xsl:parameter

Sincerely,
Elina

Life is great!!!
Enjoy every moment of it! Blush | :O

Sarvis27-Oct-06 12:04

27-Oct-06 12:04

That gives me a syntax error too, which says the same basic thing only with fewer words.

Dustin Metzgar26-Oct-06 9:33

26-Oct-06 9:33

This actually works just fine. Could you please elaborate on what "name" is? I assume it's a child element of report. There's nothing that I can see would be wrong with this code. Could you also please give some indication on what that non-working statement is returning in the output?

Sarvis26-Oct-06 14:02

26-Oct-06 14:02

Yes, I'm pretty sure name is a child element of report. I'm not at work now though so I can't look. It SHOULD print out "true" when it gets to the workordertime report but I'm getting nothing at all. It prints out "true" fine when I hardcode 'workordertime' instead of using the $reportname variable though.

I can look at the source xml tomorrow and post it, I didn't have a chance to work on that today anyway.

Dustin Metzgar27-Oct-06 7:59

27-Oct-06 7:59

One thing that I thought of is that there may be some whitespace in the variable that is not in your hard coded 'workordertime'. You might want to try this:

<xsl:variable name="reportName">
   <xsl:value-of select="normalize-space(NodeName)"/>
</xsl:variable>

Sarvis27-Oct-06 12:03

27-Oct-06 12:03

Normalize-space didn't work. Frown | :(

Here's the relevant part of the source XML:

<PageXML>
<Ident>14</Ident>
<PageIdent>266</PageIdent>
<Name>test</Name>
<Document>
<report>
<name>workordertime</name>
<regionalFlag>true</regionalFlag>
</report>
</Document>
</PageXML>

The whole document would be way too large to post...

Dustin Metzgar27-Oct-06 12:21

27-Oct-06 12:21

Could you find the NodeName node in the XML and post what that looks like?

www.logifusion.com

Sarvis27-Oct-06 13:07

27-Oct-06 13:07

Here's a little more of the original xsl that is failing. I thought this would be a simple syntax error or something so didn't post the surrounding loop.

Here it is:

<xsl:for-each select="//node[NodeParentNodeIdent = $ThisIdent][PagePublished = 'True']">
<xsl:if test="NodeIdent = //LinkedPageDetail/PageIdent">

<xsl:copy-of select=""/>

<xsl:variable name="reportName" >
<xsl:value-of select="normalize-space(NodeName)"/>
</xsl:variable>

<xsl:value-of select="$reportName"/>
<xsl:value-of select="//PageXML/Document/report[name = $reportName]/regionalFlag"/>
<br />


<xsl:variable name="regionFlag">
<xsl:value-of select="//PageXML/Document/report1"/>
</xsl:variable>

<p><a href="{PageBreadcrumb}?UseRegions={$regionFlag}" target="_blank"><xsl:value-of select="PageTitle" disable-output-escaping="yes"/></a></p>
</xsl:if>
</xsl:for-each>

And here is the current node of that loop when it should find the workordertime report and print it's value:

<node>
<TreeIdent>2</TreeIdent>
<NodeIdent>274</NodeIdent>
<TreeName>Synergy - ePortal</TreeName>
<NodeName>workordertime</NodeName>
<NodeLevel>3</NodeLevel>
<NodeParentNodeIdent>273</NodeParentNodeIdent>
<SiteIdent>2</SiteIdent>
<SiteSortOrder>1</SiteSortOrder>
<SiteName>Synergy - ePortal</SiteName>
<SiteDescription>Synergy - ePortal</SiteDescription>
<SiteTitle>Web Site - Synergy - ePortal - QuantumCMS</SiteTitle>
<SitePublished>True</SitePublished>
<PageShowInNav>False</PageShowInNav>
<PageBreadcrumb>/Home/Reports/summaries/workordertime</PageBreadcrumb>
<PageIdent>274</PageIdent>
<PageSortOrder>1</PageSortOrder>
<PageName>workordertime</PageName>
<PageDescription>Workorder Time</PageDescription>
<PageTitle>Workorder Time</PageTitle>
<PageLevel>3</PageLevel>
<PageLeftBound>125</PageLeftBound>
<PageRightBound>126</PageRightBound>
<ParentNodeIdent>273</ParentNodeIdent>
<ParentPageIdent>273</ParentPageIdent>
<PageTypeIdent>1</PageTypeIdent>
<PageTypeName>Document</PageTypeName>
<PageSummary></PageSummary>
<PageReleaseDate>2006-10-03T00:00:00.0000000-04:00</PageReleaseDate>
<PageRevision>1</PageRevision>
<PageCached>False</PageCached>
<PageSearched>False</PageSearched>
<PageRequired>False</PageRequired>
<PagePublished>True</PagePublished>
<PageActive>True</PageActive>
<PageURL>/Home/Reports/summaries/workordertime</PageURL>
</node>

It's basically inside of another node just like it, and this for-each loop is an inner loop from another for-each loop.

Dustin Metzgar27-Oct-06 14:08

27-Oct-06 14:08

Well, I thought maybe NodeName had something strange about it, but that doesn't seem to be the case. The variable looks fine and I recreated very similar XML and XSL files and it worked without a problem. There are two things I can think of to try. First, declare your variable like this:

<xsl:variable name="reportName" select="NodeName"/>

But I doubt that will have an effect. The other thing is to comment out that if statement in the loop. It may be correct, but it looks like a really odd syntax. NodeIdent = //LinkedPageDetail/PageIdent looks to me like you're comparing the contents of NodeIdent to a list of nodes PageIdent anywhere in the document. It may be putting you in a different position in the XML document unexpectedly.

Just grasping at straws really.

Logifusion[^]

Sarvis1-Nov-06 4:35