-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Possible bug - ObservablePattern is not a subclass of Pattern #543
Comments
@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. |
@sbarnum confirmed on today's call - this was an oversight/bug. |
I think as a structural change, this would be backwards-incompatible and would need to target UCO 2.0.0. |
…mport This patch also has the Observable namespace import the Pattern namespace, to attain first access to the Pattern class. No effects were observed on Make-managed files. References: * #543 Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
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. |
The previous patch included a direct Pattern namespace import. This turns out to not be necessary because the Pattern namespace is already in the transitive `owl:imports` closure, via the Action namespace. Hence, the `Pattern` class is already available for `ObservablePattern`. I realized this when I noticed the `catalog-v001.xml` file didn't require an update from adding the direct import. References: * #543 Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
No effects were observed on Make-managed files. References: * ucoProject/UCO#543 Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
A follow-on patch will regenerate Make-managed files. References: * ucoProject/UCO#543 Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
References: * ucoProject/UCO#543 Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
No effects were observed on Make-managed files. References: * ucoProject/UCO#543 Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
No effects were observed on Make-managed files. References: * ucoProject/UCO#543 Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
This turned out to not be the case. The transitive import closure for the Observable namespace was not affected; 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. |
No effects were observed on Make-managed files. References: * ucoProject/UCO#543 Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
No effects were observed on Make-managed files. References: * ucoProject/UCO#543 Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
No effects were observed on Make-managed files. References: * ucoProject/UCO#543 Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
No effects were observed on Make-managed files. References: * ucoProject/UCO#543 Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
References: * ucoProject/UCO#543 Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
No effects were observed on Make-managed files. References: * ucoProject/UCO#543 Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
A follow-on patch will regenerate Make-managed files. References: * ucoProject/UCO#543 Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
References: * ucoProject/UCO#543 Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
No effects were observed on Make-managed files. References: * ucoProject/UCO#543 Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
No effects were observed on Make-managed files. References: * ucoProject/UCO#543 Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
Bug description
While reviewing subclasses of
observable:Observable
, I came acrossobservable: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
develop
for the next release (N/A)develop
state with backwards-compatible implementation merged intodevelop-2.0.0
(N/A)develop-2.0.0
develop
branch updated to track UCO's updateddevelop
branch (N/A)develop-2.0.0
branch updated to track UCO's updateddevelop-2.0.0
branchThe text was updated successfully, but these errors were encountered: