StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
12315962
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-09-07T10:05:48.980
FavoriteCount
0
LastActivityDate
2012-09-07T10:05:48.980
LastEditDate
LastEditorUserId
0
OwnerUserId
7585
ParentId
12315353
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
One way to do this in XSLT1.0 is define a key that groups the non-pid elements under person-list, by the first most preceding pid element <pre><code><xsl:key name="fields" match="person-list/*[not(self::pid)]" use="generate-id(preceding-sibling::pid[1])" /> </code></pre> Then, for the person-list element, you would select just the pid elements <pre><code><xsl:apply-templates select="pid" /> </code></pre> And within the template that matches the pid you would create a person element, and output the other elements using the key: <pre><code><xsl:apply-templates select="key('fields', generate-id())" /> </code></pre> Here is the full XSLT <pre><code><xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> <xsl:output method="xml" indent="yes"/> <xsl:key name="fields" match="person-list/*[not(self::pid)]" use="generate-id(preceding-sibling::pid[1])" /> <xsl:template match="person-list"> <person-list> <xsl:apply-templates select="pid" /> </person-list> </xsl:template> <xsl:template match="pid"> <person> <xsl:copy-of select="." /> <xsl:apply-templates select="key('fields', generate-id())" /> </person> </xsl:template> <xsl:template match="@*|node()" name="identity"> <xsl:copy> <xsl:apply-templates select="@*|node()"/> </xsl:copy> </xsl:template> </xsl:stylesheet> </code></pre> When applied to your sample XML, the following is output <pre><code><person-list> <person> <pid>100</pid> <pname>Tom Jones</pname> <pdescription>Some Text</pdescription> </person> <person> <pid>101</pid> <pname>John Thomas</pname> <pdescription></pdescription> </person> </person-list> </code></pre> Note that with approach you could add further fields to you input document for each person without the need for amending the XSLT. Also note the use of the 'identity transform' to copy existing elements.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POxslt transform sequence with maxOcurs=unbounded to nested elements
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USTim C
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.