<html> <head> <meta http-equiv="content-type" content="text/html; charset=UTF-8"> </head> <body text="#000000" bgcolor="#FFFFFF"> <div class="moz-cite-prefix">On 11/20/2012 02:42 PM, Simon Lukasik wrote: </div> <blockquote class=" cite" id="mid_50ABDD32_9070203_redhat_com" cite="mid:50ABDD32.9070203@redhat.com" type="cite"> <pre wrap="">And regarding filenames you've mentioned: .*-{xccdf,cpe,oval}.xml -- is this really a standard file-naming scheme or is it just commonly used? Currently, there is no consensus amongst developers whether the oscap command-line tool shall try to guess filenames or not. And I believe it should not.</pre> </blockquote> I believe the same. The document naming conventions first appeared in NIST <a href="http://csrc.nist.gov/publications/nistpubs/800-126-rev1/SP800-126r1.pdf">SP 800-126 rev 1</a> §3.1. There were none in the prior, initial version. An intricately more elaborate scheme of titanic scope and consequence is presented in <meta http-equiv="content-type" content="text/html; charset=UTF-8"> <a href="http://csrc.nist.gov/publications/nistpubs/800-126-rev2/SP800-126r2.pdf">SP 800-126 rev 2</a> §3. I don't think either scheme is desirable. The one in SP 800 126 rev1 is tolerable, but, in my opinion, by no means necessary nor the sole usable method. Once upon a time, a URL for the XCCDF document sufficed, as the XCCDF document in turn specified any companion documents, such as OVAL. This was simple, straightforward, and effective, which is why it likely came upon hard times. The Flying Dutchman of CPE drifted near enough at one time to alter the <tt><platform></tt> element in a way that should have been designed to be self-sufficient, but instead companion documents lacking any referential URI within the XCCDF document were deemed necessary. Convention, rather than explication, must be used if one cares about <tt><platform></tt>. Those who are happily without care (the French language has a pleasant term for this) can dispense with the <tt><platform></tt> element and all related CPE documents. For those who feel they must use <tt><platform></tt> elements, which, by the way, can be liberally sprinkled all over XCCDF documents (a practice that is rare at the moment), actual platform specificity can usually be determined using the value of its <tt>idref</tt> attribute without regard to ancillary documents. </body> </html>