XML refactoring to move attribute value to a new attribute/element

pbentley · Post by **pbentley** » Mon Sep 19, 2022 11:42 pm

Hi there,
Is there a way that I can use XML Refactoring to move an attribute value to a different attribute and element?
I have a value like this: 
but I need to move it to here: <resourceid appid="section_2100.502" appname="legacy-id"/>
I've looked at the refactoring files but can't figure out how to accomplish this so any help would be great appreciated!

Thanks!
Peyton

Post by **Radu** » Tue Sep 20, 2022 8:24 am

Hi Peyton,

We do not have a predefined XML refactoring action to do exactly what you want.
You can implement your own custom XML refactoring actions based on XSLT or XQuery scripts:
https://www.oxygenxml.com/doc/versions/ ... tools.html
We have a bunch of sample XML refactoring actions based on XSLT here: https://github.com/oxygenxml/dita-refactoring-examples
For example an XSLT stylesheet for an XML refactoring operation doing something similar to what you want could look like this:

Code: Select all

<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
    xmlns:xs="http://www.w3.org/2001/XMLSchema"
    exclude-result-prefixes="xs"
    version="2.0">
    <xsl:template match="node() | @*">
        <xsl:copy>
            <xsl:apply-templates select="node() | @*"/>
        </xsl:copy>
    </xsl:template>
    <xsl:template match="prolog">
        <xsl:copy>
            <xsl:apply-templates select="@*"/>
            <xsl:apply-templates select="node()"/>
            <xsl:if test="//*[starts-with(@id, 'section_')]">
                <resourceid appid="{//*[starts-with(@id, 'section_')]/@id}" appname="legacy-id"/>
            </xsl:if>
        </xsl:copy>
    </xsl:template>
</xsl:stylesheet>

Regards,
Radu

Post by **chrispitude** » Tue Sep 20, 2022 12:52 pm

Hi Peyton,

Can you provide an example of the input and output you would like to see?

pbentley · Post by **pbentley** » Tue Sep 20, 2022 4:08 pm

Thanks, Radu! I'll look into that page.

I'm doing a whole series of refactoring combined with find/replaces but for this particular step, I'd have something like this as my input:
<body>

Accountability
(accountable).

<prolog>
<resourceid appid="" appname="legacy-id"/>
</prolog>
</body>

and I'd want to see this as the output:
<body>

Accountability
(accountable).

<prolog>
<resourceid appid="section_2100.502" appname="legacy-id"/>
</prolog>
</body>
Essentially just moving the id from the p down to the resourceid appid.
Thanks!!

Post by **chrispitude** » Tue Sep 20, 2022 4:50 pm

Hi Peyton,

In DITA, the <prolog> element should be before the <body> element. Can you confirm that is true in your content?

Will there only be a single  element with an @id defined, or could there be multiple such  elements?

Will all topics have an existing <prolog> element? Or will some topics have no <prolog> element, such that they will need to be created by the refactoring operation?

pbentley · Post by **pbentley** » Tue Sep 20, 2022 7:56 pm

Hi chrispitude,

Yes, the structure is right, with <prolog> following body. This is currently a specialized topic file that I'm refactoring to become a glossary file, so at this point in my refactoring/adjusting, the body is still there (but it will eventually get dropped/changed).
Each file will have only one and I added the <prolog> manually to each file (with an empty value for the appid) so no need for the refactoring to add it.

Thank you!

Post by **chrispitude** » Wed Sep 21, 2022 5:26 am

Hi Peyton,

First, you need a template to remove the @id attribute from the element:

Code: Select all

  <xsl:template match="p/@id"/>

To leave @id set to a blank value as you asked (which is not valid XML!)!, then you would do this:

Code: Select all

  <xsl:template match="p/@id">
    <xsl:attribute name="id" select="''"/>
  </xsl:template>

Now you need a second template to place the @id value where you want it. If you already have an empty <prolog> element, then you can do something like this:

Code: Select all

  <xsl:template match="prolog[preceding-sibling::p[@id]]">
    <xsl:copy>
      <resourceid appid="{preceding-sibling::p[@id][1]/@id}" appname="legacy-id"/>
    </xsl:copy>
  </xsl:template>

(The curly braces in an attribute value allow an XPath expression to be evaluated for the value.)

If some <prolog> elements do not yet exist, or they do exist and contain other metadata, then some smarter templates would be needed to handle those cases too.

XML refactoring to move attribute value to a new attribute/element

XML refactoring to move attribute value to a new attribute/element

Re: XML refactoring to move attribute value to a new attribute/element

Re: XML refactoring to move attribute value to a new attribute/element

Re: XML refactoring to move attribute value to a new attribute/element

Re: XML refactoring to move attribute value to a new attribute/element

Re: XML refactoring to move attribute value to a new attribute/element

Re: XML refactoring to move attribute value to a new attribute/element