Skip to content

Conversation

@ajnelson-nist
Copy link
Contributor

This Pull Request resolves all backwards-compatible requirements of Issue #651 outside of global prefix changes .

PR review progress will be tracked in PR #657 .

@ajnelson-nist ajnelson-nist added this to the UCO 1.4.0 milestone Apr 30, 2025
@ajnelson-nist ajnelson-nist linked an issue Apr 30, 2025 that may be closed by this pull request
15 tasks
@ajnelson-nist ajnelson-nist modified the milestones: UCO 1.4.0, UCO 1.5.0 May 27, 2025
@ajnelson-nist ajnelson-nist force-pushed the Feature-Issue-651-prefixes branch from 86972cd to 0d9cd33 Compare November 24, 2025 12:45
Perdurant was originally proposed in Issue 544 with a sibling class.
Issue 651 introduces Perdurant independently due to timelining needs.

No effects were observed on Make-managed files.

References:
* #544
* #651

Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
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>
…L-Time

A follow-on patch will regenerate Make-managed files.

References:
* #651

Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
References:
* #651

Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
@ajnelson-nist
Copy link
Contributor Author

This PR was being built on top of #657 . However, since initial drafting, I've realized that 657 will cause a lot of noise in the testing process (merging into unstable and the -2.0.0 branches) and shouldn't sit merged in testing long. I'm about to force-push an update to somewhat rebase the changes atop of develop since 1.4.0's release and leaves aside all global prefix changes aside from UCO's time:uco-time:. In case the old branch state is needed for review, I've archived it here.

@ajnelson-nist ajnelson-nist changed the base branch from Feature-Issue-651-prefixes to develop November 24, 2025 13:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

UCO should add support for the time relations

2 participants