<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to feature-requests</title><link>https://sourceforge.net/p/ovalutils/feature-requests/</link><description>Recent changes to feature-requests</description><atom:link href="https://sourceforge.net/p/ovalutils/feature-requests/feed.rss" rel="self"/><language>en</language><lastBuildDate>Fri, 29 Mar 2013 18:56:20 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/ovalutils/feature-requests/feed.rss" rel="self" type="application/rss+xml"/><item><title>update xmlbeans to use the 5.10.1 schemas</title><link>https://sourceforge.net/p/ovalutils/feature-requests/9/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;We need to update xmlbeans to use the 5.10.1 schemas in the merge utility.  It currently encounters errors when it tries to process content based on constructs added after 5.9.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Danny Haynes</dc:creator><pubDate>Fri, 29 Mar 2013 18:56:20 -0000</pubDate><guid isPermaLink="false">https://sourceforge.netc0b28d77f46ace146aef30bd4a7600aeb962892a</guid></item><item><title>Add change log to XSL Transforms</title><link>https://sourceforge.net/p/ovalutils/feature-requests/8/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Currently the changes between releases are only described in the SVN commit logs. We should add either a version.txt file or change log section to the README.txt file to track these changes.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">David Rothenberg</dc:creator><pubDate>Fri, 09 Nov 2012 19:56:20 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net03be348c3ee81b9933204e4885c1c053d7fde00c</guid></item><item><title>create a least version principle tool</title><link>https://sourceforge.net/p/ovalutils/feature-requests/7/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;It would be great if there was a command line tool where you could point to a directory of content and it would set the contents' schema_version to the least version.  If the tool had a recursive option that would be nice too.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Danny Haynes</dc:creator><pubDate>Thu, 27 Sep 2012 18:49:50 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net6c5ad98910102a0be29ad89425881b222e349914</guid></item><item><title>Allow users to run from any directory</title><link>https://sourceforge.net/p/ovalutils/feature-requests/6/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Because you have hardcoded the location of configuration files to be the current working directory, you have to run the utilities from the same directory where the jar exists. This makes the utilties a real pain to use.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Thu, 09 Feb 2012 19:36:00 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net5f6fad8fb22707e44eb7c5b48a93f0e212b6284f</guid></item><item><title>Create tool to do a cascading delete.</title><link>https://sourceforge.net/p/ovalutils/feature-requests/5/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Create a tool that will take an OVAL file as and input and allow the user to select one or more OVAL things (Definitions, Objects, States, Tests, &amp;amp; Variables) for deletion from the file.  The tool would then:&lt;/p&gt;
&lt;p&gt;1. Remove all of the references to the deleted things.&lt;br /&gt;
2. Review all of the dependencies for the deleted things, removing those that are now no longer referenced by anything else. &lt;/p&gt;
&lt;p&gt;The result would be an OVAL file without the deleted things as well as those dependencies that were no longer in use.&lt;br /&gt;
&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Matthew Hansbury</dc:creator><pubDate>Fri, 03 Feb 2012 15:43:54 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net5498f4e4c2c263af0492c85aed0be22b03bd046e</guid></item><item><title>Create tool for managing comments</title><link>https://sourceforge.net/p/ovalutils/feature-requests/4/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Create a tool that will apply an agreed-upon set of rules to auto-generate comments for a given OVAL file.  This tool would help content authors deal with the manual and sometimes difficult process of creating and maintaining required comments.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Matthew Hansbury</dc:creator><pubDate>Fri, 03 Feb 2012 15:23:15 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net980c3d6618bbd25b3b628bfe1ad126ffd12a1169</guid></item><item><title>Create merge oval-definitions documents utility</title><link>https://sourceforge.net/p/ovalutils/feature-requests/3/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;The Merge OVAL capability will be a Java command line utility that will take two OVAL Definition documents and merge them. The utility will output a result file that contains the contents of the two input files merged into one valid OVAL Definitions document. The conflict resolution process will be fairly simple. One document will be treated as the base document and items from the other document will be copied into the base document. If a conflict is detected the item in the base document will be overwritten. Once the merge operation is completed the resulting document will be validated and any validation issues will be reported. If we commit to developing this capability we will further investigate the conflict resolution algorithm.&lt;/p&gt;
&lt;p&gt;This utility should take 2 oval-definitions documents and merge them into one document. &lt;/p&gt;
&lt;p&gt;Should be able to:&lt;br /&gt;
- take input files as a local file on disk or a url.&lt;br /&gt;
- just use standard java arguments for this...&lt;br /&gt;
- allow the user to specify the output file&lt;br /&gt;
- designate one of the input files as the primary file for collisions.&lt;br /&gt;
- log all collisions&lt;br /&gt;
- use log4j with xml configuration file.&lt;br /&gt;
- use xmlbeans&lt;br /&gt;
- validate content in both input files and report errors&lt;br /&gt;
- log the occurrence of any collisions so the user knows they occurred.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jonathan Baker</dc:creator><pubDate>Thu, 28 May 2009 01:48:37 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net94a9fe04b2b9e0599902eeef4b81e2d231b9d852</guid></item><item><title>add command line flag to designate output xml file</title><link>https://sourceforge.net/p/ovalutils/feature-requests/2/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;user's should be able to optionally designate the output file name. &lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jonathan Baker</dc:creator><pubDate>Mon, 27 Apr 2009 15:54:49 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net8917ced7ae8552a95064df0377b91bf8ede9fded</guid></item><item><title>add command line flag to skip schematron validation</title><link>https://sourceforge.net/p/ovalutils/feature-requests/1/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;add a command line flag to allow the user to skip Schematron validation. The default shoudl continue to be to run the Schematron validation.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jonathan Baker</dc:creator><pubDate>Mon, 27 Apr 2009 15:46:04 -0000</pubDate><guid isPermaLink="false">https://sourceforge.netac978d1c1ea9af6d03d88cde368fa2c5f0465059</guid></item></channel></rss>