Version 5.6 RC 3 has been posted

classic Classic list List threaded Threaded
13 messages Options
Reply | Threaded
Open this post in threaded view
|

Version 5.6 RC 3 has been posted

Jon Baker
Administrator

I am pleased to announce that Version 5.6 RC 3 has been posted.

 

http://oval.mitre.org/language/download/schema/version5.6/index.html

 

The changes in this new release candidate are limited to documentation updates to address concerns about the supported regular expression syntax in oval and the addition of new behaviors on the textfilecontent54_test to ensure that backwards compatibility is maintained.

 

With this release candidate we are also delaying the official release of version 5.6 by one week. The new release date is September 11th. If you have any questions or comments, please let us know.

 

Thank you for your continued review of the 5.6 release candidate,

 

Jon

 

============================================

Jonathan O. Baker

G022 - IA Industry Collaboration

The MITRE Corporation

Email: [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].
Reply | Threaded
Open this post in threaded view
|

Re: Version 5.6 RC 3 has been posted

James Hugard

Looks great!

 

-- James

 

 

Perfection is reached not when there is nothing left to add, but when nothing more can be taken away.”  -- Antoine de Saint-Exupery


James Hugard
Foundstone Architect
[hidden email]
(949) 212-9894 (cell)


McAfee, Inc.
27201 Puerta Real, Suite 400
Mission Viejo, CA 92691
(949) 297-5603 (direct)

 

Note: This email may contain confidential and privileged information for the sole use of the intended recipient. Any review or distribution by others is strictly prohibited. If you are not the intended recipient please contact the sender and delete all copies of this message.

 

 

 

 

From: Baker, Jon [mailto:[hidden email]]
Sent: Tuesday, September 01, 2009 6:39 PM
To: [hidden email]
Subject: [OVAL-DEVELOPER-LIST] Version 5.6 RC 3 has been posted

 

I am pleased to announce that Version 5.6 RC 3 has been posted.

 

http://oval.mitre.org/language/download/schema/version5.6/index.html

 

The changes in this new release candidate are limited to documentation updates to address concerns about the supported regular expression syntax in oval and the addition of new behaviors on the textfilecontent54_test to ensure that backwards compatibility is maintained.

 

With this release candidate we are also delaying the official release of version 5.6 by one week. The new release date is September 11th. If you have any questions or comments, please let us know.

 

Thank you for your continued review of the 5.6 release candidate,

 

Jon

 

============================================

Jonathan O. Baker

G022 - IA Industry Collaboration

The MITRE Corporation

