`ObservablePattern` definition depends on object AND action; should be AND/OR?

[ajnelson-nist]

The definition of observable:ObservablePattern reads as follows in UCO 1.4.0:

An observable pattern is a grouping of characteristics unique to a logical pattern composed of observable object and observable action properties.

It is unclear if the "and" is intended to be truly restrictive.

I haven't seen a demonstration of observable:ObservablePattern, and am unclear how it distinguishes from pattern:LogicalPattern.

For reference:

• LogicalPattern has this definition: "A logical pattern is a grouping of characteristics unique to an informational pattern expressed via a structured pattern expression following the rules of logic."
• Issue 550 was posted to demonstrate several query patterns, but I'd asked a question, still unanswered, on whether those query patterns (such as a SQL query) would be subclasses of ObservablePattern.

The current Issue pertains to the narrower question of if ObservablePattern is meant to somehow require both ObservableObjects and ObservableActions. This could be answered by the question, "Is a SQL query (neverminding running the query---just the query string itself) an ObservablePattern?"

If the SQL query (and other queries from #550) were intended to be LogicalPattern and ObservablePatterns, can we change the definition of ObservablePattern to be (emphasis added):

An observable pattern is a grouping of characteristics unique to a logical pattern composed of observable object and/or observable action properties.

[sbarnum]

I definitely believe this was an unintentional typo. It should be and/or

[ajnelson-nist]

I think this would be a low-risk change and merit either bugfix (no review) or fast-track (Solutions Approval vote, should be in September) to correct. Reasoning: There may have been an informal expectation set that some ObservableAction be associated because of the spelling. But we had never encoded that. Further as a relaxation to "and/or", we would not be invalidating any instance of an ObservablePattern that had done both.

Let's confirm on today's call.