1060 Forum - Recent Entries

Re: Ignore an element

Fri, 27 Jun 2008 007:47:00 GMT

Hi Arul,

Thanks for the question. There are various ways to ignore an element during the comparison. I have outlined a couple below.

The simplest solution is to remove the element you wish to ignore before comparing. All this requires a simple input filter. It does mean that the element isn't in the result file at all, this may of course not be what you require.

Another possible solution is to leave the element in for comparison but then convert it back to the version that was in one of the input documents. This requires an output filter and again, this should be relatively easy to write. Take a look at dx2-extract-version.xsl in the xsl samples directory for an example of how to output a particular version of an element (or in the case of the XSL filter, the whole file).

These are just a couple of suggestions, if you could provide a more detailed example of what you are trying to achieve, we will be able to give you some more relevant help with a solution.

Many thanks,

Tristan

Ignore an element

Fri, 27 Jun 2008 007:47:00 GMT

I would like to know how to ignore an element. Defining keys based on the id attribute is not appropriate in this case.
Could you provide me some samples for ignoring an element?

Hai chrisc

Thu, 19 Jun 2008 15:50:00 GMT

Thanks for your support. It works fine now. I am also in need of another help. I would like to know how to ignore an element. I looked out for samples in your site. I got samples only for ignoring some attributes.

Could you provide me some samples for ignoring an element?

Thanks,
Arul

re: ignore all attributes of an element

Thu, 19 Jun 2008 15:50:00 GMT

There are various settings that control the matching. Looking at this data it appears that you weren't using the enhanced matcher.

When I run this command:

java -jar /usr/local/DeltaXMLCore-5_0/command.jar compare delta f1.xml f2.xml f12.xml

I the following result (using the new deltaV2 format):

<footnotes xmlns:deltaxml="http://www.deltaxml.com/ns/well-formed-delta-v1" xmlns:dxa="http://www.deltaxml.com/ns/non-namespaced-attribute" deltaxml:deltaV2="A!=B">
  <footnote deltaxml:deltaV2="A" alt="1" id="61177" label="1" order="2" size="1">
    <para>New Footnote</para>
  </footnote>
  <footnote deltaxml:deltaV2="A!=B" alt="1" id="61178" order="2" size="1">
    <deltaxml:attributes deltaxml:deltaV2="A!=B">
      <dxa:label deltaxml:deltaV2="A!=B">
        <deltaxml:attributeValue deltaxml:deltaV2="A">2</deltaxml:attributeValue>
        <deltaxml:attributeValue deltaxml:deltaV2="B">1</deltaxml:attributeValue>
      </dxa:label>
    </deltaxml:attributes>
    <para deltaxml:deltaV2="A=B">share report</para>
  </footnote>
</footnotes>

This command has the enhanced matcher turned on by default. With this command:

java -jar /usr/local/DeltaXMLCore-5_0/command.jar compare delta f1.xml f2.xml f12.xml "Enhanced Match 1=false"

I get a similar result to the one you posted.

If you are coding using the API see the feature settings information in the javadoc.

The enhanced matcher takes note of the PCData in the <para> child elements when aligning the <footnote> elements. There are other ways of aligning the footnotes, one of which is to assign higher priority to certain attributes using deltaxml:keys. Perhaps defining keys based on the id attribute would be appropriate in this case?

If so this can be achieved with an input XSLT filter which adds the deltaxml:key attribute to each of your footnote elements. Keys are discussed in http://www.deltaxml.com/dxml/library/how-to-use-keys.html and there is an interactive example.

And if you are looking for sample code, including an XSLT filter please see the AddressBook sample program in the release.

Now the matching is more appropriate, it should then be possible to address any issues with the attributes. You could decide to:

- remove the label attribute from the result
- use either the A or B values when there is a difference.

Are any of these appropriate? When you say you want to ignore an attribute change, what are you trying to achieve? We can provide some sample code but we need to understand the requirement a little more.

ignore all attributes of an element

Thu, 19 Jun 2008 15:50:00 GMT

But my problem is totally different. Please look at this problem I have attached the code also. I have two footnotes and i have deleted one and taking diff xml using deltaxml api. Please look at the code give provide me some samples.

old xml
<footnote alt="1" id="61177" label="1" order="2" size="1"> <para>New Footnote</para>
</footnote>
<footnote alt="1" id="61178" label="2" order="2" size="1"> <para>share report</para>
</footnote>
new xml
<footnote alt="1" id="61178" label="1" order="2" size="1"> <para>share report</para>
</footnote>
diff xml
<footnote id="61177" deltaxml:delta="WFmodify" alt="1" label="1" order="1" size="1">
<para deltaxml:delta="WFmodify"><deltaxml:PCDATAmodify><deltaxml:PCDATAold>
New Footnote</deltaxml:PCDATAold>
<deltaxml:PCDATAnew>share report</deltaxml:PCDATAnew></deltaxml:PCDATAmodify></para></footnote>
<footnote deltaxml:delta="delete" alt="1" id="61178" label="2" order="2" size="1"><para>share report.</para></footnote>

In the above new xml I have deleted one footnote and i want to compare the old and new xml. I have to get the result as first footnote as deleted. But i get the result as modified. For this i fount label is same for the first element in both xml. So i want to ignore this I would like to get the xsl file for this and do i have to set this as input filter or output filter.

DeltaXML Core 5.0

Thu, 29 Mar 2007 11:38:00 GMT

DeltaXML Core 5.0 is now available. This is a major new release
with these features:

- A new delta format ('deltaV2') which is easier to
process with XSLT/XPath/XQuery.

- New filters and some new pipelines, particularly
suited to document-centric XML.

- Some API-level changes, including some new methods,
improved error/exception handling and API
house-keeping including the removal of some
previously deprecated features.

Further details are provided in the release notes:

http://www.deltaxml.com/core/current/docs/release-notes.html

While this release defaults to use the new delta format, the old
format is still available through a feature setting. We would
encourage existing users to upgrade to the new format and filters.
However, support for users who wish to continue to use deltaV1
and the current filters is available via a 'Filter Compatibility Pack'
or 'FCP'. For more information:

http://www.deltaxml.com/library/filter-migration.html
http://www.deltaxml.com/library/downloads.html

The feature-walkthroughs, sandboxes, online services and technical
documentation on the DeltaXML website have been updated to support this
release. The following link provides an index to the documentation:

http://www.deltaxml.com/library/index.html

Enterprise release customers with current support contracts can request
a Core 5.0 build be prepared and made available at their download area.

Evaluations of DeltaXML Core 5.0 are available to registered users of
the DeltaXML website. We have reset all user records so that even if
you have previously had an evaluation you can now request a new
evaluation activation key for 5.0. These can be used with the
5.0 download available from the website (after registered-user login).

Named-user and Professional-server customers with annual maintenance
will shortly receive their new activation keys via email.

As always, feedback is welcome via the website support forums or
via our usual support channels for enterprise customers.

Thanks for the update/plans