Email: [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 [hidden email].
Reply | Threaded
Open this post in threaded view
|

Re: Version 5.6 RC 3 has been posted

James Hugard
In reply to this post by Jon Baker

One minor nit: the references to “re_support_1.0.html” are all plain text, not hyperlinks.

 

Also, in Textfilecontent54Behaviors, what is the meaning of “singleline” vs “multiline”?  One possible interpretation could be that the object processes individual lines rather than the file as a whole (a very good thing, because that allows the file to be parsed as a stream, rather then loaded into memory all at once).  If this is the case, perhaps the attribute name could be a bit more clear, such as “readlinebyline” or “parsebyline”, etc.  Some explanatory text would be quite helpful, too.

 

jh

 

From: Baker, Jon [mailto:[hidden email]]
Sent: Tuesday, September 01, 2009 6:39 PM
To: [hidden email]
Subject: [OVAL-DEVELOPER-LIST] Version 5.6 RC 3 has been posted

 

I am pleased to announce that Version 5.6 RC 3 has been posted.

 

http://oval.mitre.org/language/download/schema/version5.6/index.html

 

The changes in this new release candidate are limited to documentation updates to address concerns about the supported regular expression syntax in oval and the addition of new behaviors on the textfilecontent54_test to ensure that backwards compatibility is maintained.

 

With this release candidate we are also delaying the official release of version 5.6 by one week. The new release date is September 11th. If you have any questions or comments, please let us know.

 

Thank you for your continued review of the 5.6 release candidate,

 

Jon

 

============================================

Jonathan O. Baker

G022 - IA Industry Collaboration

The MITRE Corporation

Email: [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 [hidden email].
Reply | Threaded
Open this post in threaded view
|

Re: Version 5.6 RC 3 has been posted

Jon Baker
Administrator

re_support_1.0.html is referenced within the schema documentation and it is link to from here:

 

http://oval.mitre.org/language/about/index.html

 

I think it would make sense to also link from here:

 

http://oval.mitre.org/language/download/schema/version5.6/index.html

 

Does this help or were you looking for a specific location to insert another link?

 

Jon

 

============================================

Jonathan O. Baker

G022 - IA Industry Collaboration

The MITRE Corporation

Email: [hidden email]

 

From: [hidden email] [mailto:[hidden email]]
Sent: Wednesday, September 02, 2009 1:24 PM
To: oval-developer-list OVAL Developer List/Closed Public Discussion
Subject: Re: [OVAL-DEVELOPER-LIST] Version 5.6 RC 3 has been posted

 

One minor nit: the references to “re_support_1.0.html” are all plain text, not hyperlinks.

 

Also, in Textfilecontent54Behaviors, what is the meaning of “singleline” vs “multiline”?  One possible interpretation could be that the object processes individual lines rather than the file as a whole (a very good thing, because that allows the file to be parsed as a stream, rather then loaded into memory all at once).  If this is the case, perhaps the attribute name could be a bit more clear, such as “readlinebyline” or “parsebyline”, etc.  Some explanatory text would be quite helpful, too.

 

jh

 

From: Baker, Jon [mailto:[hidden email]]
Sent: Tuesday, September 01, 2009 6:39 PM
To: [hidden email]
Subject: [OVAL-DEVELOPER-LIST] Version 5.6 RC 3 has been posted

 

I am pleased to announce that Version 5.6 RC 3 has been posted.

 

http://oval.mitre.org/language/download/schema/version5.6/index.html

 

The changes in this new release candidate are limited to documentation updates to address concerns about the supported regular expression syntax in oval and the addition of new behaviors on the textfilecontent54_test to ensure that backwards compatibility is maintained.

 

With this release candidate we are also delaying the official release of version 5.6 by one week. The new release date is September 11th. If you have any questions or comments, please let us know.

 

Thank you for your continued review of the 5.6 release candidate,

 

Jon

 

============================================

Jonathan O. Baker

G022 - IA Industry Collaboration

The MITRE Corporation

Email: [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 [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].
Reply | Threaded
Open this post in threaded view
|

Re: Version 5.6 RC 3 has been posted

James Hugard

The following places have plain text of

 

                http://oval.mitre.org/language/about/re_support_1.0.html

 

rather than

 

                <a href=”http://oval.mitre.org/language/about/re_support_1.0.html”> http://oval.mitre.org/language/about/re_support_1.0.html</a>

 

Again, this is just a nit, since it’s easy enough to cut-and-paste the link into a browser.

 

----

 

http://oval.mitre.org/language/download/schema/version5.6/ovaldefinition/documentation/oval-common-schema.html

 

pattern match 

The 'pattern match' operation allows an item to be tested against a regular expression. When used by an entity in an OVAL Object, the regular expression represents the set of matching objects on the system. OVAL supports a common subset of the regular expression character classes, operations, expressions and other lexical tokens defined within Perl 5's regular expression specification. For more information on the supported regular expression syntax in OVAL see: http://oval.mitre.org/language/about/re_support_1.0.html

 

 

----

 

http://oval.mitre.org/language/download/schema/version5.6/ovaldefinition/documentation/oval-definitions-schema.html

 

== RegexCaptureFunctionType ==

<snip>

Note that when using regular expressions, OVAL supports a common subset of the regular expression character classes, operations, expressions and other lexical tokens defined within Perl 5's regular expression specification. For more information on the supported regular expression syntax in OVAL see: http://oval.mitre.org/language/about/re_support_1.0.html.

 

== EscapeRegexFunctionType ==

<snip>

Note that when using regular expressions, OVAL supports a common subset of the regular expression character classes, operations, expressions and other lexical tokens defined within Perl 5's regular expression specification. For more information on the supported regular expression syntax in OVAL see: http://oval.mitre.org/language/about/re_support_1.0.html.

 

 

 

From: Baker, Jon [mailto:[hidden email]]
Sent: Wednesday, September 02, 2009 10:29 AM
To: [hidden email]
Subject: Re: [OVAL-DEVELOPER-LIST] Version 5.6 RC 3 has been posted

 

re_support_1.0.html is referenced within the schema documentation and it is link to from here:

 

http://oval.mitre.org/language/about/index.html

 

I think it would make sense to also link from here:

 

http://oval.mitre.org/language/download/schema/version5.6/index.html

 

Does this help or were you looking for a specific location to insert another link?

 

Jon

 

============================================

Jonathan O. Baker

G022 - IA Industry Collaboration

The MITRE Corporation

Email: [hidden email]

 

From: [hidden email] [mailto:[hidden email]]
Sent: Wednesday, September 02, 2009 1:24 PM
To: oval-developer-list OVAL Developer List/Closed Public Discussion
Subject: Re: [OVAL-DEVELOPER-LIST] Version 5.6 RC 3 has been posted

 

One minor nit: the references to “re_support_1.0.html” are all plain text, not hyperlinks.

 

Also, in Textfilecontent54Behaviors, what is the meaning of “singleline” vs “multiline”?  One possible interpretation could be that the object processes individual lines rather than the file as a whole (a very good thing, because that allows the file to be parsed as a stream, rather then loaded into memory all at once).  If this is the case, perhaps the attribute name could be a bit more clear, such as “readlinebyline” or “parsebyline”, etc.  Some explanatory text would be quite helpful, too.

 

jh

 

From: Baker, Jon [mailto:[hidden email]]
Sent: Tuesday, September 01, 2009 6:39 PM
To: [hidden email]
Subject: [OVAL-DEVELOPER-LIST] Version 5.6 RC 3 has been posted

 

I am pleased to announce that Version 5.6 RC 3 has been posted.

 

http://oval.mitre.org/language/download/schema/version5.6/index.html

 

The changes in this new release candidate are limited to documentation updates to address concerns about the supported regular expression syntax in oval and the addition of new behaviors on the textfilecontent54_test to ensure that backwards compatibility is maintained.

 

With this release candidate we are also delaying the official release of version 5.6 by one week. The new release date is September 11th. If you have any questions or comments, please let us know.

 

Thank you for your continued review of the 5.6 release candidate,

 

Jon

 

============================================

Jonathan O. Baker

G022 - IA Industry Collaboration

The MITRE Corporation

Email: [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 [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 [hidden email].
Reply | Threaded
Open this post in threaded view
|

Re: Version 5.6 RC 3 has been posted

Jon Baker
Administrator

I see. The link comes from the xsd here. There is no real mark up in the xsd:documentation element that this link is included in. I will let this stand for now, but next time we open up the xsl the creates the element dictionaries we will look into changing this url to a link.

 

Thanks,

 

Jon

 

============================================

Jonathan O. Baker

G022 - IA Industry Collaboration

The MITRE Corporation

Email: [hidden email]

 

From: [hidden email] [mailto:[hidden email]]
Sent: Wednesday, September 02, 2009 1:40 PM
To: oval-developer-list OVAL Developer List/Closed Public Discussion
Subject: Re: [OVAL-DEVELOPER-LIST] Version 5.6 RC 3 has been posted

 

The following places have plain text of

 

                http://oval.mitre.org/language/about/re_support_1.0.html

 

rather than

 

                <a href=”http://oval.mitre.org/language/about/re_support_1.0.html”> http://oval.mitre.org/language/about/re_support_1.0.html</a>

 

Again, this is just a nit, since it’s easy enough to cut-and-paste the link into a browser.

 

----

 

http://oval.mitre.org/language/download/schema/version5.6/ovaldefinition/documentation/oval-common-schema.html

 

pattern match 

The 'pattern match' operation allows an item to be tested against a regular expression. When used by an entity in an OVAL Object, the regular expression represents the set of matching objects on the system. OVAL supports a common subset of the regular expression character classes, operations, expressions and other lexical tokens defined within Perl 5's regular expression specification. For more information on the supported regular expression syntax in OVAL see: http://oval.mitre.org/language/about/re_support_1.0.html

 

 

----

 

http://oval.mitre.org/language/download/schema/version5.6/ovaldefinition/documentation/oval-definitions-schema.html

 

== RegexCaptureFunctionType ==

<snip>

Note that when using regular expressions, OVAL supports a common subset of the regular expression character classes, operations, expressions and other lexical tokens defined within Perl 5's regular expression specification. For more information on the supported regular expression syntax in OVAL see: http://oval.mitre.org/language/about/re_support_1.0.html.

 

== EscapeRegexFunctionType ==

<snip>

Note that when using regular expressions, OVAL supports a common subset of the regular expression character classes, operations, expressions and other lexical tokens defined within Perl 5's regular expression specification. For more information on the supported regular expression syntax in OVAL see: http://oval.mitre.org/language/about/re_support_1.0.html.

 

 

 

From: Baker, Jon [mailto:[hidden email]]
Sent: Wednesday, September 02, 2009 10:29 AM
To: [hidden email]
Subject: Re: [OVAL-DEVELOPER-LIST] Version 5.6 RC 3 has been posted

 

re_support_1.0.html is referenced within the schema documentation and it is link to from here:

 

http://oval.mitre.org/language/about/index.html

 

I think it would make sense to also link from here:

 

http://oval.mitre.org/language/download/schema/version5.6/index.html

 

Does this help or were you looking for a specific location to insert another link?

 

Jon

 

============================================

Jonathan O. Baker

G022 - IA Industry Collaboration

The MITRE Corporation

Email: [hidden email]

 

From: [hidden email] [mailto:[hidden email]]
Sent: Wednesday, September 02, 2009 1:24 PM
To: oval-developer-list OVAL Developer List/Closed Public Discussion
Subject: Re: [OVAL-DEVELOPER-LIST] Version 5.6 RC 3 has been posted

 

One minor nit: the references to “re_support_1.0.html” are all plain text, not hyperlinks.

 

Also, in Textfilecontent54Behaviors, what is the meaning of “singleline” vs “multiline”?  One possible interpretation could be that the object processes individual lines rather than the file as a whole (a very good thing, because that allows the file to be parsed as a stream, rather then loaded into memory all at once).  If this is the case, perhaps the attribute name could be a bit more clear, such as “readlinebyline” or “parsebyline”, etc.  Some explanatory text would be quite helpful, too.

 

jh

 

From: Baker, Jon [mailto:[hidden email]]
Sent: Tuesday, September 01, 2009 6:39 PM
To: [hidden email]
Subject: [OVAL-DEVELOPER-LIST] Version 5.6 RC 3 has been posted

 

I am pleased to announce that Version 5.6 RC 3 has been posted.

 

http://oval.mitre.org/language/download/schema/version5.6/index.html

 

The changes in this new release candidate are limited to documentation updates to address concerns about the supported regular expression syntax in oval and the addition of new behaviors on the textfilecontent54_test to ensure that backwards compatibility is maintained.

 

With this release candidate we are also delaying the official release of version 5.6 by one week. The new release date is September 11th. If you have any questions or comments, please let us know.

 

Thank you for your continued review of the 5.6 release candidate,

 

Jon

 

============================================

Jonathan O. Baker

G022 - IA Industry Collaboration

The MITRE Corporation

Email: [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 [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 [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].
Reply | Threaded
Open this post in threaded view
|

Re: Version 5.6 RC 3 has been posted

James Hugard

Jon:

 

Can you also comment on the other item?

 

Also, in Textfilecontent54Behaviors, what is the meaning of “singleline” vs “multiline”?  One possible interpretation could be that the object processes individual lines rather than the file as a whole (a very good thing, because that allows the file to be parsed as a stream, rather then loaded into memory all at once).  If this is the case, perhaps the attribute name could be a bit more clear, such as “readlinebyline” or “parsebyline”, etc.  Some explanatory text would be quite helpful, too.

 

Thank you,

 

James

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].
Reply | Threaded
Open this post in threaded view
|

Re: Version 5.6 RC 3 has been posted

Jon Baker
Administrator

Given your previous suggestion to include a link in the html documentation I am wondering if you looked at the html documentation only or if you also looked at the documentation embedded in actual xml schema.

 

Here is a link to the html documentation:

http://oval.mitre.org/language/download/schema/version5.6/ovaldefinition/documentation/independent-definitions-schema.html#Textfilecontent54Behaviors

 

The xml schema documentation says this about the new behaviors:

 

ignore_case

'ignore_case' indicates whether case should be considered when matching system values against the regular expression provided by the pattern entity. This behavior is intended to align with the Perl regular expression 'i' modifier: if true, case will be ignored.  If false, case will not be ignored. The default is false.

 

Multiline

'multiline' enables multiple line semantics in the regular expression provided by the pattern entity. This behavior is intended to align with the Perl regular expression 'm' modifier: if true, the '^' and '$' metacharacters will match both at the beginning/end of a string, and immediately after/before newline characters.  If false, they will match only at the beginning/end of a string.  The default is false.

 

Singleline

'singleline' enables single line semantics in the regular expression provided by the pattern entity. This behavior is intended to align with the Perl regular expression 's' modifier: if true, the '.' metacharacter will match newlines. If false, it will not.  The default is false.

 

The schema can be found here:

http://oval.mitre.org/language/download/schema/version5.6/ovaldefinition/complete/independent-definitions-schema.xsd

 

Does the documentation above clarify the intent of the behaviors?

 

Jon

 

============================================

Jonathan O. Baker

G022 - IA Industry Collaboration

The MITRE Corporation

Email: [hidden email]

 

From: [hidden email] [mailto:[hidden email]]
Sent: Wednesday, September 02, 2009 2:53 PM
To: oval-developer-list OVAL Developer List/Closed Public Discussion
Subject: Re: [OVAL-DEVELOPER-LIST] Version 5.6 RC 3 has been posted

 

Jon:

 

Can you also comment on the other item?

 

Also, in Textfilecontent54Behaviors, what is the meaning of “singleline” vs “multiline”?  One possible interpretation could be that the object processes individual lines rather than the file as a whole (a very good thing, because that allows the file to be parsed as a stream, rather then loaded into memory all at once).  If this is the case, perhaps the attribute name could be a bit more clear, such as “readlinebyline” or “parsebyline”, etc.  Some explanatory text would be quite helpful, too.

 

Thank you,

 

James

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].
Reply | Threaded
Open this post in threaded view
|

Re: Version 5.6 RC 3 has been posted

James Hugard

Jon:

 

Yes, that’s exactly what I was doing (reading the HTML docs rather than schema).  Thanks for the clarification.

 

 

FYI:

 

The Singleline modifier is available with:

 

                Boost

                Java

                Perl5

                PCRE

                .NET

                Python

 

But not:

 

                ECMAScript (use [\s\S] instead)

 

Since the latter form is compatible with all the libraries tested, we would still like to recommend inclusion of just ignore_case and multiline.

 

-- James

 

From: Baker, Jon [mailto:[hidden email]]
Sent: Wednesday, September 02, 2009 12:44 PM
To: [hidden email]
Subject: Re: [OVAL-DEVELOPER-LIST] Version 5.6 RC 3 has been posted

 

Given your previous suggestion to include a link in the html documentation I am wondering if you looked at the html documentation only or if you also looked at the documentation embedded in actual xml schema.

 

Here is a link to the html documentation:

http://oval.mitre.org/language/download/schema/version5.6/ovaldefinition/documentation/independent-definitions-schema.html#Textfilecontent54Behaviors

 

The xml schema documentation says this about the new behaviors:

 

ignore_case

'ignore_case' indicates whether case should be considered when matching system values against the regular expression provided by the pattern entity. This behavior is intended to align with the Perl regular expression 'i' modifier: if true, case will be ignored.  If false, case will not be ignored. The default is false.

 

Multiline

'multiline' enables multiple line semantics in the regular expression provided by the pattern entity. This behavior is intended to align with the Perl regular expression 'm' modifier: if true, the '^' and '$' metacharacters will match both at the beginning/end of a string, and immediately after/before newline characters.  If false, they will match only at the beginning/end of a string.  The default is false.

 

Singleline

'singleline' enables single line semantics in the regular expression provided by the pattern entity. This behavior is intended to align with the Perl regular expression 's' modifier: if true, the '.' metacharacter will match newlines. If false, it will not.  The default is false.

 

The schema can be found here:

http://oval.mitre.org/language/download/schema/version5.6/ovaldefinition/complete/independent-definitions-schema.xsd

 

Does the documentation above clarify the intent of the behaviors?

 

Jon

 

============================================

Jonathan O. Baker

G022 - IA Industry Collaboration

The MITRE Corporation

Email: [hidden email]

 

From: [hidden email] [mailto:[hidden email]]
Sent: Wednesday, September 02, 2009 2:53 PM
To: oval-developer-list OVAL Developer List/Closed Public Discussion
Subject: Re: [OVAL-DEVELOPER-LIST] Version 5.6 RC 3 has been posted

 

Jon:

 

Can you also comment on the other item?

 

Also, in Textfilecontent54Behaviors, what is the meaning of “singleline” vs “multiline”?  One possible interpretation could be that the object processes individual lines rather than the file as a whole (a very good thing, because that allows the file to be parsed as a stream, rather then loaded into memory all at once).  If this is the case, perhaps the attribute name could be a bit more clear, such as “readlinebyline” or “parsebyline”, etc.  Some explanatory text would be quite helpful, too.

 

Thank you,

 

James

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 [hidden email].
Reply | Threaded
Open this post in threaded view
|

Re: Version 5.6 RC 3 has been posted

Jon Baker
Administrator

Ok, glad to hear the documentation in the schema helped. Once this release wraps up I would like to touch up the element dictionaries a bit (html documentation) to include more of the source schema documentation and include a notice that the schema should be referenced for more information.

 

Regarding the single line modifier, we internally debated that one a bit. Internally it was suggested that [\w\W] could be used which I think would have the same effect as your suggested [\s\S] solution. We went back and forth on this one and I can easily be convinced that we should allow the single line modifier. If we decide to make a change we would drop the newly added 'singleline' behavior and update the documentation to allow the ‘s’ modifier. I don’t think this change would require us to delay the release. I would like to know what others think about this though.

 

Also note that in reviewing your message and looking more at the new behaviors we discovered inconsistencies between the documentation and the schema on these new behaviors.

·         The documentation for multiline said that the default value is false, but the schema states that the default is true. The default should be true and the documentation will be corrected.

·         The documentation for the singleline behavior states that the default is false, but the schema states that the default is true. The schema default should be false and will be corrected.

 

Thanks,

 

Jon

 

============================================

Jonathan O. Baker

G022 - IA Industry Collaboration

The MITRE Corporation

Email: [hidden email]

 

From: [hidden email] [mailto:[hidden email]]
Sent: Wednesday, September 02, 2009 5:52 PM
To: oval-developer-list OVAL Developer List/Closed Public Discussion
Subject: Re: [OVAL-DEVELOPER-LIST] Version 5.6 RC 3 has been posted

 

Jon:

 

Yes, that’s exactly what I was doing (reading the HTML docs rather than schema).  Thanks for the clarification.

 

 

FYI:

 

The Singleline modifier is available with:

 

                Boost

                Java

                Perl5

                PCRE

                .NET

                Python

 

But not:

 

                ECMAScript (use [\s\S] instead)

 

Since the latter form is compatible with all the libraries tested, we would still like to recommend inclusion of just ignore_case and multiline.

 

-- James

 

From: Baker, Jon [mailto:[hidden email]]
Sent: Wednesday, September 02, 2009 12:44 PM
To: [hidden email]
Subject: Re: [OVAL-DEVELOPER-LIST] Version 5.6 RC 3 has been posted

 

Given your previous suggestion to include a link in the html documentation I am wondering if you looked at the html documentation only or if you also looked at the documentation embedded in actual xml schema.

 

Here is a link to the html documentation:

http://oval.mitre.org/language/download/schema/version5.6/ovaldefinition/documentation/independent-definitions-schema.html#Textfilecontent54Behaviors

 

The xml schema documentation says this about the new behaviors:

 

ignore_case

'ignore_case' indicates whether case should be considered when matching system values against the regular expression provided by the pattern entity. This behavior is intended to align with the Perl regular expression 'i' modifier: if true, case will be ignored.  If false, case will not be ignored. The default is false.

 

Multiline

'multiline' enables multiple line semantics in the regular expression provided by the pattern entity. This behavior is intended to align with the Perl regular expression 'm' modifier: if true, the '^' and '$' metacharacters will match both at the beginning/end of a string, and immediately after/before newline characters.  If false, they will match only at the beginning/end of a string.  The default is false.

 

Singleline

'singleline' enables single line semantics in the regular expression provided by the pattern entity. This behavior is intended to align with the Perl regular expression 's' modifier: if true, the '.' metacharacter will match newlines. If false, it will not.  The default is false.

 

The schema can be found here:

http://oval.mitre.org/language/download/schema/version5.6/ovaldefinition/complete/independent-definitions-schema.xsd

 

Does the documentation above clarify the intent of the behaviors?

 

Jon

 

============================================

Jonathan O. Baker

G022 - IA Industry Collaboration

The MITRE Corporation

Email: [hidden email]

 

From: [hidden email] [mailto:[hidden email]]
Sent: Wednesday, September 02, 2009 2:53 PM
To: oval-developer-list OVAL Developer List/Closed Public Discussion
Subject: Re: [OVAL-DEVELOPER-LIST] Version 5.6 RC 3 has been posted

 

Jon:

 

Can you also comment on the other item?

 

Also, in Textfilecontent54Behaviors, what is the meaning of “singleline” vs “multiline”?  One possible interpretation could be that the object processes individual lines rather than the file as a whole (a very good thing, because that allows the file to be parsed as a stream, rather then loaded into memory all at once).  If this is the case, perhaps the attribute name could be a bit more clear, such as “readlinebyline” or “parsebyline”, etc.  Some explanatory text would be quite helpful, too.

 

Thank you,

 

James

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 [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].
Reply | Threaded
Open this post in threaded view
|

Re: Version 5.6 RC 3 has been posted

Jon Baker
Administrator

As a result of this discussion we will drop the newly added 'singleline' behavior from the TextFileContent54Behaviors and update the documentation to allow the ‘s’ modifier.

 

Thanks,

 

Jon

 

============================================

Jonathan O. Baker

G022 - IA Industry Collaboration

The MITRE Corporation

Email: [hidden email]

 

From: Baker, Jon [mailto:[hidden email]]
Sent: Thursday, September 03, 2009 9:39 PM
To: oval-developer-list OVAL Developer List/Closed Public Discussion
Subject: Re: [OVAL-DEVELOPER-LIST] Version 5.6 RC 3 has been posted

 

Ok, glad to hear the documentation in the schema helped. Once this release wraps up I would like to touch up the element dictionaries a bit (html documentation) to include more of the source schema documentation and include a notice that the schema should be referenced for more information.

 

Regarding the single line modifier, we internally debated that one a bit. Internally it was suggested that [\w\W] could be used which I think would have the same effect as your suggested [\s\S] solution. We went back and forth on this one and I can easily be convinced that we should allow the single line modifier. If we decide to make a change we would drop the newly added 'singleline' behavior and update the documentation to allow the ‘s’ modifier. I don’t think this change would require us to delay the release. I would like to know what others think about this though.

 

Also note that in reviewing your message and looking more at the new behaviors we discovered inconsistencies between the documentation and the schema on these new behaviors.

·         The documentation for multiline said that the default value is false, but the schema states that the default is true. The default should be true and the documentation will be corrected.

·         The documentation for the singleline behavior states that the default is false, but the schema states that the default is true. The schema default should be false and will be corrected.

 

Thanks,

 

Jon

 

============================================

Jonathan O. Baker

G022 - IA Industry Collaboration

The MITRE Corporation

Email: [hidden email]

 

From: [hidden email] [mailto:[hidden email]]
Sent: Wednesday, September 02, 2009 5:52 PM
To: oval-developer-list OVAL Developer List/Closed Public Discussion
Subject: Re: [OVAL-DEVELOPER-LIST] Version 5.6 RC 3 has been posted

 

Jon:

 

Yes, that’s exactly what I was doing (reading the HTML docs rather than schema).  Thanks for the clarification.

 

 

FYI:

 

The Singleline modifier is available with:

 

                Boost

                Java

                Perl5

                PCRE

                .NET

                Python

 

But not:

 

                ECMAScript (use [\s\S] instead)

 

Since the latter form is compatible with all the libraries tested, we would still like to recommend inclusion of just ignore_case and multiline.

 

-- James

 

From: Baker, Jon [mailto:[hidden email]]
Sent: Wednesday, September 02, 2009 12:44 PM
To: [hidden email]
Subject: Re: [OVAL-DEVELOPER-LIST] Version 5.6 RC 3 has been posted

 

Given your previous suggestion to include a link in the html documentation I am wondering if you looked at the html documentation only or if you also looked at the documentation embedded in actual xml schema.

 

Here is a link to the html documentation:

http://oval.mitre.org/language/download/schema/version5.6/ovaldefinition/documentation/independent-definitions-schema.html#Textfilecontent54Behaviors

 

The xml schema documentation says this about the new behaviors:

 

ignore_case

'ignore_case' indicates whether case should be considered when matching system values against the regular expression provided by the pattern entity. This behavior is intended to align with the Perl regular expression 'i' modifier: if true, case will be ignored.  If false, case will not be ignored. The default is false.

 

Multiline

'multiline' enables multiple line semantics in the regular expression provided by the pattern entity. This behavior is intended to align with the Perl regular expression 'm' modifier: if true, the '^' and '$' metacharacters will match both at the beginning/end of a string, and immediately after/before newline characters.  If false, they will match only at the beginning/end of a string.  The default is false.

 

Singleline

'singleline' enables single line semantics in the regular expression provided by the pattern entity. This behavior is intended to align with the Perl regular expression 's' modifier: if true, the '.' metacharacter will match newlines. If false, it will not.  The default is false.

 

The schema can be found here:

http://oval.mitre.org/language/download/schema/version5.6/ovaldefinition/complete/independent-definitions-schema.xsd

 

Does the documentation above clarify the intent of the behaviors?

 

Jon

 

============================================

Jonathan O. Baker

G022 - IA Industry Collaboration

The MITRE Corporation

Email: [hidden email]

 

From: [hidden email] [mailto:[hidden email]]
Sent: Wednesday, September 02, 2009 2:53 PM
To: oval-developer-list OVAL Developer List/Closed Public Discussion
Subject: Re: [OVAL-DEVELOPER-LIST] Version 5.6 RC 3 has been posted

 

Jon:

 

Can you also comment on the other item?

 

Also, in Textfilecontent54Behaviors, what is the meaning of “singleline” vs “multiline”?  One possible interpretation could be that the object processes individual lines rather than the file as a whole (a very good thing, because that allows the file to be parsed as a stream, rather then loaded into memory all at once).  If this is the case, perhaps the attribute name could be a bit more clear, such as “readlinebyline” or “parsebyline”, etc.  Some explanatory text would be quite helpful, too.

 

Thank you,

 

James

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 [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 [hidden email].
Reply | Threaded
Open this post in threaded view
|

Re: Version 5.6 RC 3 has been posted

Andrew Buttner
Administrator
I'm not convinced that allowing the 's' modifier in the pattern is the best way forward.  As far as I am aware, these modifiers are not actually part of the regular expression syntax, but rather are library specific syntax designed to specify the mode in which to evaluate the regular expression.  (am I correct about this?)  It doesn't feel right to me to have the modifier as part of the pattern used within OVAL.

I'm in favor of keeping the schema as it stands.  No modifiers are allowed, there are some behaviors on the TextFileContent54 test to enable multiline features if desired.

Thanks
Drew

>-----Original Message-----
>From: Baker, Jon [mailto:[hidden email]]
>Sent: Tuesday, September 08, 2009 7:22 AM
>To: oval-developer-list OVAL Developer List/Closed Public Discussion
>Subject: Re: [OVAL-DEVELOPER-LIST] Version 5.6 RC 3 has been posted
>
>As a result of this discussion we will drop the newly added 'singleline' behavior
>from the TextFileContent54Behaviors and update the documentation to allow the 's'
>modifier.
>
>
>
>Thanks,
>
>
>
>Jon
>
>
>
>============================================
>
>Jonathan O. Baker
>
>G022 - IA Industry Collaboration
>
>The MITRE Corporation
>
>Email: [hidden email]
>
>
>
>From: Baker, Jon [mailto:[hidden email]]
>Sent: Thursday, September 03, 2009 9:39 PM
>To: oval-developer-list OVAL Developer List/Closed Public Discussion
>Subject: Re: [OVAL-DEVELOPER-LIST] Version 5.6 RC 3 has been posted
>
>
>
>Ok, glad to hear the documentation in the schema helped. Once this release wraps up I
>would like to touch up the element dictionaries a bit (html documentation) to include
>more of the source schema documentation and include a notice that the schema should
>be referenced for more information.
>
>
>
>Regarding the single line modifier, we internally debated that one a bit. Internally
>it was suggested that [\w\W] could be used which I think would have the same effect
>as your suggested [\s\S] solution. We went back and forth on this one and I can
>easily be convinced that we should allow the single line modifier. If we decide to
>make a change we would drop the newly added 'singleline' behavior and update the
>documentation to allow the 's' modifier. I don't think this change would require us
>to delay the release. I would like to know what others think about this though.
>
>
>
>Also note that in reviewing your message and looking more at the new behaviors we
>discovered inconsistencies between the documentation and the schema on these new
>behaviors.
>
>*         The documentation for multiline said that the default value is false, but
>the schema states that the default is true. The default should be true and the
>documentation will be corrected.
>
>*         The documentation for the singleline behavior states that the default is
>false, but the schema states that the default is true. The schema default should be
>false and will be corrected.
>
>
>
>Thanks,
>
>
>
>Jon
>
>
>
>============================================
>
>Jonathan O. Baker
>
>G022 - IA Industry Collaboration
>
>The MITRE Corporation
>
>Email: [hidden email]
>
>
>
>From: [hidden email] [mailto:[hidden email]]
>Sent: Wednesday, September 02, 2009 5:52 PM
>To: oval-developer-list OVAL Developer List/Closed Public Discussion
>Subject: Re: [OVAL-DEVELOPER-LIST] Version 5.6 RC 3 has been posted
>
>
>
>Jon:
>
>
>
>Yes, that's exactly what I was doing (reading the HTML docs rather than schema).
>Thanks for the clarification.
>
>
>
>
>
>FYI:
>
>
>
>The Singleline modifier is available with:
>
>
>
>                Boost
>
>                Java
>
>                Perl5
>
>                PCRE
>
>                .NET
>
>                Python
>
>
>
>But not:
>
>
>
>                ECMAScript (use [\s\S] instead)
>
>
>
>Since the latter form is compatible with all the libraries tested, we would still
>like to recommend inclusion of just ignore_case and multiline.
>
>
>
>-- James
>
>
>
>From: Baker, Jon [mailto:[hidden email]]
>Sent: Wednesday, September 02, 2009 12:44 PM
>To: [hidden email]
>Subject: Re: [OVAL-DEVELOPER-LIST] Version 5.6 RC 3 has been posted
>
>
>
>Given your previous suggestion to include a link in the html documentation I am
>wondering if you looked at the html documentation only or if you also looked at the
>documentation embedded in actual xml schema.
>
>
>
>Here is a link to the html documentation:
>
>http://oval.mitre.org/language/download/schema/version5.6/ovaldefinition/documentatio
>n/independent-definitions-schema.html#Textfilecontent54Behaviors
>
>
>
>The xml schema documentation says this about the new behaviors:
>
>
>
>ignore_case
>
>'ignore_case' indicates whether case should be considered when matching system values
>against the regular expression provided by the pattern entity. This behavior is
>intended to align with the Perl regular expression 'i' modifier: if true, case will
>be ignored.  If false, case will not be ignored. The default is false.
>
>
>
>Multiline
>
>'multiline' enables multiple line semantics in the regular expression provided by the
>pattern entity. This behavior is intended to align with the Perl regular expression
>'m' modifier: if true, the '^' and '$' metacharacters will match both at the
>beginning/end of a string, and immediately after/before newline characters.  If
>false, they will match only at the beginning/end of a string.  The default is false.
>
>
>
>Singleline
>
>'singleline' enables single line semantics in the regular expression provided by the
>pattern entity. This behavior is intended to align with the Perl regular expression
>'s' modifier: if true, the '.' metacharacter will match newlines. If false, it will
>not.  The default is false.
>
>
>
>The schema can be found here:
>
>http://oval.mitre.org/language/download/schema/version5.6/ovaldefinition/complete/ind
>ependent-definitions-schema.xsd
>
>
>
>Does the documentation above clarify the intent of the behaviors?
>
>
>
>Jon
>
>
>
>============================================
>
>Jonathan O. Baker
>
>G022 - IA Industry Collaboration
>
>The MITRE Corporation
>
>Email: [hidden email]
>
>
>
>From: [hidden email] [mailto:[hidden email]]
>Sent: Wednesday, September 02, 2009 2:53 PM
>To: oval-developer-list OVAL Developer List/Closed Public Discussion
>Subject: Re: [OVAL-DEVELOPER-LIST] Version 5.6 RC 3 has been posted
>
>
>
>Jon:
>
>
>
>Can you also comment on the other item?
>
>
>
>Also, in Textfilecontent54Behaviors, what is the meaning of "singleline" vs
>"multiline"?  One possible interpretation could be that the object processes
>individual lines rather than the file as a whole (a very good thing, because that
>allows the file to be parsed as a stream, rather then loaded into memory all at
>once).  If this is the case, perhaps the attribute name could be a bit more clear,
>such as "readlinebyline" or "parsebyline", etc.  Some explanatory text would be quite
>helpful, too.
>
>
>
>Thank you,
>
>
>
>James
>
>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].
>
>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 [hidden email].
Reply | Threaded
Open this post in threaded view
|

Re: Version 5.6 RC 3 has been posted

Jon Baker
Administrator
We held a quick meeting this morning to discuss this issue as a team here at MITRE. Over the course of the discussion I was convinced that RC 3 is correct in how it approached regular expression modifiers. Version 5.6 RC 3 currently states that modifiers are not supported. Sticking with this approach will ensure that we have specified a regex subset that is very widely supported and also allows us to enable additional behaviors on objects as needed.

I stand corrected and contrary to my message this morning, we should keep the 'singleline' behavior as it is defined on the Textfilecontent54Behaviors and continue to not support the use of regular expression modifiers.

Thanks,

Jon

============================================
Jonathan O. Baker
G022 - IA Industry Collaboration
The MITRE Corporation
Email: [hidden email]


>-----Original Message-----
>From: Buttner, Drew [mailto:[hidden email]]
>Sent: Tuesday, September 08, 2009 12:13 PM
>To: oval-developer-list OVAL Developer List/Closed Public Discussion
>Subject: Re: [OVAL-DEVELOPER-LIST] Version 5.6 RC 3 has been posted
>
>I'm not convinced that allowing the 's' modifier in the pattern is the best way
>forward.  As far as I am aware, these modifiers are not actually part of the
>regular expression syntax, but rather are library specific syntax designed to
>specify the mode in which to evaluate the regular expression.  (am I correct
>about this?)  It doesn't feel right to me to have the modifier as part of the
>pattern used within OVAL.
>
>I'm in favor of keeping the schema as it stands.  No modifiers are allowed,
>there are some behaviors on the TextFileContent54 test to enable multiline
>features if desired.
>
>Thanks
>Drew
>
>>-----Original Message-----
>>From: Baker, Jon [mailto:[hidden email]]
>>Sent: Tuesday, September 08, 2009 7:22 AM
>>To: oval-developer-list OVAL Developer List/Closed Public Discussion
>>Subject: Re: [OVAL-DEVELOPER-LIST] Version 5.6 RC 3 has been posted
>>
>>As a result of this discussion we will drop the newly added 'singleline'
>behavior
>>from the TextFileContent54Behaviors and update the documentation to allow the
>'s'
>>modifier.
>>
>>
>>
>>Thanks,
>>
>>
>>
>>Jon
>>
>>
>>
>>============================================
>>
>>Jonathan O. Baker
>>
>>G022 - IA Industry Collaboration
>>
>>The MITRE Corporation
>>
>>Email: [hidden email]
>>
>>
>>
>>From: Baker, Jon [mailto:[hidden email]]
>>Sent: Thursday, September 03, 2009 9:39 PM
>>To: oval-developer-list OVAL Developer List/Closed Public Discussion
>>Subject: Re: [OVAL-DEVELOPER-LIST] Version 5.6 RC 3 has been posted
>>
>>
>>
>>Ok, glad to hear the documentation in the schema helped. Once this release
>wraps up I
>>would like to touch up the element dictionaries a bit (html documentation) to
>include
>>more of the source schema documentation and include a notice that the schema
>should
>>be referenced for more information.
>>
>>
>>
>>Regarding the single line modifier, we internally debated that one a bit.
>Internally
>>it was suggested that [\w\W] could be used which I think would have the same
>effect
>>as your suggested [\s\S] solution. We went back and forth on this one and I
>can
>>easily be convinced that we should allow the single line modifier. If we
>decide to
>>make a change we would drop the newly added 'singleline' behavior and update
>the
>>documentation to allow the 's' modifier. I don't think this change would
>require us
>>to delay the release. I would like to know what others think about this
>though.
>>
>>
>>
>>Also note that in reviewing your message and looking more at the new behaviors
>we
>>discovered inconsistencies between the documentation and the schema on these
>new
>>behaviors.
>>
>>*         The documentation for multiline said that the default value is
>false, but
>>the schema states that the default is true. The default should be true and the
>>documentation will be corrected.
>>
>>*         The documentation for the singleline behavior states that the
>default is
>>false, but the schema states that the default is true. The schema default
>should be
>>false and will be corrected.
>>
>>
>>
>>Thanks,
>>
>>
>>
>>Jon
>>
>>
>>
>>============================================
>>
>>Jonathan O. Baker
>>
>>G022 - IA Industry Collaboration
>>
>>The MITRE Corporation
>>
>>Email: [hidden email]
>>
>>
>>
>>From: [hidden email] [mailto:[hidden email]]
>>Sent: Wednesday, September 02, 2009 5:52 PM
>>To: oval-developer-list OVAL Developer List/Closed Public Discussion
>>Subject: Re: [OVAL-DEVELOPER-LIST] Version 5.6 RC 3 has been posted
>>
>>
>>
>>Jon:
>>
>>
>>
>>Yes, that's exactly what I was doing (reading the HTML docs rather than
>schema).
>>Thanks for the clarification.
>>
>>
>>
>>
>>
>>FYI:
>>
>>
>>
>>The Singleline modifier is available with:
>>
>>
>>
>>                Boost
>>
>>                Java
>>
>>                Perl5
>>
>>                PCRE
>>
>>                .NET
>>
>>                Python
>>
>>
>>
>>But not:
>>
>>
>>
>>                ECMAScript (use [\s\S] instead)
>>
>>
>>
>>Since the latter form is compatible with all the libraries tested, we would
>still
>>like to recommend inclusion of just ignore_case and multiline.
>>
>>
>>
>>-- James
>>
>>
>>
>>From: Baker, Jon [mailto:[hidden email]]
>>Sent: Wednesday, September 02, 2009 12:44 PM
>>To: [hidden email]
>>Subject: Re: [OVAL-DEVELOPER-LIST] Version 5.6 RC 3 has been posted
>>
>>
>>
>>Given your previous suggestion to include a link in the html documentation I
>am
>>wondering if you looked at the html documentation only or if you also looked
>at the
>>documentation embedded in actual xml schema.
>>
>>
>>
>>Here is a link to the html documentation:
>>
>>http://oval.mitre.org/language/download/schema/version5.6/ovaldefinition/docum
>entatio
>>n/independent-definitions-schema.html#Textfilecontent54Behaviors
>>
>>
>>
>>The xml schema documentation says this about the new behaviors:
>>
>>
>>
>>ignore_case
>>
>>'ignore_case' indicates whether case should be considered when matching system
>values
>>against the regular expression provided by the pattern entity. This behavior
>is
>>intended to align with the Perl regular expression 'i' modifier: if true, case
>will
>>be ignored.  If false, case will not be ignored. The default is false.
>>
>>
>>
>>Multiline
>>
>>'multiline' enables multiple line semantics in the regular expression provided
>by the
>>pattern entity. This behavior is intended to align with the Perl regular
>expression
>>'m' modifier: if true, the '^' and '$' metacharacters will match both at the
>>beginning/end of a string, and immediately after/before newline characters.
>If
>>false, they will match only at the beginning/end of a string.  The default is
>false.
>>
>>
>>
>>Singleline
>>
>>'singleline' enables single line semantics in the regular expression provided
>by the
>>pattern entity. This behavior is intended to align with the Perl regular
>expression
>>'s' modifier: if true, the '.' metacharacter will match newlines. If false, it
>will
>>not.  The default is false.
>>
>>
>>
>>The schema can be found here:
>>
>>http://oval.mitre.org/language/download/schema/version5.6/ovaldefinition/compl
>ete/ind
>>ependent-definitions-schema.xsd
>>
>>
>>
>>Does the documentation above clarify the intent of the behaviors?
>>
>>
>>
>>Jon
>>
>>
>>
>>============================================
>>
>>Jonathan O. Baker
>>
>>G022 - IA Industry Collaboration
>>
>>The MITRE Corporation
>>
>>Email: [hidden email]
>>
>>
>>
>>From: [hidden email] [mailto:[hidden email]]
>>Sent: Wednesday, September 02, 2009 2:53 PM
>>To: oval-developer-list OVAL Developer List/Closed Public Discussion
>>Subject: Re: [OVAL-DEVELOPER-LIST] Version 5.6 RC 3 has been posted
>>
>>
>>
>>Jon:
>>
>>
>>
>>Can you also comment on the other item?
>>
>>
>>
>>Also, in Textfilecontent54Behaviors, what is the meaning of "singleline" vs
>>"multiline"?  One possible interpretation could be that the object processes
>>individual lines rather than the file as a whole (a very good thing, because
>that
>>allows the file to be parsed as a stream, rather then loaded into memory all
>at
>>once).  If this is the case, perhaps the attribute name could be a bit more
>clear,
>>such as "readlinebyline" or "parsebyline", etc.  Some explanatory text would
>be quite
>>helpful, too.
>>
>>
>>
>>Thank you,
>>
>>
>>
>>James
>>
>>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].
>>
>>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-DEVELOPER-
>[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].