Issue 651: Add support for time relations, including global prefix changes#657
Draft
ajnelson-nist wants to merge 3 commits intodevelopfrom
Draft
Issue 651: Add support for time relations, including global prefix changes#657ajnelson-nist wants to merge 3 commits intodevelopfrom
ajnelson-nist wants to merge 3 commits intodevelopfrom
Conversation
This change is due to Issue 651 proposing additions to the UCO Time namespace that will be describing concepts from the W3C OWL-Time namespace. For uniformity, instead of only `uco-time:` picking up the new prefix prefix [sic.], all UCO prefixes will now start `uco-`. A follow-on patch will regenerate Make-managed files. References: * #651 * https://www.w3.org/TR/owl-time/#abstract Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
15 tasks
This was referenced Apr 30, 2025
Contributor
Author
|
I caught a few needed prefixes in the examples' context definitions, which happened to have no effect on test results. Mostly it was forgotten |
References: * #651 Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
ajnelson-nist
force-pushed
the
Feature-Issue-651-prefixes
branch
from
86972cd to
0d9cd33
Compare
Contributor
Author
ajnelson-nist
added a commit
that referenced
this pull request
Nov 24, 2025
This change is due to Issue 651 proposing additions to the UCO Time namespace that will be describing concepts from the W3C OWL-Time namespace. For uniformity, instead of only `uco-time:` picking up the new prefix prefix [sic.], all UCO prefixes will start `uco-`; however, the effect of that change will be sufficiently distracting from the UCO Time concept additions that they are left to a separate branch (PR 657). No effects were observed on Make-managed files. References: * #651 * #657 * https://www.w3.org/TR/owl-time/#abstract Signed-off-by: Alex Nelsin <alexander.nelson@nist.gov>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This Pull Request will resolve all backwards-compatible requirements of Issue #651 .
The total changes for Issue 651 will be part of this PR. However, for review purposes, the changes specific to adding support for the time relations (properties, SHACL shapes, tests, etc.) are going into a separate PR. The initial needed change is adapting all prefixes to start with
uco-for disambiguating from OWL-Time (e.g.,core:UcoObjectwill now readuco-core:UcoObject), and that turns out to be thousands of changed lines.For the sake of easing review on GitHub, see this tab on PR #658, which shows the diffs that aren't just prefix-change effects. PR 658 will be merged into this PR after the Solutions Approval vote.
This PR will still track the testing progress.
Coordination
developunstablebranch (merge-commit)unstablebranch tracking UCO'sunstableas submodule (merge-commit)