IMPORTANT:
this is not a Support Forum! Experienced users might answer from time to time questions posted here. If you need a professional and reliable answer, or if you want to report a bug, please contact Altova Support instead.

Profile: Gibson335
About
User Name: Gibson335
Forum Rank: Member
Real Name:
Location Sweden
Occupation:
Interests:
Gender: None Specified
Statistics
Joined: Monday, September 18, 2017
Last Visit: Monday, March 18, 2019 9:12:33 AM
Number of Posts: 10
[0.06% of all post / 0.00 posts per day]
Avatar
Last 10 Posts
Topic: XSLT - Disabling that deafult attributes gets added to result
Posted: Sunday, March 17, 2019 11:20:18 AM
Unchecking "Validate XML files used in transformation" seems to solve this problem.
Topic: XSLT - Disabling that deafult attributes gets added to result
Posted: Friday, March 15, 2019 9:57:15 PM
I know this has been answered before, but is it still impossible to disabling that default attributes are added to the transformed output? I get a lot of attributes added when making a simple identity transform, and this is not desired...
Topic: Mapping S1000D XML to other things
Posted: Friday, October 20, 2017 6:41:47 PM
Great initiative. I'm hoping that I can contribute to this topic in the future. I'm just beginning to using this tool so I'm not that Confident in my skills just yet ;-)
Topic: Grouping elements under new parent elements
Posted: Friday, October 20, 2017 1:38:57 PM
Yes it is. Sorry for the late reply, but my PC just got the better of me for a while...
Topic: Grouping elements under new parent elements
Posted: Monday, September 18, 2017 10:33:18 AM
Thank you - worked like a charm :-)
Topic: Grouping elements under new parent elements
Posted: Monday, September 18, 2017 7:05:50 AM
Source xml-fragment:
<legend>
<deflist>
<term>1.</term>
<def>Target A</def>
<term>2.</term>
<def>Target B</def>
<term>3.</term>
<def>Target D</def>
</deflist>
</legend>

Target xml-fragment:
<legend>
<definitionList>
<definitionListItem>
<listItemTerm>1.</listItemTerm>
<listItemDefinition>
<para>Target A</para>
</listItemDefinition>
</definitionListItem>
<definitionListItem>
<listItemTerm>2.</listItemTerm>
<listItemDefinition>
<para>Target B</para>
</listItemDefinition>
</definitionListItem>
<definitionListItem>
<listItemTerm>3.</listItemTerm>
<listItemDefinition>
<para>Target D</para>
</listItemDefinition>
</definitionListItem>
</definitionList>
</legend>

Since I have no element to connect to my parent element "definitionListItem", I get into some problems. One element containing all listItemTerms is created when I do not connect anything, but that is not the desired structure. Can I achieve this in MapForce or do I have to write this directly in xslt?

Use of the Altova User Forum(s) is governed by the Altova Terms of Use.