Basically, if someone out there feels like tracking down this or any bug in the tool they can email it to me. I will review the code and push an update to SourceForge.
Unfortunately I have been informed that we cannot open the project to outside developers without oversight and we cannot afford to perform the oversight ourselves. If there is anyone out there willing to take over management, please talk to me as we are interested in finding a partner on this.
>-----Original Message-----
>From: Kent Landfield [mailto:
[hidden email]]
>Sent: Friday, October 23, 2009 8:21 AM
>To: oval-developer-list OVAL Developer List/Closed Public Discussion
>Subject: Re: [OVAL-DEVELOPER-LIST] 5.6 Schema problem?
>
>Any chance this could be opened up a bit on sourceforge so others could
>actively work the project as well? Seems putting the code on
>sourceforge and then restricting its updating to those that are being
>paid to do it is sort of counter intuitive to the intent to move it to
>sourceforge in the first place. FWIW..
>
>--
>Kent Landfield
>Director, Risk and Compliance Security Research
>McAfee, Inc.
>+1 972.963.7096 Direct
>+1 214.385.1138 Mobile
>
[hidden email]
>-----Original Message-----
>From: Schmidt, Charles M. [mailto:
[hidden email]]
>Sent: Friday, October 23, 2009 8:07 AM
>To:
[hidden email]
>Subject: Re: [OVAL-DEVELOPER-LIST] 5.6 Schema problem?
>
>Regarding the Benchmark Editor, the issue has been logged. As there are
>currently no funds to support fixes to the editor, I don't know when
>I'll have a chance to track this down, but will attempt to do so when
>time permits.
>
>Thanks,
>Charles
>
>>-----Original Message-----
>>From:
[hidden email] [mailto:
[hidden email]]
>>Sent: Friday, October 23, 2009 7:56 AM
>>To: oval-developer-list OVAL Developer List/Closed Public Discussion
>>Subject: Re: [OVAL-DEVELOPER-LIST] 5.6 Schema problem?
>>
>>This causes the Mitre Benchmark Editor tool to go into an infinite loop
>>while trying to recursively load the 5.6 schemas. In general, it seems
>>like bad form to create a circular reference.
>>
>>Paul Whitehurst
>>
>>
>>On 10/23/09 7:13 AM, "Haynes, Dan" <
[hidden email]> wrote:
>>
>>Hi Paul,
>>
>>The import of the independent-definitions-schema.xsd file in the oval-
>>definitions-schema.xsd file is intentional. The import is necessary
>>because there are xsd:keyref elements (name = "variable_objectKeyRef"
>>and name = "variable_stateKeyRef"), in the oval-definitions-schema.xsd
>>file, that contain xsd:selector and xsd:field elements that have xpath
>>attributes that reference elements in the independent-defintions-
>>schema.xsd file. In particular, these xpath attributes reference the
>>ind-def:var_ref, ind-def:variable_object, and ind-def:variable_state
>>elements. These xsd:keyref elements were added into the oval-
>>defintions-schema.xsd file, in OVAL 5.6, to ensure that all variables
>>referenced in the ind-def:variable_object/ind-def:var_ref and ind-
>>def:variable_state/ind-def:var_ref elements are present in the OVAL
>>Definition document. Please let me know if you have any additional
>>questions.
>>
>>Thanks,
>>
>>Danny
>>
>>
>>
>>From:
[hidden email] [mailto:
[hidden email]]
>>Sent: Thursday, October 22, 2009 2:39 PM
>>To: oval-developer-list OVAL Developer List/Closed Public Discussion
>>Subject: [OVAL-DEVELOPER-LIST] 5.6 Schema problem?
>>
>>I just found that the oval-definitions-schema.xsd file imports the
>>independent schema. Is this intentional? If so, why?
>>
>>Paul Whitehurst
>>To unsubscribe, send an email message to
[hidden email] with
>>SIGNOFF OVAL-DEVELOPER-LIST in the BODY of the message. If you have
>>difficulties, write to
[hidden email].
>>To unsubscribe, send an email message to
[hidden email] with
>>SIGNOFF OVAL-DEVELOPER-LIST in the BODY of the message. If you have
>>difficulties, write to
[hidden email].
>>
>>To unsubscribe, send an email message to
[hidden email] with
>>SIGNOFF OVAL-DEVELOPER-LIST
>>in the BODY of the message. If you have difficulties, write to OVAL-
>>
[hidden email].
>
>To unsubscribe, send an email message to
[hidden email] with
>SIGNOFF OVAL-DEVELOPER-LIST
>in the BODY of the message. If you have difficulties, write to OVAL-
>
[hidden email].
>
>To unsubscribe, send an email message to
[hidden email] with
>SIGNOFF OVAL-DEVELOPER-LIST
>in the BODY of the message. If you have difficulties, write to OVAL-
>
[hidden email].
in the BODY of the message. If you have difficulties, write to
