Possible bug - ObservablePattern is not a subclass of Pattern

[ajnelson-nist]

Bug description

While reviewing subclasses of observable:Observable, I came across observable:ObservablePattern, which only has one superclass, observable:Observable.

Was this class intended to be a subclass of pattern:Pattern?

Steps to reproduce

The subclassing statement in UCO 1.2.0 is here.

Coordination

• Tracking in Jira ticket OC-297
• [x] Administrative review completed, proposal announced to Ontology Committees (OCs) on 2023-11-09
• [x] Solution announced to OCs on 2023-11-09
• [x] Solutions development phase completed. (N/A - bugfix)
• [x] Backwards-compatible implementation merged into develop for the next release (N/A)
• [x] develop state with backwards-compatible implementation merged into develop-2.0.0 (N/A)
• [x] Backwards-incompatible implementation merged into develop-2.0.0
• [x] Milestone linked
• [x] Documentation logged in pending release page
• [x] Prerelease publication: CASE develop branch updated to track UCO's updated develop branch (N/A)
• [x] Prerelease publication: CASE develop-2.0.0 branch updated to track UCO's updated develop-2.0.0 branch

[ajnelson-nist]

@sbarnum , do you have an answer on whether this was a bug?

Absent a reply, this will be discussed in the Ontology Committees meeting on 2023-08-29.

[ajnelson-nist]

@sbarnum confirmed on today's call - this was an oversight/bug.

[ajnelson-nist]

I think as a structural change, this would be backwards-incompatible and would need to target UCO 2.0.0.

[ajnelson-nist]

PR 560 has been posted as a resolution to this confirmed bug.

Note that the implementation had a non-trivial side effect of inducing the Observable namespace to import the Pattern namespace.

Because this was more than adding a subclass designation, I would prefer to handle this as a fast-track change proposal.

[ajnelson-nist]

PR 560 has been posted as a resolution to this confirmed bug.

Note that the implementation had a non-trivial side effect of inducing the Observable namespace to import the Pattern namespace.

Because this was more than adding a subclass designation, I would prefer to handle this as a fast-track change proposal.

This turned out to not be the case. The transitive import closure for the Observable namespace was not affected; ontology/uco/observable/catalog-v001.xml already notes that the Pattern namespace is in the transitive import closure.

The impact of this proposal is reduced back to being addition of a single triple, so it is now being treated the bugfix review workflow, for UCO 2.0.0.